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 use a VPS as a homelab gateway of sorts from the outside.
Essentially, the VPS runs a Wireguard server that I connect to on my OPNSense Router. The VPS then reverse-proxies all incoming traffic through the tunnel to my homelab. All my DNS entries point to the VPS's IP. This pretty much gives me a static IP, hides my real IP, and lets me do some light caching on the VPS. Kind of like a DIY cloudflare.
I also run Uptime Kuma on the VPS, since it will continue to work if my local network is down.
I do the same thing, except with openvpn. I need to upgrade it to wireguard. I ended up just masquerading the traffic opnsense router, but now everything looks like it is coming from the internal openvpn ip address.
How are you identifying traffic that needs to go out the vpn, vs traffic that doesn't, if you don't mind sharing?
Indeed, this is perfect. No need for something like Cloudflare proxying in this case.
Which reverse-proxy do you use?