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
Install tailscale on your vps. Install tailscale on your router. Use tailscale option (on your router) to expose subnet to the tailnet, the subnet being whatever you're trying to reverse proxy.
Replace tailscale with headscale if you're paranoid, can run headscale on the vps too if you want to. I had this sort of working, my issue i ran into was manually setting up outbound rules for tailscale traffic in pfsense. Manual because the pfsense tailscale plugin didn't let you specify a headscale server, it only plays with the official tailacale backplane. Installing tailacale on the pfsense command line works and gets around this and your router will show up on your headscale tailnet, but the outbound rules wont automatically be created... so... twas a rabbit hole I didn't feeling like exploring at the time.