Your Plex library, anywhere, even behind CGNAT
Plex says "Not available outside your network" when your ISP won't let anything in. Your own WireGuard server fixes that: it has a static IP, forwards Plex's port down an encrypted tunnel to your home, and keeps your home IP private. No router changes.
- Works behind CGNAT
- Nothing to open at home
- Static IP
- Set up within 24 hours
- Rated Excellent on Trustpilot
- Human support, 24/7
- No activity logs
- 30-day money-back guarantee
Why Plex can't be reached from outside
Remote access needs viewers to reach your Plex server on a public address. More and more home connections can't offer one.
CGNAT
Many ISPs share one public IP between lots of customers. There's no address that belongs to you, so port forwarding on your router has nothing to forward from.
Starlink, 4G and 5G
Satellite and mobile home broadband almost always sit behind CGNAT. Plex works inside the house and nowhere else.
Routers that won't forward
ISP routers that lock the settings, double NAT from a second router, or a landlord's network you can't change.
An address that keeps changing
A home IP that changes breaks links and custom URLs. Your server's IP stays the same for as long as you have it.
Your home IP on show
Opening port 32400 at home publishes your home address to everyone you share with, and to anyone scanning for open servers.
Stuck on Plex Relay
When Plex can't connect directly it falls back to its relay, which limits streams to low quality. A direct connection to your server avoids it.
A public address that comes to you
Your Plex machine connects out to your own WireGuard server, which works on any connection because it's an outgoing connection. Viewers connect to the server's static IP on port 32400, and the server passes that traffic down the encrypted tunnel to Plex at home. To Plex, and to everyone you share with, the server is your public address.
- A whole server for you
- Static IP where you choose
- Unlimited port forwarding
- TCP, UDP or both
- No bandwidth caps or charges
- Managed from your dashboard
- Server
- Built for you in the location you choose, with its own static IP that isn't shared with anyone.
- Tunnel
- The WireGuard app on your Plex machine or NAS connects out to the server. Nothing comes in through your router.
- Port forward
- 32400 TCP on the server goes to Plex on your machine. Add more for Jellyfin, Emby or anything else.
- Plex
- Set Remote Access to the forwarded port. Plex checks it and turns green.
Remote access in four steps
Everything on our side is done from your dashboard. No command line.
Order your server
Choose the location closest to your Plex server at checkout. It's built and tested for you within 24 hours, often much sooner.
Connect your Plex machine
In your dashboard, create a user for the Plex machine and download its config. Import it into the WireGuard app on Windows, macOS, Linux, or your NAS.
Forward Plex's port
Add a port forward on your server to that user.32400 TCP → 32400
Tell Plex the port
In Plex, open Settings, then Remote Access, tick Manually specify public port and enter the same port.Public port: 32400 → Apply
Plex needs to see the server as its public address. The config you download sends the Plex machine's internet traffic through the tunnel, so it works as it is. If you change it to send only some traffic through the tunnel, add http://YOUR-SERVER-IP:32400 in Plex under Settings, Network, Custom server access URLs, so viewers are pointed to the server.
TVs at home showing as remote? With Plex's traffic in the tunnel, Plex can mistake devices on your own network for remote ones. Add your home network, for example 192.168.1.0/24, under Settings, Network, LAN Networks, and they'll play locally at full quality. On Windows, also untick Block untunneled traffic for the tunnel in the WireGuard app, so devices at home can still reach Plex.
Plex, Jellyfin, Emby and the rest of your stack
Plex Media Server
Forward 32400 TCP and set Remote Access to the same port. Share libraries with friends and family as normal; they connect to your server, never your house.
Jellyfin and Emby
Forward 8096 TCP, or 8920 for HTTPS, to the same machine. Run them alongside Plex on one server: port forwarding is unlimited.
NAS, Docker and Unraid
Anything that runs WireGuard can use your server, including Synology, QNAP, Unraid and a WireGuard container in Docker. Up to 253 devices per server.
About Plex Pass. Since 29 April 2025, Plex requires Plex Pass on the server owner's account, or a Remote Watch Pass for each viewer, to stream personal video remotely. Music to Plexamp is still free. Your server makes Plex reachable; Plex's own rules decide who can watch. Plex's requirements →
One server for Plex, and everything else
No setup fee, no bandwidth charges and nothing extra for port forwards. Use the same server as your own private VPN, for game servers or for cameras at home. No VPN plan needed.
- Static IP
- Unlimited port forwarding
- Up to 253 devices
- 11 locations
30-day money-back guarantee
Plex remote access questions
Do I need to open any ports on my router?
No. Your Plex machine connects out to your server over WireGuard, and viewers connect to the server. Nothing is opened on your home router, so it works even when your router or ISP won't let you forward ports.
Does it work behind CGNAT, Starlink or 4G and 5G home internet?
Yes. Those connections share one public IP between many customers, so incoming connections can't reach you and Plex shows "Not available outside your network". With a dedicated server, viewers reach the server's own static IP and the stream comes down your tunnel.
Will Plex show "Fully accessible outside your network"?
Yes, once two things are in place: the Plex machine sends its internet traffic through the tunnel, so Plex sees the server's IP as its public address, and Remote Access is set to the port you forwarded (32400). If you only send some traffic through the tunnel, add your server's address as a custom server access URL instead. The steps above cover both.
Is it fast enough for 4K?
The limit is usually your home upload speed, because every remote stream starts at your house. We don't cap or charge for bandwidth. Choose a server location close to where your Plex server is for the best throughput, and let Plex convert to a lower quality for viewers on slow connections.
Do I need Plex Pass?
Plex decides that, not us. Since 29 April 2025, streaming personal video remotely needs Plex Pass on the server owner's account, or a Remote Watch Pass for each viewer. Music to Plexamp is still free. Your server makes Plex reachable; Plex's own rules decide who can watch.
Does all my household's internet go through the server?
No. Only the device you add the WireGuard configuration to, usually the Plex machine or NAS, uses the tunnel. Everything else in the house carries on as normal.
Does it work with Jellyfin and Emby?
Yes. Forward port 8096 (or 8920 for HTTPS) to the machine running Jellyfin or Emby instead of 32400. You can run all three on one server: port forwarding is unlimited.
Can I use the server for other things too?
Yes. It's a full dedicated WireGuard server with its own static IP, up to 253 devices and unlimited port forwarding, TCP, UDP or both. Use it as your own VPN, host a game server, or reach a home camera system.
Which location should I choose?
The one closest to your Plex server. That keeps the path between your house and the server short, which matters most for streaming. Viewers anywhere in the world connect to it as normal.
Turn "Not available outside your network" green
Your own WireGuard server with a static IP and unlimited port forwarding, from $11.99/month. Covered by our 30-day money-back guarantee.