Just setup a new sub-domain to host this with SSL from #letsencypt

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 }

#CaddyServer #Caddy #SSL #ACME #LetsEncypt #ZeroSSL

Wir haben gerade #Obon in #Japan und daher hatte ich Zeit #SuiteCRM und #GLPI auf einem #RaspberryPi zu installieren. Mittels #DynDNS und #LetsEncypt ist er auch von aussen zu erreichen. Erstaunlich diese Power des Raspi5 und wiedermal ein Beweiss fuer gute #OpenSource Software fuer den Business Bereich.

It looks like #letsencypt doesn't give you actual security in some cases.

Really sad story.

https://notes.valdikss.org.ru/jabber.ru-mitm/

#mitm

Encrypted traffic interception on Hetzner and Linode targeting the largest Russian XMPP (Jabber) messaging service —

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.

https://github.com/lucaslorentz/caddy-docker-proxy

GitHub - lucaslorentz/caddy-docker-proxy: Caddy as a reverse proxy for Docker

Caddy as a reverse proxy for Docker. Contribute to lucaslorentz/caddy-docker-proxy development by creating an account on GitHub.

GitHub