Server "unreachable" on linux-based PMS on VPS

Plex Media Server Desktops & Laptops
1

Server Version#: latest
Player Version#: web client, Roku 3

I’ve been happily running Plex on both a local Windows server, and a linux-based VPS server. Tonight for unknown reasons Plex can’t find the VPS-based server.

I’ve logged onto the VPS and confirmed that plex is running and that I can run the web client on the VPS in a browser and see PMS and its content.
I’ve rebooted the VPS. I’ve logged out of Plex on the VPS and logged back in.
I checked that remote access is enabled.
I removed the server from my Plex account and re-added it successfully (on the VPS).

I’ve logged out and back in on the web client.
I’ve rebooted my router.

Plex has been doing weird things this week… anyone else having this problem?

2

Did you SSH-tunnel to it, get on the “console” to it and make sure it’s logged in to your account and remotely accessible?

3

First thing I did was bounce it from a console.
The vps runs gnome so I logged in to that (vnc) and it is up and running in a browser on the vps, and logged in to my plex account.
I cycled the Remote settings to make sure it is remotely accessible.

I checked the port just now, it’s open.
It’s been running beautifully for months and just stopped tonight without any access or changes to the VPS.

4

Just wanted to re-iterate what you said.

It says it’s up and remotely accessable.

From a browser on the box, what does Canyouseeme.org show for 32400 / the open RA port?

if it’s open, it’s not a server issue. it’s in the client(s)

1 Like
5

same issue as other thread, plex.tv is handing out the wrong address info, causing clients to fail and “remote access” to show incorrect info. If you look at your settings while this is happening you’ll see it reporting a reserved network for your external ip. If you connect your clients to your actual ip/port you can connect from “outside”.

6

Do this: Whatever you have for “latest” version? (doesn’t tell me anything useful because there are two)

Install PMS 1.13.4 or older. Retest.

7

@unhooked.net

Please stay in one topic? I will not chase two.

We can pick this up tomorrow during my normal hours.

Thanks.

8

Ok, I’ll just pretend the other 15 threads of people all complaining about the same thing don’t exist.
But remember, you did ask for examples.

9

We were experiencing a small issue on our backend. Should be cleared up now.

10

Have you announced this anywhere officially?

11

what IP you are seeing? A problem has just been identified to do with the public IP for the server and is being fixed on plex.tv - it is not related to any specific version of Plex Media Server

12

I did test from Canyouseeme and the port is open.

Last night I briefly saw a message about no relay server available. From reading other posts in the thread here, it sounds like it was a plex issue.

It’s scary to think that maintaining connectivity between a machine that I own depends on Plex’s servers to work.

13

Still not working.

Linux server version is 1.13.5.5332

14

I am connected to the Linux box - it says it’s an indirect connection (aka relayed, I suppose). This has never happened before. Actually, I didn’t know relay existed until last night. :slight_smile:

UPDATE it’s gone again. I’m going to sit tight. I have a feeling this is something Plexopoly has to fix on their end.

15

Yeah, some of my clients have been dropping to ‘indirect connection’ for a couple of days now, whilst on the local network (no DNS rebinding, no connection issues on my side. port forwarding working, no UPnP).

16

Same for me just constantly dropping, I can Retry in the Remote Access page and usually everything will come back up then it can be 5 minutes or a whole day and then it’s back down, it’s getting quite annoying now.

17

The problem where Plex media server reports a public IP address of 172.17.0.1 has now been fixed.

You will need to disable / re-enable remote access or restart the server.
You may also need to kill mobile Plex apps and re-launch them to pick the correct route to the server

Thanks for reporting the problem

18

Hmm, server restart, new web client session - it went into ‘indirect mode’ for a brief time and the remote access page is showing the attached .png (it was able to pick up the static WAN IP prior to the server restart).

Is the fix a workaround? - there have been quite a few posts about ‘indirect mode’ recently (pre-dating this issue).

remote_access
remote_access.png1184×160 97.5 KB

19

The fix was for the specific issue where the Public IP is not detected correctly and instead a 172.17.0.1 or similar local IP address picked up.

Any other issue would need to be investigated with debug logs and info on whether manual port is used or dynamic uPnP port.

Please make sure you run on the 1.13.8 release and have debug logging enabled - see https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/

Then restart the server and if remote access is enabled but failing, capture screenshot and logs zip and attach

https://support.plex.tv/articles/200250417-plex-media-server-log-files/

20

Even more intersting - with absolutely no interaction from me (or users) - the system is now claiming its unreachable. See attached screenshot. And yet, I can stll connect to it over the web client…

screen2
screen2.png1654×172 139 KB