How to Get a Public IP for Starlink CGNAT Home Servers

The missing piece for many Starlink homelabs is not bandwidth. It is a reachable public IP.

The problem

When Starlink puts you behind CGNAT, your router can make outbound connections, but the internet cannot start a connection back to your NAS, game server, Home Assistant, or reverse proxy.

The frustrating part is that everything inside your home network can be configured correctly and the service can still be unreachable from outside.

What people usually try

• Upgrade to a plan with public IP if it exists for you.
• Use a VPN mesh, but every visitor needs access.
• Rent a VPS and wire it back home.

Most failed setups come from using the right tool for the wrong job: private VPNs for public visitors, web tunnels for non-web traffic, or a VPS when all you wanted was forwarding.

The simpler shape

A managed public IPv4 ingress gives you the part you actually need: a public address and port rules that forward home over WireGuard.

Instead of moving the application to the cloud, you move only the public entry point there.

Where PUBLIC-IP.CLOUD fits

PUBLIC-IP.CLOUD is built for this narrow job: give a home server behind CGNAT a static public IPv4 and forward only the ports you choose. You open only the ports you need from the dashboard. TCP port 25 is blocked by policy, and spam, scanning, malware, and attack traffic are not allowed.

It is not a VPS and not a privacy VPN. It is the public ingress layer many home servers are missing: one static public IPv4, explicit port rules, and a WireGuard path back to your homelab.

Good fit

• Starlink, 5G home internet, double NAT, and ISP CGNAT connections
• Home Assistant, NAS, Jellyfin, Plex, reverse proxies, and small web apps
• People who tried router port forwarding and Dynamic DNS but still cannot connect
• Anyone who would rent a cheap VPS only to forward traffic home

Quick setup

1. Create an account.
2. Add your WireGuard public key or use the starter config.
3. Open the public TCP/UDP ports you want.
4. Point your domain or clients at the assigned static public IPv4.

Bottom line

CGNAT turns port forwarding into a puzzle. A managed public ingress turns it back into a product decision.