Fix Plex “Not Available Outside Your Network” With TCP 32400

The Plex Media Server message “Not available outside your network” means Plex cannot establish a direct inbound connection from the internet to your server. The fix is usually to restore automatic router mapping or create a TCP port-forward to the server’s local IP address. These instructions cover Plex Media Server on Windows 10, Windows 11, macOS, Linux, supported NAS devices, and NVIDIA SHIELD, with Windows-specific firewall steps included.
Before changing the network, note that since April 29, 2025, remote playback of personal video requires one of the following: the server administrator has Plex Pass, the viewer has Plex Pass, or the viewer has Remote Watch Pass. This subscription requirement is separate from the Remote Access connection status and does not apply to music in Plexamp or photos in Plex Photos.

Confirm the server and account are ready​

Start with these checks before editing firewall or router settings:

• Plex Media Server is running and local playback works.
• The server is signed in to the correct Plex account.
• The computer or NAS is not asleep.
• The server and router both have working internet access.
• The server is not connected through a VPN that forces all traffic through the VPN tunnel.
• You have administrator access to the router.
• You know whether the internet connection uses one router, two routers, or an ISP gateway plus a personal router.

To check the server:

1. Open Plex Web App from the server computer. On Windows, right-click the Plex Media Server icon in the notification area and select Open Plex.
2. Select Settings.
3. Choose the correct server in the left pane.
4. Open General under the server name.
5. Confirm that the server is signed in to your Plex account.
6. Check the displayed server version. If Plex offers a public server update, install it and restart Plex Media Server when prompted.
7. Open Remote Access under the server name.

If the page briefly reports that the server is accessible and then returns to Not available outside your network, continue with the network checks below.

Retry Plex automatic Remote Access​

Plex first tries to configure the router automatically using UPnP or NAT-PMP. This is the simplest configuration when the router supports it correctly.

1. In Plex Web App, go to Settings > Server > Remote Access.
2. If Remote Access is enabled, select Disable Remote Access.
3. Wait approximately 10 seconds.
4. Select Enable Remote Access.
5. Allow Plex time to test the connection.

If the status remains unavailable:

1. Sign in to the router’s administration page or app.
2. Locate its UPnP, NAT-PMP, or automatic port-mapping setting.
3. Confirm that the feature is enabled.
4. If it was already enabled, turn it off, save the setting, and then turn it back on.
5. Restart the router if its documentation requires it.
6. Restart Plex Media Server.
7. Return to Settings > Server > Remote Access and select Retry.

Router menu names vary. UPnP may appear under Advanced, NAT, WAN, Network, or Security.
Automatic mapping is convenient, but it is not required. If UPnP is disabled for security reasons, is unreliable, or is unavailable on the router, use a manual port-forward instead.

Give the Plex server a reserved local IP address​

A manual port-forward must always point to the same device. If the router later assigns a different local IP address to the Plex server, the forwarding rule will stop working.
The preferred fix is a DHCP reservation in the router rather than a manually configured address in Windows.

1. Open the router’s administration page or app.
2. Find the connected-device or DHCP client list.
3. Locate the computer, NAS, or SHIELD running Plex Media Server.
4. Record its current local IPv4 address, such as 192.168.1.50.
5. Select the option named Reserve IP, Address Reservation, Static Lease, DHCP Reservation, or similar.
6. Reserve the current address for that device.
7. Save the configuration.
8. Restart the server device if the router requires it.

To confirm the address on Windows:

1. Open Windows Terminal, PowerShell, or Command Prompt.
2. Run:

ipconfig

1. Find the active Ethernet or Wi-Fi adapter.
2. Record its IPv4 Address and Default Gateway.

The default gateway is normally the address used to open the router’s administration interface. Do not assume that every router uses 192.168.0.1 or 192.168.1.1.

Create the manual TCP port-forward​

Plex Media Server listens internally on TCP port 32400. The router’s external port can also be 32400, but Plex allows a different available external port, typically in the 20000 through 50000 range.
Warning: Forward only the required TCP port to the Plex server. Do not place the server in the router’s DMZ, enable router administration from the internet, or expose Plex’s discovery and DLNA ports.

