How do I get ZeroSSL to re-use previously issued cert?

I am using Caddy 2.10.

This is my config:

glama.ai {
	tls {
		issuer zerossl 63e85e3ead0....
	}

  ...
}

My issue is that every time I deploy the service, it seems like Caddy issues a new cert. This has caused several outages.

How do I reference earlier issued certificate or otherwise reduce the risk of downtime?

Please don’t skip the template. Fill it out because that’s how we can help.

3 Likes

Without the full details from the template, we’re left to guess.

My best guess is that you’re running Caddy in a Docker container without persistent storage. So each time you redeploy, the previous container is wiped, and the new instance has to request a fresh certificate because the old one is gone.

That said, I’ll echo what @Mohammed90 mentioned - please don’t skip the template. It really helps us help you.

2 Likes

That is correct.

Is there a documentation for how to do it differently when running in a docker container?

The official Docker page for Caddy includes some usage examples.

https://hub.docker.com/_/caddy

The data directory must not be treated as a cache. Its contents are not ephemeral or merely for the sake of performance. Caddy stores TLS certificates, private keys, OCSP staples, and other necessary information to the data directory. It should not be purged without an understanding of the implications.

3 Likes

That makes sense. Thank you