Suddenly Cannot Connect With Remote Access After Working For Months

Plex Media Server Remote Access
1

Server Version#:1.16.6.1592

Everything was working great for over 6 months when all of a sudden I get a notification that PMS was offline. I hadnt change anything to my knowledge. PMS is running behind a pfsense firewall with port 32400 correctly forwarded. When using canyouseeme, I am getting an error. I also tried rolling back Plex Server to an older version to no avail. I checked the logs and am getting the following error :

HTTP error requesting GET https://74-129-147-24.de98dbceb3c8413dab3840c03017c442.plex.direct:32400/identity (0, No error) (Failed to connect to 74-129-147-24.de98dbceb3c8413dab3840c03017c442.plex.direct port 32400: Connection refused)

Not sure where to go from here?

2

And you are sure your port forwarding is setup proper?
And no firewall changes were made?

I see you are listening on port 80 and 443 and have a lets encrypt cert loaded for “cloud.nucleushosting.tk” under your nginx web server but port 32400 is not responding at all.

3

Yes everything is setup correct as I didnt change anything when it all broke. I have an FTP server on the same machine as the PMS that is still functioning correctly. The web server you are referring to is on a different machine running Unraid. I even tried changing the ports for PMS in pfsense and in my Windows firewall which did not work. Any other thoughts?

4

Can you connect to http://192.168.x.x:32400 locally from a different machine?

192.168 being your pms ip.

5

Yes sir, sure can. Its at 192.168.50.100:32400 and I can connect just fine on the LAN.

6

These are all the ports that are “reachable” on your system.

I would have to say there is something wrong with your firewall/port forwarding since FTP you said is on the same machine and works fine.

image

7

Server version: 1.17.0.1709

I’m getting the same kind of Connection refused errors, but my remote functionality works sporadically.
I’ve had several years of smooth sailing with Plex remote access (even surviving an upgrade to Ubiquiti equipment with minimal headache, over a year ago now)

Everything is configured manually, StaticIP for server, manual port configuration, and manual port forwarding rules. Everything’s been working perfectly.

Suddenly, this past week or so, remote access won’t stay connected.
Cycling the Remote Access option off and back on again will light things up green, for a little while… then it goes back to red.

While the check is green, I can access and playback library items from a remote machine. No problem. But after a short while, the remote access becomes unavailable, and the server shows as offline again.

In the logs, whenever I cycle the option or ‘Retry’ the connection, I’m getting a few warnings, and one error.

Sep 22, 2019 15:56:53.855 [1160] Debug — Content-Length is -1 (of total: -1).
Sep 22, 2019 15:56:53.980 [8612] Debug — PublicAddressManager: Obtaining public address and mapping port.
Sep 22, 2019 15:56:53.980 [8740] Debug — PublicAddressManager: Obtaining public IP.
Sep 22, 2019 15:56:53.980 [8740] Debug — HTTP requesting GET http://plex.tv/pms/:/ip
Sep 22, 2019 15:56:54.199 [8740] Debug — HTTP 200 response from GET http://plex.tv/pms/:/ip
Sep 22, 2019 15:56:54.215 [8740] Debug — PublicAddressManager: Got public IP from http://plex.tv: 108.28.61.197
Sep 22, 2019 15:57:04.261 [8740] Debug — NAT: UPnP, found device http://192.168.1.46:80/dms/device.xml with private address <192.168.1.10>
Sep 22, 2019 15:57:04.261 [8740] Debug — NAT: UPnP, not an IGD: http://192.168.1.46:80/dms/device.xml.
Sep 22, 2019 15:57:04.261 [8740] Debug — NAT: UPnP, getPublicIP didn’t find usable IGD.
Sep 22, 2019 15:57:04.527 [8740] Warning — NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Sep 22, 2019 15:57:04.527 [8740] Debug — HTTP requesting GET https://108-28-61-197.f8ce68bdae464422bf5bdea50f3cb039.plex.direct:32400/identity
Sep 22, 2019 15:57:05.746 [8740] Error — Error issuing curl_easy_perform(handle): 7
Sep 22, 2019 15:57:05.746 [8740] Warning — HTTP error requesting GET https://108-28-61-197.f8ce68bdae464422bf5bdea50f3cb039.plex.direct:32400/identity (0, No error) (Failed to connect to 108-28-61-197.f8ce68bdae464422bf5bdea50f3cb039.plex.direct port 32400: Connection refused)

Connection refused sounds like something is blocking the connection, but my fire-walling has been unchanged for months, and CanYouSeeMe is indicating that the port is working.2019-09-22%2016_05_14-Open%20Port%20Check%20Tool%20--%20Verify%20Port%20Forwarding%20on%20Your%20Router

At this point, I’m curious if there’s a remote access bug in Plex somewhere… as near as I can tell, my network is configured correctly.

Any insight would be appreciated. Let me know if any log files are desired.

On an unrelated note, I’ve had issues with HW transcoding since upgrading to this version of PMS, I saw a bunch of transcoder changes mentioned in the changelog for this release, so likely something got tripped up along the way.
I’d be glad to provide additional feedback or troubleshooting if that would be helpful.

1 Like
8

Buenos días,

Yo no entiendo mucho de servidores etc. Por casualidad encontre Plex me pareció interesante y lo empece a probar. Me funciono tan bien que se lo descargue a mi madre y le enseñe como iba.
Desde ayer no me conecta a mi servidor. He desinstalado, he reiniciado, lo he probado todo … nada de nada
Estoy igual que vosotros

9

Same issue here, my logs look exactly the same as you:

10

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