Selfhosted

I switched from SWAG to Caddy. Its config file is much simpler, with many best practice settings being default resulting in each sites being like 3 lines of code. Implementing something like mTLS requires one line per site, just super nice to configure, and you’re not left without a template config for more obscure services.

That being said, SWAG does more than enough and Nginx is a powerful software so you really aren’t missing out on anything but more streamlined config.

Traefik is kind of just like, a nightmare that tries to sell you on it being “self configuring” but it takes some work to get to that point and the “self configuring” requires the same amount of time in a text editor as manually configuring Caddy does. I can see Traefik being powerful if you’re using it with actually clustered k8s and distributed workloads. If that’s not your use case it’s kinda just more work than it’s worth.

I was an avid nginx user but having caddy handle the ssl certificate creation and renewal is amazing.

I probably am outdated on nginx (maybe it supports it?) but caddy is what I use from here on out.

Not depend on a specific corporation to access all your services for one.

A reverse proxy (I use nginx) will let you centralize certificates and allow the use of subdomains easily, without depending from a specific service provider like cloudflare.

Looks like you are are a lucky american with access to a real IP address, good for you, a luxury nowadays where CG-NAT is common place everywhere.

Opening a port is not even possible where I live.

Well, not using Cloudflare would make us all rely a bit less on a single company that already dominates the internet. And it'd make them unable to theoretically mess with your traffic and snoop on your data. Other than that... I don't think you're missing out on features.

Haven't messed with it personally (yet), but I've seen some examples where Caddy can do some cool stuff (I think the example I saw recently was defining routes that can call an arbitrary program with the HTTP request details).

I use Nginx almost exclusively (I've got HAProxy in the mix, too, but it's strictly for load balancing). Everyone always keeps recommending Traefik to me, but from what I've seen, it doesn't do anything Nginx can't already do, and the config is all bizarre and way less intuitive. Not saying it's bad, just not for me. (This is not an invitation to proselytize Traefix at me lol).

Use whatever works for you.

Except that everything is under your control and not managed by a third party, not much I think.

If this setup works for you and you're happy with it, just keep it going.

If you have time to spare, want to learn new things, tinkerer arround with network security, certificates, DNS, reverse proxy and, and, and... You can give it a try in a virtual machine and docker containers. But keep in mind that's not an easy way and involves a lot of personal time before you get a GOOD working self-hosted / exposed services.

I wouldn't recommend to open any port on your router except for a secured tunnel like wireguard and connect to your services through that tunnel. Opening port 443/80 on your router is bound to some heavy automated scanning and brute force by bots. If you don't have the necessary knowledge/tool/hardware, this is just going to put you at risk of ddos and remote attacks.

That's way something like cloudflare is populare, they most of the time take care of that nuisance and also why something like wireguard is popular among the selfhosting community.

No.