Server not reachable after latest update

Server Version#: PlexMediaServer-1.18.0.1900-6887070bc-x86_64.qpkg
Player Version#: trying web.

Notes: I’m on a office network, and the firewalls have since long before been configured to let PLEX traffic in and out. This stopped working after today’s update. I have tried restarting the app multiple times, even the server.

What should I do?

Are you 100% sure the ports are mapped? Does canyouseeme.org indicate the port is open?

Has anything changed with the ports with this update? Because it’s been working for two years, and several updates before this update. How do I do the same test but on a QNAP NAS? I can remote into it, but there is no browser exactly.

Just checked 32400 via that webpage and from that network, and got a positive response. So the port is open.

Also tried the latest build and still no luck. Even tried local version:
http://192.168.1.100:32400/web

And it also can’t reach the server.

Some support would be appreciated.

1 Like

For a start, it can sometime happen, that a process is not properly shutdown during the upgrade. to be 100% sure, restart your QNAP

If that doesn’t help, then you need to fetch the PMS logs manually, and upload here

Tried many times unfortunately to no avail. How do I get the logs manually?

Install this:

Then in the share created, you’ll find a directory named logs

Zip that, and upload here

So heres an update, since the last update I did prior to your message, to version: PlexMediaServer-1.18.0.1913-e5cc93306-x86_64.qpkg

Plex has been using 95% of my NAS memory from start.
I had to reboot the NAS just to install the QPKG you suggested, but it wont start, I can only assume that it is because of the memory shortage, or that it isn’t digitally signed and perhaps no-longer compatible? Regardless, I tried to stop PLEX to free up the memory, but even though it’s stoped its still running the process in the background taking all memory.

So what do I do now? I’ve read somwhere that I can remove the app and it will keep all my settings and libraries, but I am very hesitant to do so without further consultation.

I am on a QNAP TS-453A, if that has any importance at this stage.

It’s not supposed to start…It creates a share and then exits
So for a start, what I asked for, namely logs!

Without those, we are wasting each others time, since we’ll be guessing and speculating

I miss-read and missed the “It’ll” in “It’ll then create a share named Plex”

Sorry to waste your time, I am only a humble paying plex user, not an expert.
Logs where pretty huge so had to upload them here:

Sorry if I came out arrogant here, didn’t mean to.

You seem to be having network issues…

Did anything else change in your setup?

1 Like

That’s ok, I know how it can be, and I do appreciate the help.

As for your question, not really. After the first update that lead to me not being able to find the server, I ran a firmware update on the NAS. But other than that no. And the issues started right after the plex-update.

Since yesterday I had the plex app stopped and have had no resource issues, or problems remote connecting to the NAS, as soon as I start the app the CPU spikes, and according to the resource monitor its plex. Oddly enough yesterday it was the memory and today its the CPU.

1 Like

What QTS are you on now?

4.4.1.1081

I, along with many others have seen this issue rolling up to 1.18.xxx from 1.17.xxx

There are threads all over reddit and Plex forums with people complaining about the issue. I myself saw it. I rolled back to the 1.17.xx version and everything works fine.

Even tried a fresh install of the most recent 1.18.xx and no one side from my main admin account can access the server, not even my managed users.

It’s very odd cause nothing has changes on my network or firewall side in ages.

Interesting, glad I’m not the only one at least. So what’s the correct way to roll back on?

Simply install on top…

Do NOT uninstall/reinstall

1 Like

So I installed PlexMediaServer-1.17.0.1841-d42cfa161-x86_64.qpkg and everything works again.

I have the exact same issue. WTF mayn. This latest update seriously destoyed my plex environement.

how do you get that older package?