Migrating to Caddy with existing LetsEncrypt certs

I’ve been running something of a Rube Goldberg machine involving Ansible + nginx + letsencrypt to provide a secure endpoint for our user’s custom domains. They point they domain name to our proxy, we provide the SSL certs through LetsEncrypt, and forward the request on to our apps servers


I’m considering migrating to Caddy to simplify the deployment of this stack and reduce the number of moving parts. I’ve built a quick prototype and it appears to work really well :+1:

But I’m wondering if I can / should migrate the existing LetsEncrypt certs?

I’ve currently got 171 sites configured with certs from LetsEncrypt (using the letsencrypt command line tool).

  1. Can I reference those existing certs from Caddy?
  2. Should I? Or should I let Caddy try to reissue them? Does that even work?
  3. And if I just reference them from the Caddyfile, how will they be renewed?

The easiest thing is to just let caddy re-issue them. Rate limits could be an issue, but likely not, unless you have a high number of subdomains of a single domain. Shouldn’t hurt to try.


As Craig says, just let Caddy do its auto-HTTPS. If you provide certs manually, you’ll have to renew them manually too. The best thing you can do is let Caddy just obtain and manage them for you.

If you have a lot of subdomains, switch them over to Caddy a little bit at a time so you don’t hit rate limits.

1 Like

Ok, cool. That sounds like a plan. I might scrounge some time this week to test out the migration

Thanks for your help @matt @captncraig

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.