You’ve set up Plex, your library looks perfect at home, and then you try to stream from work or your phone on cellular — nothing. The dreaded “Not available outside your network” message. Or worse: it connects but everything buffers at 2 Mbps through the Plex relay.

Remote access issues are the second most common Plex problem we fix (after 4K transcoding). The good news: once you understand what Plex needs from your network, the fix is usually straightforward.

How Plex Remote Access Actually Works

When you enable remote access, Plex tries to make your server reachable from the internet. Here’s the simplified version:

If any link in that chain breaks, remote access fails. Let’s walk through each failure mode.

Cause #1: Port Forwarding Isn’t Set Up (or Is Wrong)

This is the most common cause. Plex tries to use UPnP to automatically configure your router, but UPnP is unreliable on many consumer routers.

The Fix

Log into your router (usually 192.168.1.1 or 192.168.0.1) and manually create a port forward:

After saving, go to Plex Settings → Remote Access → click “Retry.” The green checkmark should appear within 30 seconds.

Cause #2: Double NAT

If you have two routers (common when your ISP provides a modem/router combo and you added your own router), you’re behind double NAT. Port forwarding on your inner router doesn’t help because the outer router blocks the traffic first.

The Fix

You have three options, in order of preference:

  1. Bridge mode: Put the ISP router/modem into bridge mode so it passes all traffic to your router. This is the cleanest solution.
  2. DMZ: Set your inner router’s WAN IP as the DMZ host on the ISP router. Less clean but works.
  3. Double port forward: Forward 32400 on both routers. Fragile and annoying to maintain.

Cause #3: CGNAT (Carrier-Grade NAT)

This is the worst one. Some ISPs (especially mobile/5G home internet providers like T-Mobile Home Internet) put you behind CGNAT, meaning you don’t even have a real public IP address. No amount of port forwarding will work.

How to Check

Compare your router’s WAN IP (shown on the router admin page) with your actual public IP (search “what is my IP”). If they’re different, you’re behind CGNAT.

The Fix

Cause #4: Firewall Blocking Port 32400

Your OS firewall (Windows Defender, UFW on Linux, macOS firewall) might be blocking incoming connections even if your router is forwarding correctly.

The Fix

On Windows: open Windows Defender Firewall → Advanced Settings → Inbound Rules → create a new rule allowing TCP 32400. On Linux: sudo ufw allow 32400/tcp. On macOS: System Preferences → Security → Firewall → add Plex Media Server to allowed apps.

Cause #5: Plex Relay Fallback

When direct connection fails, Plex falls back to its relay service. The relay works but caps bandwidth at roughly 2 Mbps — enough for 720p at best. If your remote streams look terrible, you’re probably on the relay.

How to Check

In Plex, go to Settings → Remote Access. If it says “Not available outside your network” but you can still connect remotely, you’re on the relay. Also check the Dashboard during playback — relay connections show a different icon.

The Fix

Fix the underlying remote access issue (causes #1-4 above). Once direct connections work, the relay is bypassed automatically and you get full bandwidth.

Cause #6: Server IP Changed

If your Plex server’s local IP address changes (common with DHCP), the port forward points to the wrong device.

The Fix

Assign a static IP to your Plex server, either in your router’s DHCP reservation settings or directly on the server’s network configuration. Then update your port forwarding rule to match.

Testing Remote Access

After making changes, test from outside your network:

  1. Disconnect your phone from Wi-Fi (use cellular data)
  2. Open the Plex app and try to stream something
  3. Check the Plex Dashboard to confirm the connection type is “direct” not “relay”

You can also use an online port checker (search “check port 32400”) to verify the port is open from the internet.

Still Not Working?

If you’ve tried everything above and remote access still won’t cooperate, there’s likely something specific to your network setup that needs hands-on diagnosis. That’s exactly what our remote sessions handle — we screen-share into your setup, trace the actual network path, and fix it.