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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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
As I said, I've got a VPS. The VPS is not on my local net, but in a datacenter. As part of being a VPS it has a unique IPv4.
My VPN (which I currently use for TCP traffic) is hosted on the VPS, giving me access to (and from) all devices connected to my VPN regardless of whether they are behind a NAT or not.
I've also got a beefy server which hosts more power hungry services, though this one is behind multiple layers of NAT. I can forward and reverse-proxy TCP services from the beefy server through the VPN and out to the public net using another server with a unique IPv4 just fine.
What I (and OP) need, is to also be able to forward\reverse-proxy UDP services from a beefy NATed/firewalled server through a VPN and out to the public internet using another server which has a unique IPv4.