Plex Not Available Outside Your Network? 9 Fixes

The “Not available outside your network” message means Plex Media Server is working locally but cannot establish a direct connection with devices outside your home network.

Your libraries may still appear normally on your TV or computer at home. However, playback can fail when you switch to mobile data, travel, or share the server with someone elsewhere.

In most cases, the solution is to give the Plex server a fixed local IP address and forward one TCP port from your router to that device:

External port: 32400
Internal port: 32400
Protocol: TCP
Destination: Your Plex server’s local IP address

If this does not work, your ISP may be using double NAT or Carrier Grade NAT, commonly called CGNAT.

Quick fix: Open Plex on the server, go to Settings > Server > Remote Access, and click Retry. If automatic configuration fails, reserve the server’s local IP address and manually forward TCP port 32400 to it.

Check this before changing your router

Since April 29, 2025, remote playback of personal video content is no longer available completely free on affected Plex apps.

At least one of these conditions must now be met:

• The Plex Media Server administrator has Plex Pass.
• The person watching has Plex Pass.
• The person watching has a Remote Watch Pass.

When the server administrator has Plex Pass, other people with access to that server can also stream its video libraries remotely without buying their own subscription. The rule does not apply to music streamed through Plexamp or photos accessed through Plex Photos. (Plex Support)

This subscription requirement is separate from the “Not available outside your network” warning. You must first establish Remote Access and then have an eligible subscription for remote video playback.

Why Plex is unavailable outside your network

The error usually has one of the following causes:

Symptom	Likely cause
Plex works at home but not on mobile data	Remote Access or port forwarding is not configured
Remote Access turns green and then red	Dynamic local IP, unreliable UPnP, double NAT, or firewall interference
Port forwarding appears correct but remains inaccessible	CGNAT, double NAT, VPN, or incorrect destination IP
Remote videos play at very low quality	Plex is probably using Relay
Server appears offline everywhere	Plex Media Server may not be running or signed in
Remote Access is green but video will not play	Subscription or client playback issue
Plex thinks a device at home is remote	Multiple subnets, VPN, DNS-rebinding protection, or container networking

Follow the fixes below in order. Do not start changing advanced router settings until you confirm that Plex works on the server itself.

1. Confirm that Plex Media Server is running locally

Perform the initial checks on the computer or NAS that hosts Plex.

On the server computer, open:

http://127.0.0.1:32400/web

This opens the local version of Plex Web App without depending on remote discovery. Plex documents this address as the local setup page for Plex Media Server. (Plex Support)

If the page does not open:

1. Restart Plex Media Server.
2. Restart the computer or NAS.
3. Check whether another application is using port 32400.
4. Install the latest stable Plex Media Server update.
5. Confirm that the server service starts automatically after a reboot.

Do not troubleshoot your router until the local page opens and your libraries appear.

2. Sign the server into the correct Plex account

Remote Access requires Plex Media Server to be signed in.

In Plex Web App:

1. Open Settings.
2. Select Server > General.
3. Confirm that the server is signed in.
4. Verify that it is linked to the account you intend to use.
5. Claim the server if Plex displays that option.

Then open:

Settings > Server > Remote Access

Click Enable Remote Access or Retry.

Plex first tries to configure the router automatically through UPnP or NAT-PMP. If the router supports one of these protocols and nothing else blocks the connection, the status should change to Fully accessible outside your network. (Plex Support)

3. Restart Plex’s automatic Remote Access configuration

A temporary router mapping can become stale after a router restart, server update, or local IP-address change.

Try resetting it:

1. Open Settings > Server > Remote Access.
2. Select Disable Remote Access.
3. Wait approximately 20 seconds.
4. Select Enable Remote Access.
5. Allow Plex up to a minute to test the connection.

Restart the router and Plex server if the status remains red.

Automatic configuration depends on UPnP or NAT-PMP. Look for one of these settings in your router’s administration page:

• UPnP
• NAT-PMP
• Automatic Port Mapping
• Universal Plug and Play

