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
You can easily forward arbitrary IP traffic if you get an additional IP for that VPS. Then you add the IP as your own on the local end, and set up routing like
ip r a 1.2.3.4 via 10.10.10.10 dev wg0where 1.2.3.4 is the extra ip, and 10.10.10.10 is your local wireguard address.With just one IP, you can forward ports over wireguard with iptables, but I failed to do that correctly.
Now I'm using xinetd to forward traffic from external ports to Wireguard with a single IP. iptables would be better but I ran out of patience.