"No soup for you!" error after disk ran full

Plex Media Server Desktops & Laptops
1

Server Version#:1.18.1.2019-c186313fe
Player Version#: 4.8.3

I’m running plex on a virtual ubuntu 16.04 server. The virtual disk ran full so I increased it. I now get the following error when connecting to serverip:32400/web

No soup for you!

The server you’re trying to access doesn’t want to let you in. Make sure you’re signed in as a user with access to this server.

I also tried to upgrade from 1.11 to 1.18 which didn’t change anything. I also removed the Preferences.xml file which does not help.

2

SSH tunnel to it and reassert yourself as owner.

“No soup for you” is it telling you that it’s not accepting anything your browser is offering it from authentication to network.

SSH tunnel is the only way to get back on the loopback port (127.0.0.1) / console and get control.

3

Thanks. How can I reassert myself as the owner?

4

Anyone?

5

Sorry for the delay.

To reassert yourself as owner — CLAIM it again.

Worse case scenario:

  1. Stop Plex
  2. Delete Preferences.xml
  3. Plex.tv/destkop -> Authorized devices -> Servers - Delete the server name
  4. Start PMS
  5. open HTTP://127.0.0.1:32400/web or http://LAN.IP.of.host:32400/web
  6. Be greeted “Got It”
  7. Sign in
  8. See first-run setup wizard.
  9. DO NOT create new library sections. They still exist.
  10. Step through otherwise, setting options as you wish
  11. When at Dashboard, review and again set all other options.
6

Thanks for your further help. Unfortunately I’m still faced with the same error.
After doing steps 1 to 5 I’m not getting “Got it” but getting redirected straight to the login page. After logging in I’m again seeing the “no soup for you!” error message.
Under “aufhorized devices” I can also no longer see the server (as expected). I tried this twice with the same result.
Any further ideas?

7

Yes.

Open a terminal window

  1. Stop Plex
  2. Delete the Preferences.xml file
  3. Reclaim it again – but do not create new shares (they persist through ownership reset)
  4. Revisit Authorized devices and any existing sharing as required after reclaiming and pref tweaking
8

Unfortunately I’m not able to get to the eeclaim page. When deleting Preferences.xml and then connecting to http://ip-of-server:34200/web it just loads for a couple of seconds and then I’m getting the “No soup for you!” error (or I have to loginto my plex account first if I’m not already logged in) without ever having the possibility to reclaim the server .

9
  1. Is this all on your LAN, or it any part of it remote?
  2. If both are on your LAN, are both RFC-1918 compliant ?
  3. Is this server in a VM or Container?
10
  1. This is all my LAN. The plex server, the server where the media is hosted and my client are all in different subnets, but there are no blocks on the firewall and this setup was working without any problem for about 2 years and I haven’t made any change in the last few months. The only change was that the VM with Plex on it was running out of disk space which lead to the problem I’m now facing.
  2. Yes, my LAN is compliant
  3. It’s a VM
11

Ok… let’s make the VM PMS forget who it is and go through “reclaiming”.

It won’t know you’re the owner at first.
You will re-associate it with your Plex account.
It will think it is in a first-run setup mode , which we will skip through.
We’ll keep your data intact.

  • If the server is sharing to anyone, you’ll need to share again. (unless we do text editor surgery – your choice)
  • If you have custom settings in Settings - Server (any of the categories), you’ll need review and make certain it’s where you want.

Procedure:

  1. Stop PMS
  2. In /var/lib/plexmediaserver/Library/Application Support/Plex Media Server
  3. mv Preferences.xml Preferences.xml.prev (save the pref file)
  4. Start PMS
  5. In your existing Plex/Web browser window - Sign out
  6. Open an incognito window to http://ip.addr.of.vm;32400/web
  7. Be greeted by “Got It”
  8. Sign in
  9. See setup wizard
  10. Do Not create new library sections - SKIP
  11. Set other preferences as you deem appropriate
  12. When you arrive at the dashboard, your libraries are waiting for you.

Should the above fail:

  1. http://app.plex.tv/desktop (invoke the hosted web app)
  2. Settings
  3. Authorized Devices
  4. Servers
  5. Delete the VM’s friendly server name (and any other unused instances there).
  6. Repeat steps in section above.
Ubuntu ran out of disk space, now Server Starts but is listed unavailable
Ubuntu ran out of disk space, now Server Starts but is listed unavailable
12

Hi,

I just tried all the solutions in this forum and I don’t get greeted by Got it. I get greeted by a request to login. The server does not show up on my authorized devices list and it was removed.

13

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.