Plex Media Server users have been grappling with a confusing error for years: \"Not available outside your network.\" But since April 29, 2025, a new subscription requirement has turned a straightforward network troubleshooting chore into a two-headed beast. The message itself still points to a connection failure between your server and the internet, yet many users are now hitting it because of a licensing change that has nothing to do with routers, firewalls, or port forwarding. If you’re suddenly locked out of your own media while away from home, you need to know which problem you’re actually solving.

What changed with Plex remote access?

On April 29, 2025, Plex quietly tightened access to personal video streams from outside the home. Before that date, anyone with a properly configured server could watch their movies and shows remotely for free. Now, remote video playback demands a paid subscription on either the server owner’s side or the viewer’s side. Specifically, one of the following must be true:

  • The server administrator has an active Plex Pass subscription.
  • The person watching has their own Plex Pass subscription.
  • The viewer purchases a Remote Watch Pass.

This requirement is entirely separate from the server’s Remote Access connectivity status. Music streamed through Plexamp and photos viewed in Plex Photos are exempt. But for most people running a home media library, remote video is the whole point. When the change rolled out, existing remote connections did not break immediately—but if the server’s remote access was disabled for any reason and then re-enabled, or if a viewer’s subscription lapsed, the familiar \"Not available outside your network\" warning began appearing even though the network was perfectly fine.

Is it a network problem or a billing problem?

The confusion is real. Plex’s interface does not offer separate error messages for a failed TCP handshake versus a blocked stream due to licensing. When a remote client tries to pull up a video and the server refuses to serve it, the user often sees the same remote access failure banner. The first critical diagnostic step is to open the Plex Web App on the server machine, navigate to Settings > Server > Remote Access, and look at the connection status.

  • If the page says \"Fully accessible outside your network\" (or briefly flashes green before returning to an error), your network configuration is correct, and the issue is almost certainly the subscription requirement.
  • If the status persistently stays \"Not available outside your network\" after retries, you have a genuine network obstacle.

To be absolutely sure, test with a non-video media type or check the behavior described by many users: the library loads over a cellular connection, but playing any video file immediately triggers a prompt about Plex Pass, Remote Watch Pass, or an ownership requirement. That’s the licensing wall, not a dead port.

What to do if it’s a billing issue

If the Remote Access status shows green but video playback still locks you out, your network is not at fault. You have three choices:

  1. The server owner can purchase a Plex Pass. This covers all users who stream from that server, and it unlocks additional features like hardware transcoding, downloads, and DVR functionality.
  2. Each remote viewer can buy their own Plex Pass.
  3. A viewer who only needs occasional access can get a Remote Watch Pass, which is a cheaper, a-la-carte option for temporary remote video access.

There is no workaround to bypass this requirement; Plex enforced it server-side. The company’s support pages and community forums make it clear that the subscription condition is permanent. If you’re philosophically opposed to paying for remote access to media you already own, you might consider alternative self-hosted platforms like Jellyfin, which offer free remote streaming. But for those staying within the Plex ecosystem, the fix is simply to add the appropriate subscription and restart the server—no router tweaking required.

How to fix actual remote access problems

When the Remote Access page genuinely reports \"Not available outside your network,\" you’re dealing with one of several classic network impediments. While the full, step-by-step guide published by MSPoweruser details every possible scenario, the essentials boil down to a handful of checks and actions. Here’s what you need to know to restore an external connection on a Windows 10 or Windows 11 machine.

Start with the obvious

Before touching your router, confirm that the Plex Media Server is running, signed in, and not asleep. On Windows, right-click the system tray icon and choose Open Plex. Under Settings > Server > General, verify the account and check for pending updates. Disconnect any VPN running on the server, as it can hijack outbound traffic and break the expected inbound route. Restart Plex and try enabling remote access again—sometimes the issue is transient.

Toggle automatic port mapping

Plex’s preference is to use UPnP or NAT-PMP to negotiate a port opening with your router automatically. If you’ve never manually configured anything, start here:

  1. In Remote Access settings, disable remote access, wait ten seconds, and re-enable it.
  2. If it fails, log into your router’s admin interface. Find the UPnP setting (often under Advanced, NAT, or WAN). Toggle it off, save, then back on. Some routers need a restart afterward.
  3. Restart Plex Media Server and try the automatic test again.

Automatic mapping is convenient but not reliable on every router. If UPnP is disabled for security reasons or simply doesn’t work, manual port forwarding is the next step.

Create a manual TCP port-forward

