Plex Remote Access Not Working? Complete Fix Guide
Remote access is the most common Plex headache. The dreaded “Not available outside your network” message. Here’s every cause and fix, in order of likelihood.
1. Port Forwarding
Plex needs port 32400 (TCP) forwarded from your router to your server’s local IP. Go to your router admin page (usually 192.168.1.1) and add the rule. Most routers have a “Port Forwarding” or “Virtual Server” section.
Common mistakes:
- Forwarding to the wrong internal IP (check your server’s IP with
ipconfigorip addr) - Forwarding UDP instead of TCP (Plex uses TCP on 32400)
- Firewall blocking the port (Windows Firewall, UFW on Linux)
2. Double NAT
If you have two routers (ISP modem/router combo + your own router), you have double NAT. Port forwarding on your router alone won’t work because the ISP router blocks incoming traffic too.
Fix: put the ISP modem in bridge mode, or forward 32400 on BOTH devices.
3. CGNAT
Some ISPs (especially mobile/fixed wireless like T-Mobile Home Internet, Starlink) use CGNAT — they share one public IP among many customers. Port forwarding is impossible because you don’t have your own public IP.
Workarounds:
- Ask your ISP for a public IP (some offer it for $5–10/month)
- Use a VPN with port forwarding (Mullvad, AirVPN)
- Use Cloudflare Tunnel or Tailscale to bypass NAT entirely
- Accept Plex relay (works but limited to 2 Mbps without Plex Pass, 10 Mbps with)
4. ISP Blocking Port 32400
Some ISPs block common server ports. Test by changing Plex’s port to something unusual (like 42400) in Settings > Network > Custom server access URL. Update your port forwarding rule to match.
5. Server Sleeping
If your server goes to sleep, remote access drops. Disable sleep in your OS power settings when the server needs to stay available.