PLEX media Server local Port 32400 on QNAP NAS not reachable

Plex Media Server NAS & Devices
,
1

Server Version#: 1.32.8 (downgraded to 1.32.7 but same problem)
Player Version#: iOS Player, Samsung Smart TV, plex.tv

Hi Plex Team,
unfortunally I cannot reach PMS anymore via local IP and port 32400. I am getting a ERR_CONNECTION_REFUSED error. All firewall settings and LAN settings seem to be fine… I googled hours but couldnt find any useful hints yet ;(

hope you can help me.
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

2
  1. Do this to create a “PlexData” shared folder

  1. Try to restart Plex once then leave it stopped.

  2. Use FileStation: PlexData/Plex Media Server
    – Right-click ‘Logs’ → Compress (ZIP)
    – Download the ZIP
    – Attach it here

The reason you can’t connect to it is Plex won’t start / keep running.
We need to see what’s happening (what the logs tell us)

3

I had to split the logs due to large size → i splitted the logs in 1st the whole PMS Plugin Logs Folder and 2nd everything else
PMS Plugin Logs.zip (2.0 MB)
other logs.zip (7.5 MB)

4

just for info… I didn’t need the steps with the PlexData Folder as I can see all the plex folders via filestation (I did that a couple of years ago… can’t remember how I did it :-P)
image

5

I immediately see you have the DLNA server running.

There is a known memory leak which causes QTS to shut all of Plex down when memory is fully consumed

Is the DLNA server required ?

6

Hi, yes DLNA is being used, so I cant shut the service down.
Plex worked before while DLNA was enabled.

7

DLNA leaks memory. They never found out the cause.
The result is – it will eventually grow in memory usage until QTS kills it (and Plex with it)
It’s been like this for a very long time.

The only hap-hazard work around is to restart PMS daily.

1 Like
8

Hi Chuck,
First of all I want to thank you in advance for your support and sorry for any inconveniency while trying to support me!

I already restarted PMS several times, i restartet the whole QNAP several times, and the Router too.

It seems there is anything blocking the PMS Server as I cant even connect to 192.168.0.2:32400.

Portforwarding for the UPNP Router is fine, but neverless in my opinion the local 32400 port should work without UPNP too.

9

Yes, it should always work on LAN

http://LAN.IP.of.QNAP:32400/web should always work.

What happens if you go into the QNAP via SSH, as root / admin or sudo/su and then execute /etc/init.d/plex.sh restart ?

You’ll see output in the SSH session’s console window

10

image
image832×222 6.66 KB

11

before running the commad via Putty Plex Server was already running (at least QNAP GUI says so)

image
image1067×175 34.1 KB

12

plex process is runnning too (but with very few ressoruces?!)

image
image1531×327 29.4 KB

13

There should only be 1 plex server process running.
PID 2858 appears stuck.

kill -11 2858

make certain it’s gone

then restart PMS

ps -ef | grep -i plex

I think the first one crashed and it’s stuck terminating.
The new one can’t get started

1 Like
14

i killed the process

image
image472×180 4.14 KB

image
unfortunally still not working

image
image927×539 19.4 KB

15

please try it this way. (something in QTS is very confused… I know you’ve restarted it too)

  1. App Center – Stop Plex
  2. From the putty session
    – ps -ef | grep -i plex
  3. If any processes are remaining, kill -11 them
    – Check again with another ps -ef | grep -i plex until all are gone
  4. Now start Plex.
  5. Wait 30 seconds and do another ps -ef | grep -i plex
  6. Keep an eye on the CPU load. If nothing is happening,
  7. Then stop Plex, grab the Plex Media Server.log file (just that one)
  8. Attach it here so I can see what’s happening (there is a problem here somewhere)
16

I did all steps as you described…
image

the Plex Media Server Log File is 4 days old!?

image
image1603×66 13.5 KB

the newest log file ist the crash start log - I have attached both:
Startup Crash.log (162 Bytes)
Plex Media Server.log (5.2 MB)

17

Although I stopped PMS via App Center, process is still running … :frowning:

image
image1080×123 28.4 KB

image
image1205×62 7.78 KB

18

The server log being 4 days old … Dec 16, 2023 18:41:53.587

App Center has it stopped.

NOW, if you restart the QNAP, Plex will not auto start

Confirm Plex stopped in App Center.
Restart the QNAP
Putty into it
ps -ef | grep -i plex – You should not see any processes.

Start PMS via App Center

Allow it to run (or think it’s running) for one minute.

Let’s see if it’s opened any of the ports

netstat -an | grep 32400

If they are open, you will see them listed. This is good
It means you will also have activity in the log file.

Let me know what you find

19

After restart I made sure Plex is not running via App Center.
Then I startet putty and checked disabled Apps: → Plex disabled
image
Then I ran your first command
image
→ I don’t know what that output means
image
but I followed the next steps!

I started Plex via AppCenter and waited a minute.and then requested the following command:
image

nothing happens, so I thought I had to do the following command: netstat -an
So I got a veeery long list (see attached file) but I can’t find any 32400 relation.
netstat -an.txt (22.5 KB)

20

in the meantime I tried installing the v.1.40.0.7775-456fbaf97 Beta Release… didn’t work either… I still think Plex is just not starting correctly as the only current Log is the start up crash log that gives to following output:
Dec 22, 2023 20:14:22: Failed to initialize logging: Error parsing file at “/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Preferences.xml”

Any new ideas or recommendations?

Maybe one more useful info for you, plex stopped working after QNAP sudden systemcrash due to a power problem. Maybe it is the Preferences.xml which stops plex from starting correctly?!