Why does docker stop working after upgrading to Artifactory 4.4.0?

JFrog Support
2016-10-06 13:38

From Artifactory version 4.4.0, the X-Artifactory-Override-Base-Url become a mandatory header on a reverse proxy configuration for Docker repositories.

Without it Docker client commands such as login, push and pull will fail to work.

For NGINX, this should be added:

proxy_set_header X-Artifactory-Override-Base-Url $http_x_forwarded_proto://$host:$server_port/<public context>;

For example, 

proxy_set_header X-Artifactory-Override-Base-Url  $http_x_forwarded_proto://$host:$server_port


proxy_set_header X-Artifactory-Override-Base-Url  $http_x_forwarded_proto://$host:444/my-artifactory

For Apache, this should be added:


RequestHeader set X-Artifactory-Override-Base-Url %{my_scheme}e://<server name>/<public context>


For example   


RequestHeader set X-Artifactory-Override-Base-Url %{my_scheme}e://artifactory.com/artifactory

From Artifactory version 4.4.1, for backward compatibility on existing configurations, there will be a fallback on the code level in case this header is missing.

How ever, best practice is still to set on the reversed proxy with this header (for requests to be handled on the reversed proxy level) so it should not be removed.

More information can be found on the following wiki guide.