Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Only if you care about security, which you should ofc.
People who don't care about security are the cancer of the selfhosting-world. Billions of devices are part of a botnet because lazy/stupid owners don't care about even the most basic shit, like changing the stock password. It's insane.
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.
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.
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.
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, and it's infinitely more secure.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.
Adding certificates is a 5 step process: Settings -> Privacy and Security -> View Certificates -> Import -> Select file and confirm. That's on firefox at least, idk about chrome, but probably not significantly more complex. With screenshots, a small guide would be fairly easy to follow.
Don't get me wrong, I do get your point, but I don't feel like making users add client certs to their browser storage is more work than helping them every 2 weeks because they forgot their password or shit like that lol. At least, that's my experience. And the cool thing about client certs is they can't really break it, unlike passwords which they can forget, or change them because they forgot, just to then forget they changed it. Once it runs, it runs.
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.
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.