Self-hosting behind CGNAT
Anything at home that the internet has to reach first, like a media server, a game server, a smart home hub, a camera recorder, a remote desktop or a file server, needs an incoming connection. CGNAT blocks incoming IPv4 connections, so these break in the same way.
Pick what you're running
- Media server behind CGNAT: why remote streaming fails
- Game server behind CGNAT: why friends can't join
- Home automation behind CGNAT: remote access to your hub
- Security cameras behind CGNAT: why remote viewing fails
- Remote desktop behind CGNAT: reaching your home computer
- Home file server behind CGNAT: remote access to your files
The common thread
Behind CGNAT, your router has no public IPv4 address of its own. Port forwarding on your router only works if the ISP's NAT forwards the port too, and that's up to the ISP (RFC 6269, section 5.2.1). Outgoing connections, and everything on your home network, keep working.
The ISP-side fixes are the same for every use case: ask to be moved off CGNAT to a public IPv4, buy a static IP if your ISP sells one on home plans, or use IPv6 where both ends support it. Of the 41 ISPs we track, 12 give a public IPv4 by default. See ISPs without CGNAT or use the ISP finder.
First, confirm it's CGNAT
Run the CGNAT checker or follow how to tell if you're behind CGNAT.
This site sticks to ISP facts. It doesn't review or recommend third-party products or services.