Have you setup port forwarding on your router? If I had to guess that could be the problem.
1 Like
I have unfortunately. I have also rebooted my server and computer
The behavior you’re seeing is what I’d expect if the traffic was not making it through your router to your PMS. You should get a certificate error, but the browser should give you the option to proceed anyway. From there, it should allow you to sign in as usual.
Can you post a complete screenshot of the port forwarding rule you set up? Also, you only have one router on your network, right? No ISP router/modem combo plus your own.
Okay, also check any local firewall software and ensure the port is allowed for inbound connections
1 Like
If you haven’t done so, you might also mention who your ISP is. Some of them are better than others about allowing port access to your IP. Sometimes you need to turn off their protection services.
1 Like
That’s correct! And this is the full rule
I’ve checked my firewall and my ISP is Comcast
It should also ask you which internal IP address to send that traffic. Is that on a different screen? That IP address should be the IP address of your PMS.
I can’t see the destination IP (the internal IP the rule forwards traffic to) in that screenshot. Do you have your server on a static IP, and the destination IP set properly?
Also a random note, I believe Plex only needs TCP forwarding (I’m sure someone else could confirm that).
Yes, only TCP is needed.
1 Like
It actually doesn’t ask me which IP address to send it to, but I did make sure to set up a rule:
That’s your Windows IP configuration. Somewhere in your router’s port forward configuration for the rule you showed above you should need to enter that IP address. Do you have a screenshot of that?
For example, here’s mine:
Yours will obviously look different, but there are always 4 important pieces to a rule:
- The port the traffic hits the router on
- The internal IP address
- The internal port
- The protocol
1 Like
Okay, might be worth trying to set your local ip for your server as static on the router matching the port forward local ip and then change the windows config to automatic obtain.
But definitely check with your ISP, they may block port forwarding and they might need to allow it for you.
Perhaps you need to create a rule in Windows Defender Firewall settings to allow Plex Media Server.
My remote access stopped recently and I found both rules had been set to block (this may be due to a recent reinstall of malwarebytes) but its a good thing to check anyway.
Checked it again just to make sure and it isn’t being blocked.
I can’t figured out how to get to IP forwarding in Comcast. Any suggestions would help
I believe you mean “Port” forwarding not IP forwarding. Port forwarding is not done at the ISP level, that is Comcast has no direct roll in it. Port forwarding is accomplished on your router and exactly how that is done depends on the router make and model and the firmware you are running on the router.
By looking at your log, I took the liberty to check if your PMS could be reached from the outside, and it could!
So, and unsure here, but guess that somehow something goes wrong when your PMS tries to update it’s record at plex.tv, so try this:
- In PMS settings, disable remote access
- Wait 2 min, and then reenable
- Wait for 2 more additional minutes, and then if still not avail outside, upload a fresh set of logs
And Sidenote, your server version is behind here 
1 Like
Thanks for your help @dane22 I appreciate it! Unfortunately it did not work 
Here are the logs: Plex Media Server Logs_2020-01-26_00-07-24.zip (3.2 MB)
I’m starting to wonder if the modem itself is bad?
When PMS tries to tell plex.tv it’s online, there’s a timeout!
Ref:
Jan 25, 2020 18:48:08.716 [10224] WARN - MyPlex: we have an existing connectivity refresh request for async identifier d1eedbba-4a1c-4367-bf47-21f8b7eb08bf, but it has expired so we will try again.
Jan 25, 2020 18:48:08.716 [10224] DEBUG - MyPlex: Requesting reachability check.
Jan 25, 2020 18:48:08.717 [10224] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/f6e754e34dc7f0d34c88582bb427fd1dbf86bfe5/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=d524311b-a608-442c-a6d7-de4d64f459e5
Jan 25, 2020 18:48:08.750 [15532] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 25, 2020 18:48:08.750 [15532] DEBUG - HTTP simulating 408 after curl timeout
Above makes PMS switch itself offline again, AFAIK. Ref:
Jan 25, 2020 18:48:10.439 [6556] DEBUG - Request: [127.0.0.1:65080 (Loopback)] PUT /:/prefs?PublishServerOnPlexOnlineKey=false (12 live) GZIP Signed-in Token (Attackonzach8210)
Jan 25, 2020 18:48:10.440 [6556] DEBUG - MyPlex: Toggling server publish state.
Jan 25, 2020 18:48:10.440 [6556] DEBUG - PublicAddressManager: Stopping.
This could happen due to a bad DNS (Slow), so suggest you as a small test, switch the DNS Servers used for your box to Google DNS (8.8.8.8 and 8.8.4.4)
After doing above, reboot Windows, and try again…
And note, if that still fails, then once more a fresh set of logs, but this time please avoid playing medias as well, since there’s already enough lines to debug from
I created a topic about my own remote access issue but I’m going to chime in here also. Here is what I’m seeing:
And here is the error I’m getting:
I checked with my internet provider and they said the public ip address is working and accessible. This leads me to believe it’s a problem with Plex and not my internet. I made no changes to my internet or system, it simply stopped working about 2 weeks ago or possibly even longer. But it can’t connect to my public ip address for some reason.
