I thought so too for a long time. Had to figure it out for actual budget though. Tailscale makes that aspect pretty simple. Still probably too complex for your average user, but if you’re setting up self hosted apps you should be able to figure it out.
Comment on They Said Self-Hosting Was Hard! - arthurpizza
realitaetsverlust@piefed.zip 3 weeks ago
As long as you don’t directly connect it to the internet, it’s not hard.
When you do, it does become hard.
Itsamelemmy@lemmy.zip 2 weeks ago
realitaetsverlust@piefed.zip 2 weeks ago
The “average user” shouldn’t selfhost anything. Might sound mean or like gatekeeping, but it’s the truth. It can be dangerous. There’s a reason why I hire an electrician to do my house installation even tho I theoretically know how to do it myself - because I’m not amazingly well versed in it and might burn down my house, or worse, burn down other peoples houses.
People who are serious about selfhosting need to learn how to do it. Halfassing it will only lead to it getting breached, integrated into a botnet and being a burden on the rest of humanity.
autriyo@feddit.org 3 weeks ago
Only if you care about security, which you should ofc.
realitaetsverlust@piefed.zip 3 weeks 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 3 weeks 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 2 weeks 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.LunaChocken@programming.dev 2 weeks ago
A lot of people simply don’t have time to go the extra steps.
Instead you should be focused on secure by default design. E.g. not setting a static router password to admin admin.
It’s stupid in this day and age to continue to see default logins occur still.
realitaetsverlust@piefed.zip 2 weeks ago
Sorry, but that is no reason. That’s a bit akin to having a dog and saying: “Nah I don’t have time to walk the dog now”. Selfhosting something that is publicly available (not as in “everyone can use it” but “everyone can access it") bears some level of responsibility. You either make the time to properly set up and maintain it, or you shouldn’t selfhost stuff.
LunaChocken@programming.dev 3 weeks ago
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.
Croquette@sh.itjust.works 3 weeks ago
Tell that to someone starting out and look at their deer in the headlight face. Then you’ll realize that the point went over your head.