Plex server on QNAP regularly unreachable unless stop/start

Plex Media Server NAS & Devices
1

Server Version 1.43.0.10389
Player Version 4.157.0

Hello,

It’s been a few months or maybe a year that I have this issue, where I realize suddenly that Plex server is not reachable.

After different tests, I have found out that stopping the server, restarting, and waiting ~5minutes will solve that issue.

With your help, I would like to get to the bottom of this issue, so that it never happens again.

Immediately after this latest restart, I have downloaded the logs, that you can find in the attached archive.

Your assistance will be greatly appreciated.

Thanks !

Best regards,

Plex Media Server Logs_2026-01-29_14-14-36.zip (3.1 MB)

2

Plex Documentation → Server Settings → Network

There are incorrect entries in List of IP addresses and networks that are allowed without auth. The log entries repeat every few seconds, making it difficult to see what else is happening with the system (there are 57K+ entries for each IP address).

If the server is still unstable after correcting Allowed Networks, pull and post a new set of log files.

  • No space after the comma for each entry.
  • It looks like you are permitting individual addresses. You can use either /32 or 255.255.255.255 for the mask.

Examples:

  • Incorrect: 192.168.0.14/32, 192.168.0.19/32, 192.168.0.167 255.255.255.255
  • Correct: 192.168.0.14/32,192.168.0.19/32,192.168.0.167/255.255.255.255

When you edit/correct the entries, have a second browser window open to the Settings → Console. If the addresses are correct, you will see log entries in blue. If they are incorrect, the log entries will be red.


From Plex Media Server.log:

Jan 29, 2026 14:10:13.782 [139876205394744] ERROR - Error parsing allowedNetworks entry ' 192.168.0.245': Invalid argument [system:22]
Jan 29, 2026 14:10:13.782 [139876205394744] ERROR - Error parsing allowedNetworks entry ' 192.168.0.19': Invalid argument [system:22]
Jan 29, 2026 14:10:13.782 [139876205394744] ERROR - Error parsing allowedNetworks entry ' 192.168.0.232': Invalid argument [system:22]
Jan 29, 2026 14:10:13.782 [139876205394744] ERROR - Error parsing allowedNetworks entry ' 192.168.0.182': Invalid argument [system:22]
Jan 29, 2026 14:10:13.782 [139876205394744] ERROR - Error parsing allowedNetworks entry ' 192.168.0.14': Invalid argument [system:22]
Jan 29, 2026 14:10:13.782 [139876205394744] ERROR - Error parsing allowedNetworks entry ' 192.168.0.167': Invalid argument [system:22]
3

Thanks for the quick answer. I have adapted the list of IP addresses according to your advice. They were highlighted in blue in the console when I added them.

We’ll see if that helps, I will come back either way to provide the status.

Thanks.

4

Hello,

I am back with same issue, 7 days later.

I have attached here the logs I downloaded after server restart.

Any help or insight into the problem would be very welcome.

Plex Media Server Logs_2026-02-05_09-37-16.zip (5.9 MB)

5

Thanks for the log files.

Plex was optimizing the database during the maintenance window when it became non-responsive. For some reason the optimization never finished. It became completely non-responsive ~02:50 until it was restarted at 09:26.

Plex optimizes the database once every seven days, I took another look at the first set of log files, and the same thing happened last Thursday.

You should run DBRepair for Plex Media Server. It will optimize and reindex the database files. It does a more thorough job than Plex Media Server since Plex is stopped and the database files closed.

When you run it, use STOP then AUTO. If it finds problems it cannot fix, then EXIT and post the output to the thread. If it finds no problems or fixes any it finds, then START and EXIT.

The readme file has instructions on how to download the script and where to locate it on QNAP NAS.

It requires using SSH & the Linux command line. If you’re unfamiliar with the process, write back and someone can step you through it.

6

Hello,

This seems to be a very nice and complete tool!

I have run it, did stop and now auto. It is still ongoing, stating ‘Checking the PMS databases’ for 20minutes now.

Is there a way to know if it’s still doing anything or stuck? I suppose I will harm the DB if I kill the command with ctrl-c.

7

Don’t kill it. Let it run. It might take some time if your database files are very large.

8

ok then. Will report here once it has progressed. Thx

9

Hello,

Process is complete. A few errors in FTS indexes. The reindex step fixed it.

I have re-started the server, let’s hope it survives next weekly optimization.

I will provide a status here either way.

Thanks a lot for your help.

10

Hey. 1 week later, my server survived without disconnection.

So using DBRepair worked perfectly.

Thanks again.

11

Thanks for the update. Glad to hear things are working OK.