# Docker push fails wuth "server gave HTTP response to HTTPS client" error

**URL:** <https://community.sonatype.com/t/docker-push-fails-wuth-server-gave-http-response-to-https-client-error/3273>\
**Category:** Sonatype Nexus Repository\
**Created:** [January 13, 2020, 7:20am UTC](https://community.sonatype.com/t/docker-push-fails-wuth-server-gave-http-response-to-https-client-error/3273 "2020-01-13T07:20:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mak.tibco](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mak.tibco](https://community.sonatype.com/u/mak.tibco)\
**Post date:** [January 13, 2020, 7:20am UTC](https://community.sonatype.com/t/docker-push-fails-wuth-server-gave-http-response-to-https-client-error/3273/1 "2020-01-13T07:20:34Z")

</div>

Hi Team,

I have created docker(hosted)repository and trying to push image and getting below error

[root@XXXXXX ~]# docker tag envoy:v2 XXXXX:18078/rancher:mytag  
[root@XXXXXX ~]# docker push XXXXX:18078/rancher:mytag  
The push refers to a repository [XXXXXX:18078/rancher]  
Get [https://XXXXXX:18078/v1/\_ping:](https://XXXXXX:18078/v1/_ping:) http: server gave HTTP response to HTTPS client

Kindly suggest what am i missing.

Regards,  
Makesh.

---

<div class="post-metadata">

**Author:** ![andres](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/andres/32/201_2.png) [@andres](https://community.sonatype.com/u/andres)\
**Post date:** [January 13, 2020, 3:17pm UTC](https://community.sonatype.com/t/docker-push-fails-wuth-server-gave-http-response-to-https-client-error/3273/2 "2020-01-13T15:17:16Z")

</div>

Hi there Makesh,

Looks like the Docker daemon is expecting an SSL connection and it is not getting it back. Is the 18078 connector an HTTP connector, or HTTPs?

The following page goes over the intricacies of setting up a registry in Repository Manager to correctly communicate with a docker client: [SSL and Repository Connector Configuration](https://help.sonatype.com/repomanager3/formats/docker-registry/ssl-and-repository-connector-configuration)

If you created an HTTP connector in Repository Manager, you can quickly test the theory by marking it as ‘insecure’ with the daemon: [Test an insecure registry | Docker Documentation](https://docs.docker.com/registry/insecure/)  
I will warn you, the use of this flag _is not supported by Repository Manager_, but this test can help guide your next steps.