# Reloading certificate

**URL:** <https://forums.docker.com/t/reloading-certificate/29833>\
**Category:** Docker Engine\
**Created:** [March 15, 2017, 11:39pm UTC](https://forums.docker.com/t/reloading-certificate/29833 "2017-03-15T23:39:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dockermon](https://avatars.discourse-cdn.com/v4/letter/d/848f3c/32.png) [@dockermon](https://forums.docker.com/u/dockermon)\
**Post date:** [March 15, 2017, 11:39pm UTC](https://forums.docker.com/t/reloading-certificate/29833/1 "2017-03-15T23:39:14Z")

</div>

Hello,

I’m planning to move my registry to another server, where I will also want to use a new certificate, which is placed in /etc/docker/certs.d/myregistry/

I need to deploy the certificate on all servers, but I don’t really want to restart the docker daemon, to “load” the new certificate file. Is there a way to reload the certificate file, without restarting all containers?

Will the command “kill -HUP ” help me on this and reload the certificate file?  
When I just replace the certificate file, it doesn’t seem to work as expected.

I’m using Docker version 1.10.3

Thank you!

---

<div class="post-metadata">

**Author:** ![jritchie](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/jritchie/32/24913_2.png) [@jritchie](https://forums.docker.com/u/jritchie)\
**Post date:** [September 5, 2019, 5:26pm UTC](https://forums.docker.com/t/reloading-certificate/29833/2 "2019-09-05T17:26:15Z")

</div>

Did you ever come up with an answer to this? I’d like to know the same thing. Sure would be nice to be a bit less aggressive for a simple certificate addition.