1. Sign in to the router’s administration page or app.
2. Open Port Forwarding, Virtual Server, NAT Rules, or the equivalent page.
3. Create a new rule with these values:
   • Name: Plex
   • Protocol: TCP
   • External/WAN port: 32400, or another available port such as 32401
   • Internal/LAN port: 32400
   • Destination IP: The reserved local IPv4 address of the Plex server
   • Enabled: Yes
4. Save or apply the rule.
5. Restart the router only if its interface or documentation requires it.
6. Open Plex Web App.
7. Go to Settings > Server > Remote Access.
8. Select Show Advanced if the manual-port option is not visible.
9. Select Manually specify public port.
10. Enter the external port configured in the router. If the router maps external port 32401 to internal port 32400, enter 32401 in Plex.
11. Select Apply or Retry.

The internal port must remain TCP 32400. Do not enter the custom external port as the internal port unless it also happens to be 32400.
If you run multiple Plex servers behind the same router, each one requires a different external port:

• Server 1: external TCP 32401 to internal TCP 32400
• Server 2: external TCP 32402 to internal TCP 32400

Each rule must point to the corresponding server’s reserved local IP address.

Allow Plex through Windows Firewall​

Microsoft recommends allowing the application through Windows Firewall rather than permanently opening a broad firewall port. An application exception is active only when the allowed program needs it.

1. Open Start and search for Windows Security.
2. Select Firewall & network protection.
3. Select Allow an app through firewall.
4. Select Change settings and approve the administrator prompt.
5. Find Plex Media Server in the list.
6. Enable it for the network profile used by the server.

A home network should normally be configured as Private. Do not enable the Public profile unless the server genuinely operates on a network Windows classifies as public and you understand the increased exposure.
If Plex Media Server is not listed:

1. Select Allow another app.
2. Select Browse.
3. Locate the installed Plex Media Server executable. The location can differ if Plex was installed to a custom folder.
4. Add the application.
5. Enable it for the appropriate network profile.
6. Select OK.

Also check whether Windows is blocking all inbound connections:

1. Open Windows Security > Firewall & network protection.
2. Select the active network profile.
3. Confirm that Blocks all incoming connections, including those in the list of allowed apps is not enabled.

If a third-party security suite controls the firewall, configure the exception there instead. Avoid leaving the firewall or antivirus disabled. A temporary disable can identify the cause, but the permanent fix is a specific application or TCP 32400 rule.
To roll back the Windows exception, return to Allow an app through firewall, select Change settings, clear the Plex entry, and select OK.

Detect and fix double NAT​

Double NAT occurs when two devices are performing routing and address translation. A common example is an ISP modem/router connected to a separate Wi-Fi or mesh router. A correct port-forward on the inner router may still be unreachable because the outer router blocks it.
To detect it:

1. Open the administration page for the router directly connected to the Plex server.
2. Find its WAN, Internet, or External IPv4 address.
3. Compare that address with the public IPv4 address reported by a reputable IP-checking service.
4. If the addresses differ, another NAT layer probably exists.

Common private WAN addresses include:

• 10.x.x.x
• 172.16.x.x through 172.31.x.x
• 192.168.x.x

You can resolve double NAT in one of three ways:

Put the ISP gateway in bridge or passthrough mode​

This is normally the cleanest fix when you want your personal router to manage the network.
Warning: Bridge mode can disable the ISP gateway’s Wi-Fi, routing, firewall, and connected-device functions. Record the current configuration first, and confirm that your personal router is ready to receive the internet connection.

1. Open the ISP gateway’s administration interface.
2. Locate Bridge Mode, Modem Mode, or IP Passthrough.
3. Enable the appropriate mode.
4. Connect the personal router’s WAN port as directed by the ISP.
5. Restart the gateway and personal router.
6. Confirm that the personal router now receives the public IPv4 address.
7. Retest Plex Remote Access.

To roll back, disable bridge or passthrough mode and restore the previous cabling and router settings.

Put the secondary router in access-point mode​

Use this approach when you want the ISP gateway to remain the main router.

