No soup for you!

Plex Media Server Desktops & Laptops
1

Server Version#: 1.15.1.710-ece95b3a1
Player Version#:

Hello everyone,

Since a few days, it’s problems when I connect to Plex via a browser …

The problem is that the problem appears randomly by putting this beautiful message:

No soup for you !

And in the navigation bar (left), I have this message:

The undefined server is inaccessible. Check that the server is running, check the network, and try again.

Specs:

  • PMS installed on Debian 9.x related to Apache 2.4
  • PMS version 1.15.1.710
  • Dedicated Kimsufi Server

Funny, I can not see the server but I can read the content that was being played, it’s weird ^^

Looking at the logs from the web interface (when I can access it), I do not find what may be wrong: frowning:

I’m interested in your ideas :slight_smile:

Thank you in advance

2 Likes
2

Since you can’t get into the Web UI, would you please log into the command line, stop Plex, and create a tar.gz of the Logs directory, in its entirety, and post it?

3

This behavior was introduced in 1.15.1.707 and remains in 1.15.1.710

At least there is a workarround: Sign-Out in the Web UI and Sign-In again.
This will work for the current session, though as soon as you close and re-open the browser, the problem will return.

2 Likes
4
  1. Try using the hosted version of the web app, instead of the local one app.plex.tv
  2. disable ‘Sync settings’ (Settings - Web App - General - ‘Show Advanced’)
5

@OttoKerner: thanks, this solved it.

The workaround is not necessary any more.

Update: seems like there is more to it, then just disabling the configuration sync. When I access my VPS instance using its own URL, and switch to my local installation, then either “no soup” is shown or my local installation is not listed in the server selection at all.

6

So this is a known problem that will be patched to the next version :slight_smile: ?

7

I do have the same problem, can you try to reproduce the issue using my procedure: [BUG] Refreshing the webapp while having a playback notification break the webapp

8

May I please see some manually captured DEBUG (not VERBOSE) log files?

  1. Verify debug on, verbose off.
  2. Recreate the problem
  3. Wait 30 seconds
  4. Stop Plex
  5. sudo tar cfz /tmp/Plexlogs.tar.gz "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs"
  6. Attach the tar.gz from /tmp here
9

same here, since upgrading from a 1.14 to current version on Windows. Yes, signing out and back seems to clear it… worst thing I have seen in a new release in all my years using Plex!

10

Hi guys,

For now, I will update PMS to 1.15.1.780 and I would see if there is better.

If it does not matter, I’ll put the logs on the post.

Thank you for your help anyway, you are super nice :slight_smile:

13

I just install 1.15.1.791 and I still have the “no soup for you” problem… Yes, signing out and back in clears it - temporarily. If you close the tab (Chrome) and try a local web version, its “no soup” all over again. I do not see the same behavior on good “old” IE 11 or FireFox right now.

1 Like
14

A server update doesn’t clear it. You need to use the hosted web app, app.plex.tv because only this has the fix.
The web app included with the latest PMS package is still too old.

1 Like
15

Hi, these are the PMS logs, I hope this will give you an idea of the problem;)

PMS Web: Version 3.83.1
PMS Server: Version 1.15.1.780

Plexlogs.tar.gz (32.4 KB)

16

Thanks for the logs.

Are you remote from the system?

Acording to the logs, someone (presumably you) is communicating with PMS remotely.

Are you able to SSH-tunnel to it and communicate over the tunnel as the next step?

ssh -L 8888:127.0.0…1:32400 ip.addr.of.system
Open http://127.0.0.1:8888/web in the browser

I realize this may be impractical if you are remote given Plex Relay is the only feature operating and Plex Relay won’t work for this level of access.

17

PMS Server is installed on a dedicated server so all access is remote via SSH

I have several users using web access through my subdomain “plex.domain.tld” on Windows web browser and other by the Plex mobile application.

N.B : PMS Server update to 1.15.2.793-782228f99

18

Not sure if my issue is quite the same but lot of the symptoms seem to be though i do not typically see the “No soup for you” message. Basically once i go to my PMS via a custom domain, select the user, enter PIN. Then i click on anything really and the page just refreshes and does not actually dive into say a list of episodes for series from the on deck area, also from the activity button at the top right if anything is playing it will be listed twice.

My workaround so far has been to Sign-out and then back in again, entering pin and everything works for some time. Come back several hours later or the next day and it i will have to go through that process again whether I leave the browser open or not. Only seems to be web player issue as other devices not using the web player do not appear to be affected.

PMS 1.15.2.793
Web player 3.83.1

Annotation%202019-03-23%20023215

19

Log files please?

Recreate the problem,
Wait 30 seconds.
Stop Plex

Manually gather, as a tar.gz “/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs”

20

Sorry my bad taught i had already attached them, here they are.

Plexlogs.tar.gz (2.1 MB)

21

Wow, talk about a lot going on in there.

From the bottom (newest) to top (older)

  1. Database access is very slow. Judging by what is happening above it, the CPU might be maxed.
