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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I'll just open them up to the internet via an nginx reverse proxy. Make sure sign up is disabled in the applications, and something blocks people from brute-forcing passwords. Pretty sure Nextcloud comes like that per default. And I'll do updates. And see if I can run stuff in containers or seperate users so in the unlikely case something happens, access to one of my services doesn't compromise the entire server.
Lots of other people use VPNs though. Like Wireguard, Netbird, Tailscale...
I do both. Wireguard VPN for anything that's just me. Expose via nginx proxy for things that are shared with friends and family.
I wouch for the VPN route... VPN servers are built to be exposed, are hardened/engineered to resist the harshness of the net and are somewhat safe even with default settings.
Should you publish on the wild a few web apps, you would have to harden, monitor and manage a bunch of environments and/or frameworks with a load of quirks each.
A VPN is easier to maintain and safer for your data with a lower effort.
I wouch for the VPN route…
Found Barry Kripke
At least of all the answers I prefer your way the most. So you set up a WireGuard access for all of the devices of your users on your router or did you install the vpn-system directly on the homeserver?
my home router is the stock one from my isp and have no vpn capabilities.
I put a port forward on the router and then configured everything on the internal node; in my case it is an opnsense vm running on proxmox.
I don't give access to any of my services to anyone, especially family or friends. LOL However, you could investigate Tailscale, Headscale, Wireguard. Additionally, if you set up Cloudflare Tunnel/Zero Trust, you can give individual users a unique access to your server. For example: You can allow alice@mysupercoolserver.com to access https://home.mysupercoolserver/shell but deny bob@mysupercoolserver.com. Only allow bob access only to https://home.mysupercoolserver/media.
I've been preferring mTLS recently. I still use a VPN for management, SMB/NFS, and anything important. But I use mTLS for web services that I'd like to access without having a VPN active all the time. Although, if your web service had a mobile app, usually they don't play nicely with mTLS, so a VPN would be required for me, but Home Assistant and TrilliumDroid do have mTLS support.
Do you happen to know of any guides on setting mTLS up?
I didn't find much other than descriptions of the technology from my search, but I'm probably not using the right terms.
I don't remember which one I specifically used, but theres plenty that show when you DDG "mtls nginx". There's probably others specific to other reverse proxies too.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| HTTP | Hypertext Transfer Protocol, the Web |
| NFS | Network File System, a Unix-based file-sharing protocol known for performance and efficiency |
| SMB | Server Message Block protocol for file and printer sharing; Windows-native |
| VPN | Virtual Private Network |
| nginx | Popular HTTP server |
4 acronyms in this thread; the most compressed thread commented on today has 9 acronyms.
[Thread #197 for this comm, first seen 29th Mar 2026, 00:20] [FAQ] [Full list] [Contact] [Source code]