Plex QNAP - No Soup for you after upgrade

Plex Media Server NAS & Devices
1

Server Version#: 1.20.1
QNAP FW: 4.5.1.1465
Player Version#: NA as no player can connect

Reinstalled PLEX Media server on QNAP and now cannot access the local server. Plex web client comes up after clicking the Plex icon in web QTS, but offers message “No Soup for You!” The server does not want to let me in.

What would be my next step.

I was previously working on 1.19 version.

2

I have also uninstalled and installed v1.20.4 and receive the same error.

I also saw a posting to remove lines from Preferences.xml, but those lines were not there.

How do a reset and reconfigure? I have uninstalled and made sure all the dirs and files are removed…

I am running out of ideas…

3

Because of how QNAP’s QTS makes us do things.

Given you uninstalled from the QNAP – this means all the metadata AND the whole server itself – is gone

One thing which happens, (there’s no way we can prevent it),

Plex.tv still thinks your old server ID numbers are installed on that system.

Therefore, the solution is simple – albeit not too intuitive,

  1. Make certain the QNAP PMS is stopped.
  2. Open https://app.plex.tv
  3. Settings -> Authorized Devices -> Servers
  4. Click the “X” and REMOVE the QNAP server instance(s) – you’ll likely have at least two
  5. Clean up anything else there which makes sense to you
  6. When done – Sign out (upper right corner under your avatar)

Now close the browser window

  1. Start PMS
  2. Open http://ip.addr.of.qnap:32400/web
  3. It should make more sense now coming in.
4

So I’ve completed these steps myself but I still get no soup for you

5

I also have the exact same issue and the solution provided above does not work.

6

I have upgraded to 1.20.5 and this corrected my issue.

Thanks
Gary

7

This solution did not resolve it for me I’m on 1.20.5.3600 and it’s still saying “No soup for you”

8

@Vexx109

  1. IP of the QNAP (LAN)
  2. IP of the PC (LAN)
  3. No proxy , FQDN, or any such other things?
9

Okay. your #3 question is what answered it. I was using my FQDN (local DNS) to get to it. Is there a reason that breaks it?

10

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