Plex troubleshooting guide

Plex Remote Access Not Working: Diagnose the Path Before Changing Settings

Category: Remote Access Troubleshooting

plex remote access not working.

Plex remote access fails at one of four layers: the Plex account entitlement, the Plex host, the router/ISP path, or the client playback decision. Test them in that order. Do not change the library or reinstall Plex until you know which layer fails.

1. Check the remote video entitlement first

Before changing a router, check whether the affected client is allowed to play video remotely at all. Plex’s official requirements apply to personal video streamed outside the server’s local network. For an affected app, at least one of these must be true:

  • The Plex Media Server admin account has an active Plex Pass.
  • Your Plex account has an active Plex Pass.
  • Your account has an active Remote Watch Pass.

The restriction applies to personal video, not music streamed to Plexamp or photos in Plex Photos. Plex currently lists Android and iOS mobile, PlayStation, Plex for Windows/Mac/Linux, Roku, supported smart TVs, the web app, and Xbox as affected platforms; more apps may enforce the requirement later. Check the account actually signed in on the client, not only the server owner’s account.

Official source: Requirements for Remote Playback of Personal Media. If the client is not entitled, fix the account/subscription first; port forwarding will not change the result. If it is entitled, continue to the network layers.

2. Record the exact failure

Open Plex Web → Settings → Remote Access. Write down the public address/port, whether it says Fully accessible, and the time. Then take the phone off Wi-Fi, use cellular, and try one title. “Works at home” is not a remote-access pass.

3. Separate double NAT from CGNAT

Double NAT is two NAT devices in your own path: for example, an ISP modem/router doing NAT and your own Wi-Fi router doing NAT again. The server’s router WAN address is a private address, but the internet sees a different public address. You can often fix this by putting one device in bridge mode or by forwarding the port through both NAT devices.

CGNAT is NAT operated by the ISP for many customers. Your router may show a WAN address in the shared carrier range 100.64.0.0/10 — specifically 100.64.0.0–100.127.255.255 — while the public internet address is different. Port forwarding on your router cannot fix CGNAT. Ask the ISP for a public IPv4 address, or use a private path such as Tailscale or Plex Relay.

Plex’s own troubleshooting article describes the same test: compare the router’s WAN/Internet address with the address shown by an external IP-check site. If they differ, suspect double NAT or CGNAT; a carrier-range address identifies CGNAT. Source: Plex: Troubleshooting Remote Access. The 100.64.0.0/10 range is defined in RFC 6598.

4. Check connection type separately from playback type

These are two different questions and must not be conflated:

  • Connection: Plex Dashboard may show Direct or Indirect. “Indirect” usually means the stream is going through Plex Relay (or another indirect path); it does not automatically mean the video is transcoding.
  • Playback — Direct Play: the client supports the file container, video codec, audio codec, resolution, and bitrate, so the file is sent as-is without changing the media.
  • Playback — Direct Stream: the client supports the video and audio streams but not the file container. The server extracts the original streams and repackages them into a compatible container on the fly. If only the container changes and the original video and audio streams are preserved, this is Direct Stream, not Transcode. A “partially transcoded direct stream” may convert only the audio while leaving the video untouched.
  • Playback — Transcode: the client cannot handle the video or audio stream, so the server converts the incompatible track (and may also change resolution or bitrate). This is the CPU-intensive case.

In Plex Dashboard → Now Playing, read the connection field and the playback decision as separate facts. A relayed stream can still be Direct Play; a direct connection can still be Direct Stream or Transcode because of container, codec, subtitle, or client limits. A green Remote Access page is not acceptance, and “Direct” is not the same as “Direct Play.”

Official definitions: Plex: Direct Play, Direct Stream, Transcoding Overview and Plex: Streaming Media — Direct Play and Direct Stream.

5. Choose one path

Tailscale: install it on the Plex host and the client, sign into the same tailnet, and browse to the host’s Tailscale IP on port 32400. This avoids router changes but requires the Tailscale app on the client.

Only run CLI commands on devices that actually provide a Tailscale command line: Windows, macOS, or Linux. Phones, tablets, TVs, and consoles use the app UI, not a shell. On a CLI-capable Plex host or client, verify the address and route with:

tailscale ip -4
tailscale status
tailscale ping <peer-name-or-tailscale-ip>

Use the 100.x.y.z address returned by tailscale ip -4 on the Plex host, and confirm the client appears in tailscale status. On a phone, use the Tailscale app’s device list and connection status instead. Tailscale CLI reference: Tailscale CLI documentation.

Port forward: only when the ISP gives a real public IPv4 address. Reserve the host IP, forward TCP 32400 to it, and set the same public port in Plex. Never expose the whole PC.

Reverse proxy: only when you need a hostname and HTTPS for several users. It adds DNS, certificate, and proxy layers; test it after the direct path works.

6. Retest from outside

Use cellular data, play for at least two minutes, and check Plex Dashboard → Now Playing. Record two separate fields:

  • Connection: Direct or Indirect.
  • Playback: Direct Play, Direct Stream, or Transcode.

Do not write “Direct” for both. A Direct connection with Direct Stream is a different result from Direct Play, and either can still be a problem if the client or network cannot sustain it. Also note the client app and account used. A green Remote Access page alone is not acceptance.

7. Rollback

Remove only the change you made: stop Tailscale, delete the one port-forward rule, or disable the proxy host. Confirm local playback still works. Keep a note of the original router/Plex values.

Need help with your exact path?

If the entitlement is active and the path is still unclear, send the Plex host OS, client device, connection type, playback type, and what happens on cellular. Do not send passwords.

Request a quote for your Plex setup

Sources

  • Plex: Requirements for Remote Playback of Personal Media
  • Plex: Troubleshooting Remote Access
  • Plex: Remote Streaming (Setting Up Remote Access)
  • Plex: Direct Play, Direct Stream, Transcoding Overview
  • Plex: Streaming Media — Direct Play and Direct Stream
  • RFC 6598: Shared Address Space (100.64.0.0/10)
  • Tailscale CLI documentation

Service scope and pricing · Ask about this exact symptom