When it comes to remote access, there’s a lot of different factors which can impact your setup. Some are under your own control, others not so much.
First off… there’s a dedicated support article on troubleshooting your remote access. I strongly recommend you have a look at that.
Find below some additional remarks on how to troubleshoot your remote access setup.
Review your internet access / remote access configuration
- It’s good practice to review if Plex gets the correct public IP address of the main router in your home network.
- Make sure your router is configured to assign the same static local IP address to your PMS (e.g.
IP reservation) - Plex’ remote access depends on your home network to have a publicly routable IPv4 address. Common problems are environments where your ISP assigns only a private IPv4 address or no IPv4 address at all (some ISPs have started moving their network entirely to IPv6).
UPnP vs. manual port forwarding
Not all routers support manual port forwarding. Though based on experience in the forum, manual port forwarding seems to be more stable/reliable – there’s e.g. less remote access dropouts if the router shifts your UPnP connection to a different port.
Therefore, if possible, try to disable UPnP and establish a manual port forward to your router instead.
General configuration
Wording of those properties will vary depending on your router; some vendors e.g. use External/Internal instead of Public/Private.
| Property | Configuration |
|---|---|
| Protocol | TCP |
| Public IP | this will be the router’s public IP address (WAN IP); some routers expect it to be entered as a separate property anyway |
| Public Port | you’re free to pick this value… preferably pick one in the range of 20000 to 50000 to avoid accidental collisions |
| Private IP | <local IP of your PMS> |
| Private Port | 32400 |
http://portforward.com/ has a wide range of manuals on how to configure a manual port forward for specific routers.
What’s wrong?
If Plex’ remote access still isn’t working after enabling your manual port forward, it’s time to dig deeper. Test if you can see the router’s public IP and the specified public TCP port. You can do this using a service like canyouseeme.org.
This is usually another opportunity to verify if the public IP they see is the same seen by Plex and your router itself.
- If you can see your router, this implies the issue is inside your home network (between your router and the Plex Media Server, including both endpoints).
- If you cannot see your router, this implies the issue is outside your home network (between “the internet” / your ISP and your router)
(1) Common issues
-
Plex remote access settings show that it’s working… then it’ll lose access after a few seconds/minutes
Best way forward: Assume that your remote access setup isn’t working at all. Plex takes an „optimistic approach“ to displaying the remote access status — it’ll display that everything is working while still testing the status. This usually takes a few seconds… it’s not unheard of to take 20-30 seconds or in exceptions up to 1-2 minutes. -
Despite all the effort… reality shows that errors happen all the time (stupid typos, mismatching configurations…)
Best way forward: Double-check the manual port forward configuration of your router -
Anything VPN
Best way forward: The easiest way forward should be creating an exception for Plex to bypass the VPN. I take it that’s not a satisfying solution for some… which will leave you with lots of individual troubleshooting beyond this post/thread.
There’s e.g. a number of known “VPN helper tools” which will write IP addresses to the server’shostsfile that can give Plex some hiccups.
(2) Common “inside your home network” issues
-
Hierarchical home network configuration and segmentation getting in the way; some active network components create their own subnet inside your home network.
Best way forward:- Accidental segmentation: Review the configuration of your active network components (e.g. WLAN access points, other routers inside your home network). If possible, set them into “bridge mode” by disabling their built-in DHCP server. This way they should get their IP addresses from the main router and no longer form an obstacle for your remote access.
- On purpose: If you segmented your home network on purpose, review those configurations and make sure to forward the communication through ALL of those network (from the main router down to the subnet hosting your PMS).
This can also apply to containerized PMS setups which don’t use bridge network mode!
-
Security restrictions implied by firewalls or security tools
Best way forward: Temporarily disable such components one-by-one to figure out which of them is impacting the Plex remote access communication. If needed, adjust their configuration to allow -
Windows network profiles getting in the way → if you’re hosting your PMS on a Windows machine which has classified your network as
public, this can block it from allowing outside access to the PMS
Best way forward: Change the network classification toprivate.
How to change network settings from public to private? - Microsoft Q&A -
Bad Plex remote access configuration
Best way forward: Double-check your configuration matches that of the manual port forward; sometimes it can help to also look into the Plex network settings (e.g. some bad custom access URLs / certificates…).
(3) Common “outside your home network” issues
-
ISPs blocking certain ports…
Best way forward: You can attempt changing the public TCP port of your port forward… until you find one that works. Sometimes it’s enough to use a port different from32400, sometimes you have to go a long way. -
ISPs blocking certain traffic (some more advanced filtering)
Best way forward: Talk to your ISP
You don’t need a “static public IPv4” address for Plex remote access to work. That won’t stop many ISPs from offering such an option… usually for a steep price.
Do know there are sites like port checker that looks all open ports of you router (if you provide you router IP or ISP number). this will help to make it easier and not to have to go a long way before open unused port is found.