Not available outside your network

Server Version#: 1.18.1.1973
Player Version#:N/A
At some point while out of town my server started saying it was unable to establish a direct connection and had to fall back to an indirect one. Upon attempting to play something it failed. After investigating my server I saw it was reporting that it was not available outside my network.

My computer is staticed on my router using a dhcp reservation and I am forwarding 32400 -> 32400 that I have manually set. I’ve verified that the port was indeed forwarding and have restarted everything between the server and the internet, as well as fully reinstalling the server program after deleting all the relevant registry keys and moving the appdata database to another location. Some of the errors I’ve been getting are:

PubSub: Received notifyConnectivity event with incorrect async identifier ([censored identifier], expected [censored different identifier])

and

HTTP error requesting GET /media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (0, No error) ( malformed)

and

Error issuing curl_easy_perform(handle): 28 as well as some others

None of those errors are a smoking gun. Please provide the entire log file so we can look.

Plex Media Server Logs_2019-10-29_18-57-45.zip (477.6 KB)

Logs.7z (12.6 MB)
and here’s the logs from my backed up appdata folder should you need them

If you need anything more specific or a smaller log snapshot or whatever I’d be more than happy to make that happen.

Your PMS appears to be using the correct address but for some reason there is no response form it. I tried pinging your server and there is no response. Something is not letting the requests get to your server. I’m thinking it’s something on your network.

Your logs show you have a Fios Router and a Nighthawk Managed Switch. Your server is connected to the Router, right? And you’ve setup the correct port forwarding? Have you checked with a site like “canyouseeme.org” to verify the port is working properly.

I actually just did a full factory reset on my router right before or as you sent this response (the notification came through when the connection restored) and am in the process of setting the static/forwards back up.

That didn’t fix it, canyouseeme.org says it can see my service on 32400. My server is connected to my switch which is connected to the router, though I just plugged directly into the router and am seeing the same behavior (with the switch off the network entirely). The only other devices on my network are a couple ios devices, 2 smart tvs, a network printer and a set top box.

Another thing that may be relevant is that when I ‘enable remote access’ it says its working for about 10 seconds before saying its not available. It seems almost like the port itself is open but the thing that checks connectivity isn’t? If that makes sense

You have a managed switch. When you plugged into the router, did you double check if you got the same IP? You might not so you would need to adjust your port forwarding.

Can you provide a screenshot of the port forwarding page from your router and the remote access page for PMS?

Yes, I verified it was the same, the managed switch was set up with only some basic qos. I’ll get you the screenshots in a sec.

I don’t think your port forward is correct. Can you show me the page to set up a new one and fill it in the way you did, but don’t apply it?

Added some notes in the details

Ok so I checked again at canyouseeme.org and now it’s saying that it cannot see my service on 32400 with reason: “No route to host”

Bah nevermind I hadn’t set up the static correctly when I reset the router to defaults and the private ip of my server had changed.

Though now its saying it’s fully accessible outside my network, but when I try and connect to it from another location it still says its indirect.

I still can’t ping your server so something is still not setup correctly.

This has started to happen to me also and it only started after I updated last night. Nothing changed in my router settings or modem settings the only thing that changed is I updated plex.

Yeah I’m at a loss, considering trying a fresh os load at this point just to rule that out