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.
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
I fully admit I may be doing this wrong. But in order to connect to a server over Wireguard I'm connecting to it over its Wireguard IP address. (And if I'm not connecting to it over Wireguard I don't connect to it over a Wireguard IP address.) It's relevant to note that I'm not using Wireguard as a traditional VPN where all traffic bound for the internet is tunneled over Wireguard. Instead, I'm using it strictly for point-to-point tunneling from a client to one of my servers. In other words, my default routes don't go to Wireguard. Maybe that's the difference here?