Enable only one automatic port-mapping method when possible. If automatic access remains unreliable, use a manual port forward instead.

4. Give the Plex server a permanent local IP address

Port forwarding sends incoming connections to a specific device. If your router later assigns a different IP address to the Plex server, the forwarding rule will point to the wrong device.

Find the server’s current address.

On Windows:

1. Press Windows key + R.
2. Enter cmd.
3. Press Enter.
4. Run:

ipconfig

Look for IPv4 Address under the active Ethernet or Wi-Fi adapter. It will typically resemble:

192.168.1.50

The best solution is usually to create a DHCP reservation in the router. Depending on the manufacturer, it may be called:

• Address Reservation
• Static Lease
• Reserved IP
• DHCP Binding
• IP and MAC Binding

Reserve the current address for the Plex server’s network adapter. Plex also recommends reserving the server’s IP through the router so the address does not change. (Plex Support)

5. Forward Plex port 32400 manually

Open your router’s administration page and find a section named Port Forwarding, NAT, Virtual Server, or Applications and Gaming.

Create the following rule:

Router field	Value
Name	Plex
Protocol	TCP
External or public port	32400
Internal or private port	32400
Internal IP	The Plex server’s reserved local IP
Enabled	Yes

Plex allows you to choose a different external port, generally in the range of 20000 to 50000. However, the internal destination port must always be TCP 32400. (Plex Support)

For example, this is valid:

External TCP port: 28765
Internal TCP port: 32400
Internal IP: 192.168.1.50

This is not valid:

External TCP port: 28765
Internal TCP port: 28765

After saving the router rule:

1. Return to Plex > Settings > Server > Remote Access.
2. Select Show Advanced.
3. Enable Manually specify public port.
4. Enter the external port used in the router.
5. Click Apply or Retry.

The Plex field must contain the external port. If the manual-port checkbox is not enabled, Plex will continue attempting automatic mapping and may report that Remote Access failed. (Plex Support)

Example configurations

When using 32400 externally:

Internet:32400 → 192.168.1.50:32400 TCP

When using a custom external port:

Internet:28542 → 192.168.1.50:32400 TCP

Do not forward Plex’s discovery, DLNA, or companion ports to the internet. Plex identifies TCP 32400 as the required server port and advises against exposing its additional local-network ports. (Plex Support)

6. Allow Plex through the server’s firewall

The forwarding rule may be correct while the firewall on the server refuses the connection.

Allow Plex through Windows Firewall

1. Open Windows Security.
2. Select Firewall & network protection.
3. Choose Allow an app through firewall.
4. Select Change settings.
5. Find Plex Media Server.
6. Allow it on the appropriate network profiles.
7. Save the changes and restart Plex.

If Plex Media Server is missing, select Allow another app and locate its executable.

You can alternatively create an inbound TCP rule for port 32400 under:

Windows Security
> Firewall & network protection
> Advanced settings
> Inbound Rules
> New Rule

Microsoft recommends allowing the application rather than disabling the entire firewall. Opening a permanent port creates more exposure than allowing a specific trusted application. (Microsoft Support)

Plex officially identifies inbound TCP 32400 as the essential firewall requirement for access to Plex Media Server. (Plex Support)

Do not switch off Windows Firewall or antivirus protection simply to make Plex work.

7. Check for double NAT

Double NAT occurs when two devices are acting as routers.

A common configuration looks like this:

Internet
   ↓
ISP modem/router
   ↓
Personal Wi-Fi router
   ↓
Plex server

Your forwarding rule may exist on the personal router, but incoming traffic first reaches the ISP router and stops there.

How to detect double NAT

1. Open your router’s status page.
2. Find its WAN, Internet, or External IPv4 address.
3. Check your current public IPv4 address through a reputable IP-checking service.
4. Compare the two addresses.

If they match, ordinary double NAT is unlikely.

If they do not match, another NAT layer probably exists between your router and the internet. Plex recommends this comparison as its primary double-NAT test. (Plex Support)

