Remote access lost (even though Plex says accessible) after Windows 10 Reinstall

Hello all, I’m hoping someone can help me with my problem!

I was previously running Plex Media Server on my Windows 10 desktop PC for several months without issue, including remote access. My router uses UPNP, so the only thing I recall needing to do to set up remote access initially was to call my ISP and ask them to disable CGNAT.

Yesterday I reinstalled Windows 10 (and wiped everything), as I am turning the PC into a dedicated server. I’ve since reinstalled Plex, however remote access no longer works.

Confusingly, Plex App says “Fully accessible outside your network” in the Remote Access tab, however when I put my phone on 4G and try to watch something, I get “An error occurred while attempting to play this video. Please check your connection and try again”. The phone will play videos if connected to the local network, though.

I’m assuming that, since windows is the only thing that has changed, the solution must be related to a setting withing windows.

Things I’ve tried:

  • I’ve set the network connection to private.
  • I’ve added rules to windows firewall to allow Plex, and also disabled the firewall (briefly) to check if it is blocking the connection, but it didn’t help.
  • I added my ISP’s DNS servers to the network settings.

Can anyone think of anything else I can try?

Thanks in advance!

Server Version#: 1.41.6.9685-d301f511a
Player Version#: 1.108.1.307-dd5b87aa

First of all, check if port 32400 is pingable from outside. Go to those CanYouSeeMe websites.

Hmmm, CanYouSeeMe was unable to see me on 32400.

However, my router shows that UPnP is active, and it seems like it’s forwarded the port?

Just do a proper port forwarding and disable UPnP.

Is your server on IP 192.168.0.201? And is plex set to use port 28061 in your connection settings? Your router is listening at 28061 which might match what you have in your settings. So that’s what you should ping from the outside.

In Plex settings,
The private IP is 192.168.0.201, the port being used is 32400.
For the public IP, Plex is using port 28061.

So I guess that explains why it couldn’t see me earlier, but doesn’t solve my problem.

I’ll experiment with disabling UPnP and replacing it with manual port forwarding.
I checked Canyouseeme.org and it was able to see me on port 28061.

Would the manual port be internal 32400 / external 32400?

1 Like

You can choose the public port. Just the internal port is hardcoded based on what port the server itself is listening on the host machine.

You can use any external port. I just use 32400 so it’s consistent, and I know what it is right away.

Okay, I turned off UPnP and set up the manual port-forwarding for 32400/32400 and Plex started to work straight away. I’m still having some problems with certain files not playing, but I’m not sure whether that’s related to the remote access issue or not.

Certainly the solution was to use manual port forwarding, even though UPnP had worked fine in the past.

Thanks for your advice!

1 Like

I’ve been there. I started plex maybe 8 years ago. There was a time when I thought I had set up port forwarding correctly, but then realized later on that all my clients were connecting via UPnP doh! So basically my port forwarding rule was doing nothing and was actually a security issue lol. I was so angry at myself for not figuring it out, lol.

So I always tell people to disable UPnP and Plex Relay because it makes troubleshooting a lot harder and less reliable.

Are you getting an error when files don’t play?

No, just the infinitely-spinning circle. It’s only certain files though, so I thought at first something had gone wrong when I reinstalled and re-added the entire library, however I’ve since found that the Plex Desktop App seems to run perfectly - no problems.

The problem is only with the Plex Web app as well as the Samsung TV app and also the Android app (all on home network).

Let me know if you have any suggestions.

delete your Codecs folder, it will download a fresh batch.

A good thought, but no change unfortunately…

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.