Replication to Azure Container Registry resluts in 413: request entity too large

[inzanez]

Hi

I got a local Harbor based registry and set up a replication rule to push certain images to an Azure Container Registry. The type of the registry I push to in the Harbor UI is Azure ACR and the connection test is successful.

Starting the replication (only images) though results in 413 errors as mentioned above. What I found so far was that this is often due to a proxy setting, but...I am not sure where that should be? I am not aware of a proxy on the Azure side nor do I have one running on my local Harbor instance (except for the nginx-photon being part of the Harbor deployment, but I could not imagine why that specific proxy should interfere with a push migration)...

[wy65701436]

To setup the proxy for replication, you should config the proxy server for harbor-core and jobservice(https://github.com/goharbor/harbor/blob/main/make/harbor.yml.tmpl#L240).

[inzanez]

@wy65701436 but why? Is it necessary to use a proxy for replication to work? My services could go to the internet directly, no proxy required,...