Server Version#: Linux 4.19.107-Unraid
Player Version#: Version 4.22.3
I have recently switched my server from a windows machine to an Unraid server. When I installed PMS on the Unraid server via Docker, I was able to get though the install and launch the GUI, but I continually get the “No Soup for You” error and cannot access the server (but I can see it in the “authorized devices” list…just can’t access it).
I have gone though all the steps here, and none of it solves the problem:
I also tried uninstalling the old plex server, so that’s no longer running. I also deleted all Plex registry entries on the old windows server. I know I will have to rebuild my library, and that’s fine…I just want to get plex back up and running.
After weeks of trying to make this work, I gave up and installed Emby. It is nowhere near as good as plex, but it installed without issue. I would really rather go back to plex but I have no idea how to fix this problem.
I also tried reinstalling a new install of PMS on the windows machine (after uninstalling the old instance of PMS and deleting all plex registry entries), but still go the “no soup for you”.
I finally got it to work. None of the “support” articles were of much help, but how I ended up resolving it was by:
Connecting a monitor, keyboard and mouse to the server (which is normally headless), and clear the browser of history and cache,
disconnect the server from the internet
accessing the GUI from localhost:32400/web/
from there I was finally able to see the server
reconnect the server to the internet
before logging in (I tried that and it went right back to “no soup for you”), click the “claim server” button; I was then prompted to login.
the server was claimed and I’m now able to access server settings.
In the end, if my unraid server was able to access the Plex sign-in servers during this process, it would not work. They must have some machine identifier somewhere that is preventing you from just logging in as a fresh server.
