I setup caddy and a proxy server for ingress.
Essentially I have a server with wireguard connections between my home server and the external VM.
Proxy using proxy protocol with nginx so it preserves the ip.
DNS certificate management with cloudflare, and I’ve got Authelia in front of the majority of my websites, with some exclusion rules, say for a share link.
Authelia has mandatory 2FA, anything less is silly, with Grafana alloy scrapping caddy metrics.
Anywho most of my stuff runs in docker. The stuff I don’t want on the WAN but on tailscale/Lan has a filter to block the wireguard interface.
realitaetsverlust@piefed.zip 1 day ago
People who don’t care about security are the cancer of the selfhosting-world. Billions of devices are part of a botnet because lazy owners don’t care about even the most basic shit, like changing the stock password. It’s insane.
autriyo@feddit.org 1 day ago
Still feels like I’m doing too little, but kinda hate 2fa.
And I kinda don’t want to know if complex passwords and low retries before an account gets locked out are enough.
realitaetsverlust@piefed.zip 17 hours ago
I’ve created a custom cert that I verify within my nginx proxy using
ssl_client_certificateandssl_verify_client on. I got that cert on every device I use in the browser storage, additionally on a USB stick on my keychain in case I’m on a foreign or new machine. That is so much easier that bothering with passwords and the likes.autriyo@feddit.org 13 hours ago
That would only work if I’m the only one using my hosted stuff, but can’t really expect non tech ppl to deal with stuff like that.
They already struggle with the little 2fa they have to use. Introducing yet another system is too much to ask.