Plex Media Server listens on TCP port 32400. Your router needs to pass inbound traffic on that port (or another external port of your choice) to the server’s local IP address. Before you create the rule, reserve the server’s IP via a DHCP reservation in the router so it never changes. On Windows, run ipconfig in a terminal to confirm the current IPv4 address and default gateway.

Then, build the forwarding rule:

  • Name: Plex (or anything descriptive)
  • Protocol: TCP
  • External/WAN port: 32400, or a custom port like 32401 if 32400 is blocked
  • Internal/LAN port: 32400
  • Destination IP: the reserved IP of your server
  • Enabled: Yes

Save the rule, restart the router if required, and then go back to Plex’s Remote Access settings. Select Show Advanced, check Manually specify public port, and enter the external port you just configured. Hit Apply.

Important: Do not forward additional ports like 1900 (DLNA) or 32410-32414 (GDM discovery). Exposing those to the internet is a security risk, as Plex’s own documentation emphatically warns.

Call out Windows Firewall and third-party security

Even with a perfect router rule, Windows Firewall might be blocking the connection. The preferred method is to allow the Plex Media Server application rather than opening a blanket port:

  1. Go to Windows Security > Firewall & network protection > Allow an app through firewall.
  2. Click Change settings, then find Plex Media Server in the list. Enable it for the Private network profile (and only enable Public if you’re absolutely sure you’re on a public network and understand the risk).
  3. If the entry doesn’t exist, browse to the Plex executable and add it manually.

Also, check that Windows isn’t blocking all incoming connections. Under the active network profile, make sure the option Blocks all incoming connections, including those in the list of allowed apps is turned off. If you use a third-party firewall or antivirus suite, create an equivalent application exception there.

Untangle double NAT and carrier-grade NAT

If the Plex server still can’t be reached, your internet connection likely has two layers of NAT (Network Address Translation). This happens when an ISP modem/router combo sits in front of your own Wi-Fi router. The symptom: your router’s WAN IP address is a private address (like 192.168.x.x, 10.x.x.x, or 172.16-31.x.x) rather than a public one. You can compare the WAN address shown in your router with the public IP reported by any \"what is my IP\" service; a mismatch indicates double NAT.

Three fixes, ranked from best to worst:

  1. Bridge mode: Put the ISP gateway into bridge or passthrough mode, which disables its routing functions and hands the public IP directly to your personal router. You will then need to configure the port-forward only on your own router.
  2. Access point mode: If you’d rather keep the ISP device as the main router, switch your own router to access point or bridge mode so it stops performing NAT. The port-forward must then be created on the ISP gateway.
  3. Forward through both routers: A kludgy workaround. Forward the external port from the outer router to the inner router’s WAN address, then forward from the inner router to the server. This doubles the complexity and is fragile.

A worse scenario is carrier-grade NAT (CGNAT), where your ISP places you behind a large-scale NAT that you cannot control. The telltale sign is a WAN address in the 100.64.0.0–100.127.255.255 range, though other indicators exist. No manual port-forward on your router will help. You must call your ISP and request a public IPv4 address—some will provide one for free, others may require a business plan. Without it, remote access will only work via Plex’s slow relay service, if at all.

Eliminate other software conflicts

If you’ve done everything right but the status remains offline, scrutinize other software. Some routers have built-in security scanners that silently drop unsolicited inbound packets. ISP-level \"threat protection\" can do the same. Temporarily disable these to test, then create the narrowest possible exception. Ad blockers, DNS filters, and proxy clients can also interfere. And if Plex runs inside a virtual machine or container, double-check that the virtual network exposes TCP 32400 to the host.

Testing your connection properly

The only valid test is from outside your home network. Disconnect a phone from Wi-Fi, launch the Plex app over cellular data, and try to play media. If the library loads and music plays but video demands a subscription, you already know the answer. If nothing loads at all, and the Remote Access page in the server settings says \"Not available,\" your network fix hasn’t taken hold. Revisit the WAN IP comparison, confirm the port-forward rule is active, and verify that no VPN or security suite is interfering.

What this means for the future of Plex

The subscription pivot is part of a broader monetization strategy that has been unfolding for years. Per-lifetime Plex Pass buyers are insulated; everyone else now faces a recurring fee to watch their own collections from outside the home. For power users who invested hours into perfecting a free remote streaming setup, this feels like a rug pull. Alternative self-hosted media servers are gaining traction, and some users are already migrating. Plex’s bet is that convenience and features will outweigh the frustration. But as the community adapts, the line between a network error and a paywall will remain a critical troubleshooting fork—one that every Windows home server operator should understand before wasting an evening on router menus.