Switching my Caddy server to use ZeroSSL for AMCE SSL certification, replacing LetsEncrypt, was as easy as adding this to my Caddyfile:
{
acme_ca https://acme.zerossl.com/v2/DV90
}
Switching my Caddy server to use ZeroSSL for AMCE SSL certification, replacing LetsEncrypt, was as easy as adding this to my Caddyfile:
{
acme_ca https://acme.zerossl.com/v2/DV90
}
It looks like #letsencypt doesn't give you actual security in some cases.
Really sad story.
Spent sometime playing with Caddy tonight in my #homelab. I set the DNS to my #Tailscale IP so I have a sweet private domain for accessing the 25 different containers I run on this home server.
The only tricky part was #LetsEncypt validation with the private IP. Ended up using the #AWS Route53 Caddy plugin.
I went with the caddy-docker-proxy container by Lucas Lorentz over the official image due to the Docker Compose labels support.