What on earth has happened to Plex on QNAP?

Plex Media Server NAS & Devices
1

Server Version: 1.18.2

Since about version 1.16 Plex on QNAP is constantly crashing, I can watch maybe 2 episodes before it becomes unavailable and I have to stop and restart the app. I’ve seen several other threads on here about this and none of them have any kind of indication that it is being looked at.

At this rate there is no point in me renewing my Plex pass as it is unwatchable and completely unfit for service for watching my library remotely?

Are there any suggested fixes?

2

May I see the log files? I might be able to glean the cause if it didn’t roll out the end of the buffer.

3

Sure I can PM them to you?

4

It’s not going well with Plex on QNAP for me.

  1. I’m now hitting issues with the web client (Unreachable) - see image
  2. An iPhone (on 12.4.3 running the latest Plex app) which can’t see the server as online
  3. The iPhones on 13.2.3 can’t back up the photos to PMS as JPG files.

Screenshot from 2019-12-02 21-43-56
Screenshot from 2019-12-02 21-43-56953×524 103 KB

5

@MiloPlex

While this seems odd:

  1. Reset the customizations in the app.
  2. When you do, it will let you reselect the server.
  3. Now try again.
6

For which of the 3 issues, and where? Thanks

7

Start at the bottom and work backwards.

Clearing the customizations is something discovered to address multiple issues in the Android app. I’m hoping it works here too

8

This is exactly what i get as well -seems to coincide with library scans too!

9

Same issue - shows server as unreachable. It finds a new server nearby…which is the same old server. Problem is I lose all watched history, etc.

Any suggestions for re-establishing connection or restoring history from original server?

10

Owning qnap, we’re all familiar with SSH

  1. Sign out the web browser
  2. close the brower
  3. Open a Putty or SSH session to the QNAP with attached tunnel forwarding:
ssh -L 8888:127.0.0.1:32400   ip.addr.of.qnap

windows-putty users use this reference: Forward source port 8888 to destination port 32400

With this ssh tunnel established, let it sit there.

Should this not allow to regain the connectivty / ownership:

  1. Stop Plex.
  2. Rename “Preferences.xml” to “Preferences.xml.old”
    (/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Preferences.xml)
  3. start plex
  4. Open 127.0.0.1:8888/web again
  5. It will want to setup a new server
  6. SKIP creating new library sections. your sessions still exist.
  7. Setup everything else as you want.
  8. When you arrive at the dashboard, you should be signed in and your existing libraries present.
11

I’m connecting to it directly via local IP, even on the same machine it has problems!

12

Also is Plex aware that the crash uploader isnt working?

I have tried the above btw - same thing happens - its definitely the Plex backend that is causing problems, im trying to monitor logs now

Dec 03, 2019 19:04:18.271 [0x7f9e8fcab700] INFO - Crash Uploader - Platform: Linux ServerUUID: f6c13af512e165b2e8ba724560da7878e2f3153e UserId: Version: 1.18.2.2058-e67a4e892
Dec 03, 2019 19:04:18.304 [0x7f9e94df7740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dec 03, 2019 19:04:20.276 [0x7f9e94df7740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dec 03, 2019 19:04:20.276 [0x7f9e94df7740] ERROR - Failed to upload crashdump 6752afc9-2efd-35c9-3faf324c-21c41795: 429
Dec 03, 2019 19:04:20.276 [0x7f9e94df7740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dec 03, 2019 19:04:22.077 [0x7f9e94df7740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dec 03, 2019 19:04:22.077 [0x7f9e94df7740] ERROR - Failed to upload crashdump 61e32f8c-8545-6633-21b1de55-0cade87a: 429
Dec 03, 2019 19:04:22.077 [0x7f9e94df7740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dec 03, 2019 19:04:24.079 [0x7f9e94df7740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dec 03, 2019 19:04:24.079 [0x7f9e94df7740] ERROR - Failed to upload crashdump 03ea5f90-86b8-1508-5d4dce9a-3ea1cfe8: 429
13

That’s a Throttled message.

The host is crashing so much, trying to upload so many reports, it’s making your uploads slow down and wait.

14

I’m running plex now and I’m following the logs for ERROR, just waiting for it to crash

15

image
image1398×358 180 KB

Ok so exactly the same problem again - there is NOTHING in the logs about this (that makes sense anyway), Videos play fine while this is happening. It is just as if the front-end cant speak to the back-end.

Really need a solution on this as it is unusable

16

For one thing, the transcoder does not like the media file. It may play fine but the time indices are all messed up.

Does it do this for every file?

17

Looks like it yes - that seems to be a very normal error message when anything is playing through Plex - old or new.

18

I need to see the log files at your earliest convenience.

Please make sure DEBUG logging is enabled but VERBOSE is off.

Please start a playback, let it play for 30 seconds then stop.
wait 30 more seconds for buffers to flush to disk.

Grab (download) the Log ZIP file and attach it here so I can look

19

Ive sent them in our private message.

Verbose is off and Debug is on.

20

The PMS version 1.18.3.2111 that I applied tonight appears to have resolved the web client issue for me (with the server flagged as unreachable).
OSX Plex client appears to still work fine, as does the iOS Plex app (only when using the “experimental” enhanced video player…but that’s another issue).