1. Open the secondary router or mesh system’s settings.
2. Enable Access Point Mode, Bridge Mode, or its equivalent.
3. Apply the change and allow the network to restart.
4. Recreate the Plex port-forward on the ISP gateway, pointing to the Plex server’s new reserved address.
5. Retest Remote Access.

Forward through both routers​

This is a workaround when neither device can be placed in bridge or access-point mode.

1. On the outer router, forward the chosen external TCP port to the WAN address of the inner router.
2. On the inner router, forward that same TCP port to internal port 32400 on the Plex server.
3. Enter the external port in Plex under Manually specify public port.
4. Retest the connection.

This configuration works but is harder to maintain than removing the second NAT layer.

Check for carrier-grade NAT​

Carrier-grade NAT, or CGNAT, means the ISP shares one public IPv4 address among multiple customers. You cannot fix CGNAT with a normal router port-forward because the ISP controls the outer NAT device.
Plex identifies the range 100.64.0.0 through 100.127.255.255 as a common sign of CGNAT. A different router WAN address from the public address can also indicate CGNAT even when that specific range is not shown.
If CGNAT is present:

1. Contact the ISP.
2. Ask whether the connection uses CGNAT.
3. Request a public IPv4 address or a static IPv4 option.
4. After the ISP changes the connection, restart the modem, router, and Plex server.
5. verify the router now receives the public IPv4 address.
6. Retest the manual port-forward.

If the ISP will not provide a public IPv4 address, Plex Relay may permit limited remote access, but it is a workaround rather than a direct Remote Access fix. Relay has lower performance and may not support the desired remote streaming quality.

Eliminate VPN, proxy, and security conflicts​

A VPN running on the Plex server can send Plex’s outbound traffic through one address while the router accepts inbound connections on another. That breaks the expected connection path.

1. Temporarily disconnect the VPN on the Plex server.
2. Restart Plex Media Server.
3. Select Retry under Settings > Server > Remote Access.
4. If Remote Access works, configure the VPN client’s split-tunneling feature to exclude Plex Media Server.
5. Reconnect the VPN and test again.

The exact split-tunneling procedure depends on the VPN provider. If the VPN does not support application exclusions or inbound port forwarding, it may be incompatible with direct Plex Remote Access.
Also inspect:

• Router security services that block unsolicited inbound connections
• ISP security products such as gateway-level threat protection
• Ad-blocking or DNS-filtering software on the server
• Proxy settings
• Container or virtual-machine networking that does not expose TCP 32400 to the host network

Disable a security feature only long enough to test it. If it is responsible, create the narrowest supported exception and turn protection back on.

Verify the fix from outside the home network​

Do not test remote access while the player remains connected to home Wi-Fi; that only verifies local access.

1. Leave Plex Media Server running.
2. On a phone, turn off Wi-Fi so it uses cellular data.
3. Open the Plex app and sign in.
4. Select the home server.
5. Play a small media item.
6. Return to Plex Web App on the server and open Settings > Server > Remote Access.
7. Confirm that Plex reports the server as fully accessible outside the network.

If the library opens but video playback requests a subscription, the network connection is working; check the Plex Pass or Remote Watch Pass requirement separately.
If the status remains unavailable after a correct firewall rule, reserved address, and port-forward, compare the router’s WAN address with the public IPv4 address again. A mismatch points to unresolved double NAT or CGNAT. If the addresses match, collect the router model, Plex Media Server version, external and internal port mapping, server local IP address, and Plex server logs before escalating to the router manufacturer, ISP, or Plex support forum.

---

References​

1. Primary source: MSPoweruser
   Published: 2026-07-14T19:56:14+00:00
   
   

   How to Fix Plex "Not Available Outside Your Network" Error

   There is nothing more frustrating than settling into a hotel room, opening your phone, and realizing your home media library is completely unreachable. The “Not Available Outside Your Network” error is one of the most common issues Plex Media Server users face. When your Plex server...

   mspoweruser.com
2. Related coverage: support.plex.tv
   
   

   What network ports do I need to allow through my firewall? | Plex Support

   Note: This article is discussing ports in the local firewall of the computer running Plex Media Server. This is not...

   support.plex.tv