I’ve been self hosting traditionally in debian, but I would like to be able to add services easier using docker. As such, I’m looking to move to a container based architecture.
One place I struggle is that I can’t seem to find a good container where the default image supports ACME to support Let’s encrypt for automatic cert renewal.
For Nginx, I would have you build my container. HAproxy ACME support seems to be a shell script.
Any suggestions?
You must log in or register to comment.
Caddy supports the HTTP-01 and TLS-ALPN-01 challenges by default, you just need to expose 80/443 and it just works. But if you want to use the DNS-01 challenge you’d need to build it with a plugin of your DNS provider.
Traefik supports all 3 challenges equally ootb, with a wide range of DNS providers. But it is a bit harder to configure and doesn’t support being a web server.
I didn’t understand, why not use nginx? It has built in support for let’s encrypt by default, you just have to activate it in the nginx config. https://nginx.org/en/docs/http/ngx_http_acme_module.html
It’s not Let’s Encrypt, but I’ve been happy with this Cloudflare-flavored ACME through Caddy.
https://github.com/CaddyBuilds/caddy-cloudflare
I really only use it for my local-hosted stuff that I don’t expose to the web. So, when I’m at home, https://radarr/.[mydomain].com resolves to 192.168.1.145:7878. That sort of thing…
You might check docker swag. It’s got built in certbot client and has preconfigured support for a couple hundred common self-hosted services.
I second SWAG. nginx, let’s encrypt, plenty of ready-to-go configs, it’s pretty great
I use Caddy and it’s great. ACME is very easy to configure, as is everything else. I haven’t tried running it in a container tho but they have official images published so it should work without issues.
I don’t think running Caddy in a container is needed. All my apps are docker images and Caddy is a system app. I treated as an important OS app.
Agreed
I run it in a container without problems. All you have you do is bind it to port 80 and 443. I prefer the container to running it directly within the host OS for ease of portability.
Also strongly recommend building it with support for DNS based validation. Using DNS validation you can have multiple instances running across the different servers you ha e to easily switch to or provide better local routing. For example please. I run one caddy frontend on a VPS that routes my traffic most of the time, but when I’m at home my DNS points me at a very instance that is running on my server on my home network avoiding the path of lit to the internet and back home. Using http based validation would require me to sync certs around.
This is usually where something like Traefik comes in. It will reverse proxy the docker instance and it can be configured to handle let’s encrypt. The are also other options I like nginx proxy manager and I think Caddy also can do this, by I don’t have experience with that.
Yep I use caddy for all that. Bonus is caddy has a docker compose proxy plugin where all your domain/port/cert config can be part of your each application’s compose file, rather than needing to make adjustments in caddy centrally. Works great for my purposes.
thanks for mentioning the Caddy-Docker-Proxy plugin.
If you want to be able to manage it via a web page instead of config files, nginx proxy manager works well, and can be run via docker/docker compose.
Can confirm running Nginx Proxy Manager with 30 configurations. Been running solid for years.
I’ve been having constant issues for over a year where it’s not able to auto update any of my certs. It has been erroring when I even try to do a manual update, but the second it’s deleted and reset up it’s fine (for the time being).
I recently installed on a new system, and it took of lot of tries with nondescript errors to get new certs fetched
Weird. With port 80/443 it should have no issues updating.
I’ve only used it on 80/443 but this issue has been happening on numerous different VMs enough to the point I’ve just stopped using it for new installs.
I’m considering moving to Talos, so I imagine Traefik would work better in k8s right?
Traefik also supports running on K8s, yes.
On that note, if you’re moving to K8s, I recommend looking into K8s Gateway API, it’s the successor to the old Ingress API. There are other, more complete, implementations of it than Traefik. See https://gateway-api.sigs.k8s.io/
Which gateway implementations would you recommend?
I’m looking to support HTTPS and Webdav
I use Zoraxy and it is great if you like GUIs.
Traefik and caddy were mentioned, the third in the game is usually nginxproxymanager.
I’m using both traefik and nginx in two different setups. The nginxproxymanager can be configured via UI natively which makes checking configurations a bit easier.
Traefik on the other hand is configured easily within the compose itself and you have everything in one place.
This turned out to be tiresome though if you don’t have a monolithic compose file - that’s actually even hr history why I switched to npm in the first place.
I don’t have any experience with caddy so can’t provide anecdotal insights there.
Don’t know if this fits for your use case but I am in love with pangolin.
I use traefik since I’m hosting stuff in docker and it works great. I think, Caddy is another popular pick, but I haven’t tried it and cannot tell you anything about it.
Take a look at Zoraxy or NPM.
Yeah, I switched to Zoraxy from NPM and it’s been great.
I find some of the workflows in it a bit strange, like not having an Add button on the list of host proxies, it’s a separate menu item on the left which weird. And the way you request a SSL cert by hitting OK and then you get a popup asking if you want a cert, and you’d better have already set your options for how you want the cert, but if you create a host without a cert you have to go through all the options again and check them because it doesn’t keep track of your preference.
IDK, in any case it fixed a bunch of problems I was having with NPM so it has that going for it, which is nice.
I have the same issues you listed. I only have one wildcard domain so it was only an issue once but I do think a UI change/workflow would help.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters HTTP Hypertext Transfer Protocol, the Web k8s Kubernetes container management package nginx Popular HTTP server
[Thread #122 for this comm, first seen 28th Feb 2026, 06:40] [FAQ] [Full list] [Contact] [Source code]
