Plex Server Remote Access stopped working

Plex Media Server Remote Access
1

Synology NAS DS1817+
Synology DSM Version 7.11-42962 Update 6
Plex Server version 4.140.1
Router Netgear Nighthawk X6 R8000 Firmware V1.0.4.84_10.1.84
Internet service XFinity/Comcast Cable Modem. Advanced security is not enabled.

I have configured the Synology to use 192.168.1.10. I set up a port forwarding rule on the router to forward port 32400 from that internal IP address.

trumpy81 helped me get this working four years ago and it has worked since then until recently. No hardware has changed on my end, but obviously there have been software updates.

At this point remote access gives the infamous “Not available outside your network”. I have tried resetting it and it fails again in a few minutes.

I can only access the Plex Music Server on my cell phone if I am in the house and turn on WiFi on my phone – which indicates that the remote access is not working. I am uploading the Plex logs from a few days ago.

Again, I have made no configuration changes from when it worked.

Plex Media Server Logs_2024-10-20_16-53-30.zip (7.0 MB)

2

GDay Fritz,

This must be your lucky day, I stuck my nose in for a minute and noticed your post … lol

From your logs:

Oct 20, 2024 15:53:10.264 [140417444191032] WARN - [EventSourceClient/pubsub/192.81.131.80:443] PubSub: Received notifyConnectivity event with incorrect async identifier (, expected 05d0ded6-791c-4e8f-9e34-b259ecf271e8)

This was the only thing I could find in your logs and it’s not overly helpful.

The first thing you should do is reboot your modem/router and everything connected to it, including the NAS and any wireless devices.

Once that is done, open Plex/Web using http://NAS-IP-Address:32400 and if asked to sign in then do so.

If it is already signed in then click on your avatar (top right of screen) and sign out. Refresh the browser tab (or open a new one) and sign into Plex again.

Next, go to Plex Settings > Server > General and make sure the server is claimed.

Then, go to Plex Settings > Server > Remote Access (Show Advanced) and make sure Remote Access is still enabled.

Also make sure you have the Internet upload speed set and if you need to specify the public port number (it should be set to 32400 depending on what you set in your router), then do that as well.

Next, refresh the browser tab, cross your fingers and hope for the best … lol

One other thing you can try is going back to an earlier version of Plex.

Uninstall Plex and choose the first option, Uninstall Only (keep all files).

Then install the earlier version for DSM 7.x. All should be the same except for the server version now.

Check and make sure all settings are correct in Plex/Web and check if Remote Access is working or not.

BTW, the server version you provided is incorrect, that is the version of Plex/Web NOT the Plex server. To find the server version go to Plex Settings > Server > General and NOT Plex Settings > Plex Web > General.

3

Great to see you again!

I will go reboot the world later. I can check the real version now… 1.41.0.8994

And, yeah, I have claimed the server. I did not have the speed set. I ran speedtest and set it in the app.

Rechecking now.

4

Alas, no change. I will reboot the router and NAS tomorrow.

Could my ISP – XFinity/Comcast – have messed with something on their end?

5

When setting the Internet Upload Speed, did you make sure the measurement was in Mbps?

E.G. If your ISP provides 50MB/s upload speed then that would equal 400 Mbps, or 50 multiplied by 8.

That’s always a possibilty, but it is most unlikely.

It is more likely that the routing of your signal is being passed around the globe from ISP to ISP and that is slowing the signal to the point where Plex cannot get a good lock on it, meaning the connection is too slow for Remote Access.

Unfortunately, there is nothing you can do about that, you just have to sit back and hope things clear soon and you get a more direct connection.

Of course, there are many other scenarios which may be in play, down servers, etc. that may also be causing the issue and there is little you can do to correct those situations.

Double check your port forwarding rule in your router settings, it should look something like the settings shown below:

Screenshot 2024-10-25 040447
Screenshot 2024-10-25 040447947×120 3.84 KB

These are my settings, which were automatically set by Plex and yes, I have three Plex servers.

If you manually set the External port number in your router settings, then you must use that External port number when setting the Manually specify public port in Plex/Web > Settings > Server > Remote Access.

If you did NOT set the External port number in your router settings, then do NOT set Manually specify public port in Plex/Web > Settings > Server > Remote Access.

6

From your example, it is abundantly clear that you are not on a cable modem – I get 24Mbps up.

Resetting did nothing. I note that now when I reset remote access it does not fail in a few minutes (which was the case years ago), but stays green for hours before suddenly going red. It isn’t working, but it does not know that it has failed.

I looked at router logs. Besides a really disturbing number of SYN floods from outside (sheesh, do people think it is 1999?), I do see logs of traffic to the Plex port on the NAS from outside. Not much, but one or two.

So – any other thoughts? This is quite frustrating.

7

@FritzSands

  1. I put my Comcast modem into Bypass mode.
    – disables WiFi and router functionality

  2. My router (pfsense), which can also be your Netgear, will get the WAN IP address. My router then creates and manages the LAN and WiFI AP.

How do you have things configured?

  • Comcast modem is configured to create LAN ?
  • What does your Netgear do? WiFi only?
  • Which device is the main? Netgear or Comcast ?
  • What are their IP addresses ?

My thinking, If you’re willing and dependent on your modem, is to emulate the configuration I have.

Regarding the SYN packets: Are you getting a SYN Flood DDOS attack?

If you are, and your Plex WAN port is 32400, then it’s clear.
Port 32400 is very popular and once found, there are those who will be obnoxious and hammer it.

The trick there is to pick an unusual port. I use uncommon numbers.
31415, 31514 ;), 17159, 32761, etc and Manually Set Port.

Apologies for jumping in. Please forgive if I’ve misunderstood anything.

The Incorrect async ID found by Trumpy is an indicator of severe network delay.

I’m seeing a modem at 192.168.1.1 which it is reporting it’s not able to use. We need to fix this.

8

Actually, I am using a cable modem because NBN in my area is FTTN (Fibre To The Node), so from the node to my home is all copper, hence the cable modem.

I only have 100Mbps down and 40Mbps upload (averages at about 37Mbps Up), but that costs me an extra $20 AUD a month … lol

In approx. 2 years time, I should have FTTP (Fibre To The Premises) and that should allow me to have a Gigabit connection, fingers crossed :slight_smile:

@ChuckPa

That was my thought also, which explains my rant about slow connections and routing globally rather than a more direct route.

And thanks for chiming in, you have far more knowledge of Comcast than I do … lol

9

I changed my port forwarding on the router so I am using a port other than 32400. I think the analysis that somebody is doing a stupid DDoS on 32400 is correct. Anyways, for now, it appears that the change in the port forwarding rule is working. Wow… Thanks, all.

10

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