Plex Remote Access Acting strange

I have a strange situation with flex remote access that just started a few days ago. Late last week I lost remote access to plex and started the process of trying to determine what was wrong. Everything I tried except powering off/on my gateway didn’t work. However, when I powered off/on my gateway the remote access turned green. Within a few minutes the green turned to red and currently it is in red. The strange thing is that my remote clients can still access my plex server and watch my libraries. I try resetting the remote access and it turns green and then red.

Does anyone know what could be causing this issue. Anyone from flex please help!!

BigWheel posted this and on my set-up it was the problem.

BigWheel Plex Employee

I am also curious what protocol folks have set in router. Seen a few reports recently of folks with both TCP&UDP enabled having issues getting Remote access working. PMS only needs TCP.

This fix my problem. Remote Access Drops with Version 1.13.2.5154 Not sure if this is what your seeing.

Hey Big Wheel:

Thank you for your quick response. To answer your question, yes I had plex protocol setup as tcp&udp. When I went into my router settings to change/delete the setting and add onlu tcp, it wouldn’t let me do either. It tells me “I can’t edit/delete an application while it is being hosted”. I shut down plex on my server but it still gives me the same error. I don’t understand why everything has been working in plex for years and now I am having problems. The strange part is that people are still accessing my server even though remote access shows red in plex settings. Any help would be greatly appreciated.

Bob

Hey Bob,

I been using PMS for over two years and a plex-pass for half a year now. Never had much issues with remote except with getting firewall to work with PMS on Linux. My issue started when upgrading to Version 1.13.2.5154 which was the reason I guided you to Remote Access Drops With Version 1.13.2.5154 Topic. If you recently upgraded this could/might be the issue.

As far a router goes have you tried rebooting/restarting router before making changes to TCP only on Port Forwarding to Port 32400. Or just trying restarting modem, router, plex box/pc first and in that order to see it that resolves issues. Passed that I myself would be hard pressed to resolved the issue you describe.

AllenDK

I also have a similar problem, started a week ago. If I disable remote access then reenable it works for a week, then it happens again. Must be a bug with the latest server version.

Tried everything I could think of and still having the same problem.

  1. Re-installed Plex
  2. Re-installed Mac OS
  3. Restored Plex from a backup prior to problem beginning
  4. Changed protocol port forwarding settings in router from tcp/udp to tcp.

Can any Plex employee help?

A problem has just been identified caused by recent migrations of pubsub Plex.tv servers - it is being looked into And changes have been made to stop the behaviour seen here : remote access status showing unavailable but is actually working

1 Like

Thank you SA2000. The one thing that I forgot to mention was that no-one with a mobile device, i.e. cell phone, or tablet can access my server remotely. Also, some of those people who were able to access my server thru their at home devices now can not. Have you heard of any time frame for this to be fixed?

Did you tick the manually specify port box and enter the public port you forwarded to 32400 (in server remote access settings) ? and is the IP address for the server fixed / reserved ?

Please make sure debug logging is enabled and restart the server and then open the remote access settings page with show advanced - disable remote access, wait 30 seconds, enable it. Do not click retry many times. once enough if needed and then take a screenshot and collect server logs

See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/

SA2000:

I did everything you mentioned and when I disabled the remote access and then enabled it it turned green for a moment and then back to red. As fore your questions, yes the box to manually specify port box was ticked and the port 32400 was already set. As far as the 1p of the server I believe it is fixed but I am not sure what you mean about reserved. Whats the difference? I downloaded the log files and I am going to attempt to attach them to this post as a zip file. Thanks so much for your help on this.Plex Media Server Logs_2018-07-10_13-47-28.zip (7.5 MB)

The port forward in the router - is it to forward WAN/Public TCP Port 32400 to Local IP Address 192.168.1.83 TCP Port 32400?

Can you check if you have double nat. On the server, load a browser and go to this web site http://canyouseeme.org and note down the public IP it displays

Then log in to your router and see what it shows as the WAN IP Address
If they are the same - there is no double nat.

The reservation i mentioned would be in the router where you tell it within DHCP Settings that 192.168.1.83 is to be reserved / permanent for the Mac - normally you would need to enter the hardware MAC Address of the ethernet card on the Mac

When I go into canyouseeme.org it shows the public ip. In the router the wan ip is the same as the public ip if you mean the the ipv4 address. There are two ipv4 addresses, one for broadband (which is what canyouseeme.org reflects) and the other ipv4 address is for Gateway. The gateway ipv4 address is the same as the public ipv4 address except for the last group of numbers.

Thanks

Could you restart the router and then the server and get me a screenshot of the port forward settings in the router and open the server remote access page and confirm it is still marked as enabled and the manually specify port 32400 is still ticked and if still not working please get fresh server logs and attach with the port forward router screenshot

