PMS not installing or upgrading on qnap

Plex Media Server NAS & Devices
1

I have a TS-453Be (F/V: 5.2.6.3229, 8Gb ram) also a TVS-463 (F/V: 5.2.7.3256, 16Gb ram).

PMS won’t upgrade from V1.42.0 which was installed 18/07/2025. On the TS (which isn’t my main PMS) I tried completely uninstalling it to start again but it won’t even reinstall now. I have tried the one on the qnap store and the latest. Am starting to get frustrated with it. Works fine on My ML350Gen9 under linux mint but that is not the one I want to leave running all the time.

Thankfully the TVS still keeps plodding along.

If anyone has any ideas it would be much appreciated.

Thanks

Steve

2

The one from plex.tv is the one you want.
Could you screenshot the error you get or whatever makes you think it failed?
The more detail you give us, the more Chuck and others can help.
For example did you get to the point where you’ve extracted the .qpkg and then

To setup the server, open a browser window and go to http://local.nas.ip.address:32400/web (e.g http://192.168.1.5:32400/web).
3

Uploading and processing. that’s it. can sit there for hrs and do nothing. As above, they both had 1.42 from plex.tv have not taken the last 2 updates. qnap store was an absolute last resort. other apps are updating normally.

4

depending on your library size we have seen up to a week to upgrade some libraries.

5

This.

During the first startup, a process called migrating database gets run. You should be able to see a message from PMS that it’s busy. The message is something like

<Response code="503" title="Maintenance" status="Plex Media Server is currently running database migrations."/>

I think you see this message when you visit the IP address:port, e.g.

http://local.nas.ip.address:32400/web (e.g. http://192.168.1.5:32400/web)

It might also appear from going to http://local.nas.ip.address:32400/identity
I doubt you would need to use https though.

Interrupting migration could cause corruption. If so you may need to restore a backup db.
Let’s hope not, but it’s easy enough. ChuckPA/DBRepair is a great utility for checking/restoring/repairing.

6

they don’t even get to that stage. when uploading and processing they don’t even get to 1% processing the installation. no notifications come up to say it is even installing. sorry I didn’t put it in the first post but these are Qnap nas. I have had them upgrade before and yes they do take a long time as my db’s are quite large. but this time they don’t even get to that stage.

7

How big are your databases ?

Do you mean –

  1. Uninstalled in App Center
  2. (RE)Installed (Manual Install) in App Center?

This is what’s not working?

8

The TVS has about 5400 movies and 23000 TV episodes, which is less than half of what used to be on it. the rest I have moved with all the main directories to my backup server, the ML350Gen9 as it has 88Tb of space. The qnap’s are the ones I run virtually 24/7. the TVS won’t let me upgrade from 1.42.0 to the latest as a manual install. The TS which is just a backup of the TVS, was doing the same, so because it is not so important I thought I would uninstall and start from scratch. first try didn’t work So I installed 1.30 from app centre after cleaning out my plexdata directory so it wouldn’t pickup on anything previous. It now seems to be installing on the TS, have been able to open it, but it is still trying. when and if it opens I will then try and upgrade it with the latest before I setup any Libraries. The TVS, thankfully is still plodding away on 1.42.0 thankfully as that is what we watch all the time.

The TS has taken the 1.30 from the app centre will now try to manual install 1.42.2.

Well, no cigar on that happening. will try some older updates tomorrow.

Thanks

9

May I see the server logs please?

It’s not possible to diagnose without DEBUG server logs.

SUPPLEMENTAL:

I’ve been thinking about how this could get corrupted.

Database Cache Size

If you make it too big, too much data (both read and WRITE data) will be held in memory. Data to be written should NOT be held in RAM.

I have 119646 episode files in my QA DB with a DB Cache Size = 40 MB (default).
I have never had a database corruption.

119649
[chuck@glockner qa.2001]$
10

Hi ChuckPa. the server logs for the TVS are 8.5mb which it doesn’t like. is there some of the logs I can remove to get it under the 8mb upload size. there are 5 server logs in there @ 10.5 MB each.

I had changed my cache to a higher number on the TVS but that was after I had the problems. I have now changed that back to the 40.

The TS under 1.30 doesn’t have it. TS server logs below.

Plex Media Server Logs_2025-10-08_06-19-50TS.zip (226.3 KB)

11

@sanangelis

In the logs you just sent, for future reference, unless I request them, you can skip ALL the com.plexapp log files.

The only ones I’m really interested in are Plex Media Server.log and it’s 5 most recent rollovers. If you’ve set retention longer then that would explain why the ZIP is so big.

I did get enough info from what you shared to take this further and show you another method to get on track.

I have taken some time to write up how to install manually (as in “really manually” :slight_smile: )

Not knowing where the problem is of you being able to 'Manual Install" in the GUI, Here is a 100% manual method. It bypasses the GUI.

This is the completely manual method. Let me paste and then describe it

ASK IF YOU HAVE QUESTIONS :slight_smile:

( This is my example. Specific details for you are below)

      1 [~] # sudo bash 
      2 [/root] # cd /share/Public
      3 [/share/Public] #
      4 [/share/Public] # wget https://artifacts.plex.tv/plex-media-server-stable/1.32.8.7639-fb6452ebf/qnap/PlexMediaServer-1.3        2.8.7639-fb6452ebf-aarch64.qpkg
      5 
      6 --2025-10-07 17:02:23--  https://artifacts.plex.tv/plex-media-server-stable/1.32.8.7639-fb6452ebf/qnap/PlexMediaServer-1        .32.8.7639-fb6452ebf-aarch64.qpkg
      7 Resolving artifacts.plex.tv... 2a06:98c1:3103::6812:2433, 2a06:98c1:310b::ac40:97cd, 104.18.36.51, ...
      8 Connecting to artifacts.plex.tv|2a06:98c1:3103::6812:2433|:443... connected.
      9 HTTP request sent, awaiting response... 200 
     10 Length: 92433329 (88M) [application/octet-stream]
     11 Saving to: ‘PlexMediaServer-1.32.8.7639-fb6452ebf-aarch64.qpkg’
     12 
     13 PlexMediaServer-1.32.8.7639-fb6 100%[=======================================================>]  88.15M  64.2MB/s    in 1        .4s
     14 
     15 2025-10-07 17:02:24 (64.2 MB/s) - ‘PlexMediaServer-1.32.8.7639-fb6452ebf-aarch64.qpkg’ saved [92433329/92433329]
     16 
     17 [/share/Public] # ls *.qpkg
     18 PlexMediaServer-1.32.8.7639-fb6452ebf-aarch64.qpkg
     19 [/share/Public] # chmod +x *.qpkg
     20 [/share/Public] # ./PlexMediaServer-1.32.8.7639-fb6452ebf-aarch64.qpkg
     21 Install QNAP package on TS-NAS...
     22 ./
     23 ./qpkg.cfg
     24 ./built_info
     25 ./qinstall.sh
     26 ./package_routines
     27 3717+1 records in
     28 3717+1 records out
     29 92408470 bytes (88.1MB) copied, 0.929462 seconds, 94.8MB/s
     30 90235+0 records in
     31 90235+0 records out
     32 92400640 bytes (88.1MB) copied, 0.930549 seconds, 94.7MB/s
     33 PlexMediaServer 1.30.0 is already installed. Setup will now perform package upgrading.
     34 Firmware check is fine.
     35 Stopping Plex Media Server...
     36 /etc/init.d/plex.sh: line 216: kill: (18442) - No such process
     37 Link service start/stop script: plex.sh
     38 Set QPKG information in /etc/config/qpkg.conf
     39 Starting Plex Media Server...
     40 [/share/Public] #
     41

0; ssh into the NAS and exit their text menu system
1: elevate your privilege to ‘root’ (above admin)
2: go to the Public shared folder
3: Confirm we’re where we want to be
4: Download the Plex package directly into the NAS
(My file is different than yours. I’ll list yours below)
6: wget is resolving the request and getting to work
11: The Plex QNAP package has been received and is being saved
13: Transfer stats , final filename, and bytes transferred
17: using the ls command, confirm the file is there
19: Make it executable (like a program)
20: Now run it. (Yes, QNAP has a strange method of installing packages)
21: Observe App Center getting involved
22-32: The various pieces and stages of the prep
33: App Center now acknowledging it’s an upgrade and will do so.
34-38: Completing the upgrade (moving the files around)
38: Recording this version as the Installed version
39: Start
40: Back to the prompt

Your steps

  1. SSH into the QNAP
  2. sudo bash and get root privilege
  3. cd /share/Public
  4. wget this file (like I did above)
https://artifacts.plex.tv/plex-media-server-stable/1.32.8.7639-fb6452ebf/qnap/PlexMediaServer-1.32.8.7639-fb6452ebf-x86_64.qpkg
  1. It will end up in /share/Public
  2. Make it executable
  3. Run it
  4. Watch QTS install it.
1 Like
12

That worked. I know a bit about how to use putty now.

13

Plex Media Server Logsonly_2025-10-08_06-03-49TVS.zip (3.9 MB)

as per request.

now that I have done that with the TS, can I now upgrade it to the 1.42.2 the same way

the TS is showing the update in plex. didn’t see anything in qts until I refreshed it.

And sorry I am new to Linux, so big learning curve on the terminal.

14

@sanangelis

Now that you have PMS updated to something more recent,

You should be able to:

  1. Download the current version
https://artifacts.plex.tv/plex-media-server-stable/1.42.2.10156-f737b826c/qnap/PlexMediaServer-1.42.2.10156-f737b826c-x86_64.qpkg

  1. Try to upload it via Manual Install in App Center.
    – If it fails, you’ll eventually need QNAP’s help to fix that

  2. If you repeat what we did a bit ago but use this new 1.42.2 version, you’ll be running on current PMS.

It will buy you some time to figure out why QTS/App Center are misbehaving.

15

look like I will be doing it your way from now on. not working in app centre.

When I put in a ticket to qnap all I got back was they don’t support anything after 1.30

1.42.2 now installed on TS.

will try the same on TVS. I removed a lot of media on TVS, should I use the optimisation in plex or use you script, (which I have already downloaded)

16

I would use a mixture

  1. Scan files
  2. Empty Trash
  3. Clean Bundles
  4. DBRepair - Auto

Seems to provide the best results because I don’t peek into the DB

17

Thanks heaps for the info. have been tearing what’s left of my hair out over this. Now I just have to hope that the ML350G9 will appear in plex.tv on my pc soon, I can find it in plex.tv on the server so it should turn up soon.

Thanks again

18

Which OS are you running on that Looks like Mint?

Whether Windows or Linux, you must, at least one time, enable Remote Access for it to “Publish” itself to Plex.tv

It is listed on Plex.tv (2 minutes ago as I write this)
but is NOT published

ALSO.. You should solve this:

192.168.1.200, 192.168.1.142, 192.168.1.171, 192.168.1.205,

it has 4 adapters showing.

PMS does not do well with 4.

You are far better off making them a Bonded adapter

19

just read that and did it, but not available outside my network

what is a bonded adapter? probably find it on google

and yes mint

20

Checking again.