How to fix double NAT

The cleanest options are:

• Put the ISP modem/router into bridge mode.
• Put your personal router into access-point or bridge mode.
• Forward the Plex port through both routers.
• Ask the ISP to help remove the extra NAT layer.

When forwarding through both devices, the ISP router should forward the external port to your personal router’s WAN address. Your personal router must then forward that port to the Plex server’s local address. (Plex Support)

8. Determine whether your ISP uses CGNAT

Carrier Grade NAT allows an ISP to place many customers behind one public IPv4 address. Because you do not control the ISP’s NAT device, ordinary port forwarding on your own router cannot create a direct inbound connection.

Check the WAN address displayed by your router. Plex identifies this range as a strong indication of CGNAT:

100.64.0.0 to 100.127.255.255

A mismatch between the router’s WAN address and your publicly visible address can also indicate CGNAT. (Plex Support)

Contact your ISP and ask:

“Is my connection behind CGNAT, and can you provide a public IPv4 address that supports inbound port forwarding?”

Depending on the provider, it may offer:

• A free public dynamic IPv4 address
• A paid public IPv4 option
• A static IP subscription
• Removal from CGNAT upon request

Plex’s documented solution for CGNAT is to ask whether the ISP can provide a static public IP address that bypasses it. (Plex Support)

If the ISP cannot provide a public address, Plex Relay may still permit limited remote access.

9. Disconnect VPN software on the Plex server

A VPN can change which network interface and public address Plex advertises.

Disconnect the VPN temporarily, restart Plex Media Server, and click Retry under Remote Access.

Also check:

Settings > Server > Network > Show Advanced

If Preferred network interface is available, select the Ethernet or Wi-Fi adapter connected directly to the home router.

Plex provides this option for servers with multiple adapters, including NAS and container installations, so clients receive the correct connection address. Plex also warns that automatically mapped ports may still use a different interface from the one selected. (Plex Support)

A commercial VPN will only support direct Plex access when it specifically provides port forwarding and the configured VPN port is mapped correctly. Merely connecting to another VPN location does not solve CGNAT.

10. Check whether Plex is using Relay

Plex Relay is a fallback that carries the stream through Plex infrastructure when an app cannot connect directly to your server.

Relay can make remote playback work even while the Remote Access screen says the server is not directly available. However, Relay has significant restrictions:

• Streams are limited to a maximum of 2 Mbps.
• The limit applies to Plex Pass and Remote Watch Pass subscribers.
• Plex Downloads cannot operate over Relay.
• High-bitrate media may need to be transcoded.
• Not every Plex client supports Relay. (Plex Support)

Check the setting under:

Settings > Server > Network > Show Advanced > Enable Relay

Relay is enabled by default. It also requires Secure connections to be set to Preferred or Required. Plex recommends the default Preferred option for most users. (Plex Support)

Relay is useful as a temporary fallback, but a direct connection provides better quality and efficiency.

Plex Remote Access turns green and then red

A status that repeatedly changes between Fully accessible outside your network and Not available outside your network usually points to an unstable mapping rather than a completely offline server.

Check these items:

1. Confirm that the server still has the same local IP.
2. Replace automatic UPnP mapping with a manual port forward.
3. Confirm that the external port in Plex matches the router rule.
4. Look for a second router or CGNAT.
5. Disconnect VPN software.
6. Restart the router after saving the rule.
7. Check whether an advanced firewall is rejecting Plex’s connection test.
8. Disable jumbo frames if the network MTU is above 1500.

Plex notes that jumbo frames can produce a green Remote Access status even though the server remains inaccessible from outside. It recommends returning to the standard 1500-byte MTU when troubleshooting. (Plex Support)

Test Plex from a genuinely external connection

Do not test remote access while the phone or laptop remains connected to the same home Wi-Fi.

A proper test is:

1. Leave Plex Media Server running.
2. Disable Wi-Fi on your phone.
3. Connect through mobile data.
4. Open the Plex app.
5. Select a video from your personal library.
6. Open playback information and check the connection type.