Mar 23, 2019 16:09:53.751 [0x7f2accff9700] INFO - [PlexRelay] Allocated port 17363 for remote forward to 127.0.0.1:32401
Mar 23, 2019 16:14:55.073 [0x7f2accff9700] WARN - SLOW QUERY: It took 330.000000 ms to retrieve 50 items.
Mar 23, 2019 16:14:55.084 [0x7f2aae7fc700] WARN - SLOW QUERY: It took 340.000000 ms to retrieve 51 items.
Mar 23, 2019 16:14:56.141 [0x7f2a8affd700] WARN - SLOW QUERY: It took 220.000000 ms to retrieve 50 items.
Mar 23, 2019 16:15:33.205 [0x7f2aaf7fe700] ERROR - QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
Mar 23, 2019 16:36:56.254 [0x7f2afd7fa700] WARN - SLOW QUERY: It took 240.000000 ms to retrieve 50 items.
Mar 23, 2019 16:36:56.307 [0x7f2a8bfff700] WARN - SLOW QUERY: It took 490.000000 ms to retrieve 51 items.
Mar 23, 2019 16:48:56.713 [0x7f2b057fa700] WARN - NAT: PMP, got an error: Not Supported by gateway.
  1. I see attempt to play a file and invoke the transcoder which fails miserably after 48 seconds.
Mar 23, 2019 12:37:39.209 [0x7f2b4330f700] WARN - avcodec_open2 returned -1313558101 for encoder 'h264_nvenc'
Mar 23, 2019 12:37:39.209 [0x7f2b4330f700] ERROR - [FFMPEG] - libva: va_getDriverName() failed with unknown libva error,driver_name=(null)
Mar 23, 2019 12:37:39.209 [0x7f2b4330f700] ERROR - [FFMPEG] - Failed to initialise VAAPI connection: -1 (unknown libva error).
Mar 23, 2019 12:37:39.210 [0x7f2b4330f700] ERROR - [FFMPEG] - Cannot load libcuda.so.1
Mar 23, 2019 12:37:39.210 [0x7f2b4330f700] WARN - avcodec_open2 returned -1313558101 for encoder 'h264_nvenc'
Mar 23, 2019 12:37:39.211 [0x7f2b4330f700] ERROR - [FFMPEG] - libva: va_getDriverName() failed with unknown libva error,driver_name=(null)
Mar 23, 2019 12:37:39.211 [0x7f2b4330f700] ERROR - [FFMPEG] - Failed to initialise VAAPI connection: -1 (unknown libva error).
Mar 23, 2019 12:39:05.501 [0x7f2a8affd700] WARN - SLOW QUERY: It took 43480.000000 ms to retrieve 6 items.
Mar 23, 2019 12:39:05.501 [0x7f2b29ffb700] WARN - Transcode runner appears to have died.
Mar 23, 2019 12:39:05.574 [0x7f2a8affd700] WARN - SLOW QUERY: It took 290.000000 ms to retrieve 50 items.
Mar 23, 2019 12:39:05.623 [0x7f2a89ffb700] WARN - Got a request to stop a transcode session without a session GUID (or with an invalid one).
Mar 23, 2019 12:39:05.662 [0x7f2b29ffb700] WARN - SLOW QUERY: It took 280.000000 ms to retrieve 14 items.
Mar 23, 2019 12:39:05.670 [0x7f2a8a7fc700] WARN - SLOW QUERY: It took 670.000000 ms to retrieve 51 items.
Mar 23, 2019 12:48:41.030 [0x7f2acd7fa700] WARN - NAT: PMP, got an error: Not Supported by gateway.
  1. And the apparent root case is a DNS lookup failure.
Mar 23, 2019 10:21:53.799 [0x7f2b057fa700] ERROR - Error issuing curl_easy_perform(handle): 6
Mar 23, 2019 10:21:53.800 [0x7f2b057fa700] WARN - HTTP error requesting PUT https://plex.tv/api/servers/ed72f5354bf4d691bef09b903e7b85ed7924f912/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=857e6776-be2e-428c-ab40-63da2673d80c (0, No error) (Could not resolve host: plex.tv)

Please check and verify networking settings.

22

DNS appears fine to me, response from far end getting a 404 but that is probably cause the tokenid is was masked in the warn message i copied it from. But it resolved. CPU can get high at times, depending on how many streams are going. Rarely have playback or buffering issues. Just this pesky re or losing auth issue with the web player.

PING

root@MrPlex:~# ping plex.tv
PING plex.tv (52.16.101.236) 56(84) bytes of data.
^C
— plex.tv ping statistics —
7 packets transmitted, 0 received, 100% packet loss, time 5999ms

Nslookup

root@MrPlex:~# nslookup plex.tv
Server: 10.87.0.250
Address: 10.87.0.250#53

Non-authoritative answer:
Name: plex.tv
Address: 52.18.254.79
Name: plex.tv
Address: 52.50.147.131
Name: plex.tv
Address: 63.32.177.143
Name: plex.tv
Address: 52.50.215.159
Name: plex.tv
Address: 52.16.101.236
Name: plex.tv
Address: 54.154.198.3
Name: plex.tv
Address: 54.171.218.244
Name: plex.tv
Address: 52.31.211.151

Curl to the url in the warn message

"root@MrPlex:~# curl https://plex.tv/api/servers/ed72f5354bf4d691bef09b903e7b85ed7924f912/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=857e6776-be2e-428c-ab40-63da2673d80c
[1] 17065
root@MrPlex:~#

Annotation%202019-03-23%20183427
Annotation%202019-03-23%201834271014×493 99.7 KB