42
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Sep 2026
42 points (97.7% liked)
Selfhosted
62205 readers
1487 users here now
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!
founded 3 years ago
MODERATORS
Are you unable to port forward?
Can't port forward through the CGNAT of my ISP, only my own router's NAT.
That is, unless I buy a unique IPv4 from my ISP.
Have the ISP place their gateway/router into bridge mode. This will pass the public WAN IP directly to your router, allowing it to handle NAT, firewall policies, and port forwarding without double NAT.
I’ve been hosting public-facing servers for several years and regularly run dedicated servers for my son. I keep the ISP gateway in the setup because they provide a substantial discount for using their modem/router rather than connecting the UDM Pro directly to the fiber ONT.
I actually had that up and running before they changed our modem and threw us behind their regular CGNAT. I've tried bridging the modem, but it's no use if the bridge leads to their intermidiary network and not the public internet. :(
They problably hadn't realized (or didn't care) that we had a unique IPv4 before, so I was lucky enough that simply opening up the provided modem and my router was enough. Now they want 15€ a month for the same service, but at least it'll be static...
Gotcha by the balls, VPN would have the same problem unless you can host the VPN server on IPv6?
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.