A Direct or Remote connection means the port-forwarding setup is working.

An Indirect connection generally means Plex is using Relay.

If the library does not appear, confirm that the phone is signed into an account with access to that server.

Plex says the server is remote while you are at home

This is a separate but related problem. Plex considers playback remote when the client cannot make a local connection to the server on the same subnet.

Potential causes include:

• The server and player are on different VLANs or subnets.
• Guest Wi-Fi prevents devices from communicating.
• A VPN is active.
• Router DNS-rebinding protection interferes with Plex discovery.
• Local-network permissions are disabled on the client.
• Plex is running in a container without appropriate host networking.
• A firewall blocks communication between local devices.

Plex specifically identifies multiple subnets, DNS-rebinding restrictions, privacy settings, VPNs, and container networking as configurations that can make a local device appear remote. (Plex Support)

Connect both devices to the same primary network and temporarily disconnect any VPN. On an iPhone or iPad, also verify that Plex has permission to access the local network.

Settings that will not fix the problem

Avoid these risky or ineffective approaches:

Do not place the Plex server in the router’s DMZ

DMZ mode can expose far more services than Plex requires. A single, correctly targeted TCP port forward is safer.

Do not forward every Plex-related port

Only TCP 32400 is required for access to Plex Media Server. Other Plex ports are used for local discovery, DLNA, or companion features and should not be opened broadly to the internet. (Plex Support)

Do not disable your firewall permanently

Create a narrow application exception or TCP rule instead.

Do not use UDP for the main forward

The Remote Access rule for the Plex server must use TCP.

Do not enter the custom external port as the internal port

Regardless of the external port chosen, the internal destination remains 32400.

Do not assume buying Plex Pass fixes port forwarding

Plex Pass or Remote Watch Pass addresses remote-playback eligibility. It does not remove CGNAT, create a router rule, or open a blocked firewall port.

Frequently asked questions

What port does Plex use for Remote Access?

Plex Media Server uses TCP port 32400 internally. You can also choose another external port, generally between 20000 and 50000, but that port must forward to internal TCP 32400. (Plex Support)

Does Plex Remote Access require Plex Pass?

Remote browsing can be enabled without Plex Pass, but remote playback of personal video on affected Plex apps now requires Plex Pass or Remote Watch Pass. If the server administrator has Plex Pass, other users of that server can remotely stream its video libraries without buying their own subscription. (Plex Support)

Can CGNAT stop Plex Remote Access?

Yes. CGNAT prevents you from controlling the public-facing NAT layer, so a port forward created on your home router cannot normally accept a direct incoming connection. Ask the ISP for a public IPv4 address or use Plex Relay with its limitations. (Plex Support)

Why does Plex work at home but not away from home?

Local playback does not need an inbound internet connection. Remote playback requires Plex Media Server to be reachable through your router, firewall, and ISP connection.

Can Plex work without port forwarding?

Automatic UPnP or NAT-PMP can create the mapping instead. Plex Relay may also provide an indirect connection when direct access fails, but it is limited to 2 Mbps and does not support remote downloads. (Plex Support)

Should I use port 32400 externally?

Using 32400 externally is the simplest configuration, but it is not mandatory. A custom external port can be forwarded to internal TCP 32400 and entered under Manually specify public port.

Final verdict

The most dependable fix for Plex not being available outside your network is a manual port-forwarding configuration:

Reserved Plex server IP: 192.168.1.50
External port: 32400
Internal port: 32400
Protocol: TCP

After creating the rule, enable Manually specify public port in Plex and enter the same external port.

If the connection still fails, compare the router’s WAN address with your public IPv4 address. A mismatch usually indicates double NAT or CGNAT. Bridge the extra router, forward through both NAT devices, or ask the ISP for a public IPv4 address.

Finally, remember that fixing Remote Access does not by itself unlock remote video playback. Current Plex requirements also call for Plex Pass or Remote Watch Pass on affected apps, either through the server administrator or the person watching.