Sorry I didn’t get back to you sooner on this but I was out of town yesterday. Did what you asked from your previous message and confirmed that the remote access page was still marked as enabled and the manually specified port 32400 was still ticked. As before after I restarted the router and the server the remote access was green and within a few seconds it turned red. Attaching new server logs and screenshot of port forward settings.Plex Media (3.3 MB)

Can any PLEX employee give me any help with this PLEASE!

I have been looking at your logs and also comparing with others from other users with remote access issues.

It looks as if you have some block at your end that is resulting in some requests not getting to the server. See if you have any IP ranges blocked. Any security / firewall software you are running

The log shows successful connection test at this time

Jul 12, 2018 10:58:46.964 [0x700004bf4000] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/faf9885735d65b752aa695ee5a838d82d01e32a7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=4f076620-fcec-44b1-980f-e88e50fe02ac
Jul 12, 2018 10:58:47.449 [0x700004bf4000] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/faf9885735d65b752aa695ee5a838d82d01e32a7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=4f076620-fcec-44b1-980f-e88e50fe02ac

Jul 12, 2018 10:58:47.881 [0x700003fac000] DEBUG - Request: [52.213.132.78:38880 (WAN)] GET /identity (16 live) TLS Signed-in Token (baboots)
Jul 12, 2018 10:58:47.881 [0x700003d1d000] DEBUG - Completed: [52.213.132.78:38880] 200 GET /identity (16 live) TLS 0ms 357 bytes

Jul 12, 2018 10:58:48.260 [0x700003d1d000] DEBUG - EventSource: Got event [data] '<Message address="76.236.xxx.xxx" port="32400" asyncIdentifier="4f076620-fcec-44b1-980f-e88e50fe02ac" connectivity="1" command="notifyConnectivity"/>'

The remote access test comes in from a WAN IP from plex.tv - in this case it was from 52.213.132.78 and it got to the server ok. This then generated a success outcome event to the server

What followed was a second connectivity test. The (WAN)] GET /identity request may have come from other IP range - these plex.tv IP address are not always the same. The request did not get to the server and as a result, the server received an event to say the connection test failed

Jul 12, 2018 10:59:10.432 [0x700003e23000] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/faf9885735d65b752aa695ee5a838d82d01e32a7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=07eeed5a-a8ba-46ed-b48a-48f2999e142c
Jul 12, 2018 10:59:10.947 [0x700003e23000] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/faf9885735d65b752aa695ee5a838d82d01e32a7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=07eeed5a-a8ba-46ed-b48a-48f2999e142c

Jul 12, 2018 10:59:20.647 [0x700003c17000] DEBUG - HTTP requesting PUT https://plex.tv/api/servers/faf9885735d65b752aa695ee5a838d82d01e32a7/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=3e19a4bb-70c5-4548-a170-9d43c8e0a692

Jul 12, 2018 10:59:21.063 [0x700003d1d000] DEBUG - EventSource: Got event [data] '<Message address="76.236.xxx.xxx" port="32400" asyncIdentifier="07eeed5a-a8ba-46ed-b48a-48f2999e142c" connectivity="0" command="notifyConnectivity"/>'

When we log the EventSource data event message, this means that a GET /identity request would have been made to the WAN IP shown as address in the message (WAN IP starting 76.236 ) and WAN port 32400

Thank you for continuing to help with this. Can you help me determine if/what ip ranges are being blocked? I am not totally proficient in these matters. I had some security software on my server that I deleted but that didn’t seem to work either. Appreciate all of your help with this.

The connectivity tests would be requests that come in Plex Amazon servers. The IP addresses vary and could be any within the Amazonws set

Amazon publish the IP ranges here https://ip-ranges.amazonaws.com/ip-ranges.json
You would need to understand subnets and subnet masks to work out exact ranges
See Netmask Converter - Bitmask | Decimal | Hex | Binary

Thank you for your help on this although I must admit I don’t understand much of this. What frustrates me is two things. First, that everything has been working fine with plex for years and secondly why can clients still somewhat access my server. It’s an on an off thing that if something is blocking these ip’s why is it so sporadic? What could possibly have changed? I have AT&T coming out in a few days to replace my arris bgw210-700 gateway in and effort to try and isolate where the trouble could be. I have thought about resetting my gateway back to its factory settings and starting over. Any thoughts? Lastly is it possible that the plex media software could be the problem? Again that you so much for all of your help!

Of course it is possible that there may be an issue with Plex Media Server software - but the logs that were seen indicated otherwise.

You can get more logs covering time when it was ok but then remote access gets lost and I will have a look to see if same as before or not

With regards to resetting the router to defaults - that is fine so long as you can re-instate settings and bring the firmware up to date