Looking for a fix for (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.)

Plex Media Server
1

Server Version#: 1.18.2309
Player Version#:

hello
Im trying to start my plex service on my NAS (synology DS1816+).
I am unable to setup my plex i try to uninstall and reinstall the app. I also created a new account to see if it would fix it no luck. I keep getting this error.

error
error995×502 18.6 KB

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.

Does anyone know a fix for this?

2

Syno FAQ (you can search that term)

FAQ #25 – first thing to try
FAQ #23 – If #25 fails

3

when i go to plex and authorized devices i only get windows web plex
and when I open Preferences.xml” → with Text editor. i don’t have any of these setting
a. PlexOnlineToken="-value-"
b. PlexOnlineUsername="-value-"
c. PlexOnlineMail="-value-"
d. PlexOnlineHome="value"

auth.dev
auth.dev1024×488 22.7 KB
xml
xml1087×455 29 KB

4

I have same rpoblem as supertechtips. Do you have solution?

5

i have a same problem , what is the solutions please

7

Had the same problem, just couldn’t get into the Plex server. Ended up diving into the logs and found this:

Jul 18, 2020 22:09:25.145 [0x7faf914b7700] DEBUG - Request came in with unrecognized domain / IP ‘nas.my.domain’ in header Host; treating as non-local

In my local network I use a “my.domain” domain name, so when navigating to devices it becomes “http://device.my.domain” (where in the case of my Synology “device” would be “nas”). Seems like Plex doesn’t like that. When I switched to accessing Plex directly via the IP of the Synology (http://192.168.0.5:32400/web) it finally worked.

11 Likes
8

Just ran into similar setting up Plex with a public IP; it seems to really want you to access it from a Class C private address for initial setup. Setting up an SSH tunnel to link a local port to 32400 on the server sorted it out:

  1. Establish the tunnel (this works for Linux and MacOS; it will work from inside WSL on Windows): ssh -L 9999:localhost:32400 user@plexserver
  2. In your browser, navigate to plexserver:9999/web

It should now allow normal login and claim, and you can then access it normally through plex.tv or the normal port, without the tunnel. This is not specific to synology, but should work for synology. In this case plex is running on a raspi outside my LAN (topology: ONT -> PoE Switch -> PI and router, each with their own static public IP).

2 Likes
10

Hi, Any soloutions for this yet? my Plex has started doing this and i really dont want to rebuild the whole thing.

11

I linked the procedure for recovering from “No Soup for You” (server credentials lost / damaged) in my post above.

Those of you who are still having trouble: To be certain, you followed the sequence step by step without skipping any ? (Important)

Also as stated above:

  1. RFC-1918 Private Network addressing is use on both server and accessing client (same subnet)
    -or-
  2. SSH tunnel to the IP of the server on a different subnet
12

I still have the issue. reinstalled my nas from scratch. still not able to access my server and add local libraries.

15

thank you.
please post the link of the post so i can follow-up there

16

Same Story here…

17

There is an additional resolution method to try

18

Why is this so needlessly complex! What was wrong with a classic local login?

Ugh, sorry- just needed to vent. Sounds like a few others here need to as well.

19

I don’t understand either. Truly don’t. I’ve argued my case and, well, this is what we have.

:man_shrugging:

20

I’ having the same issues All of the above solutions all ended in no soup for me. Attached are my logs hopefully I can come to a solution. I don’t mind starting from scratch. (File removed)

22

Solved! TY the quick connect was the issue.

24

Please, I beg all of you, help. This Plex is reaching my limits. I feel this is my last strain of patience.
I have a Synology NAS, DSM6, latest updates on it, including the recent Plex version manually installed.
I used to have a Windows Plex server that I removed, after which I uninstalled the Plex server from my NAS and deleted my Plex user and Plex folder manually from my NAS.
After I reinstalled Plex Server on my NAS, the no soup message started to appear.
I tried all possible option changes for port routing, ip adresses and so on and ended up having the same settings as before.
So:
ASUS AX58U router connecting with ppoe and 32400 router manually router for my NAS (TCP and UDP)
Plex server on my nas manually deleted and reinstalled (I tried the sign out on all portals and renaming the preferences.xml file for it to be regenerated - did not worl)
I deleted the regedit Plex Media Server files (even though it has nothing to do with the Nas Plex Server)
I tried the incognito sign in. There is no option for me to reclaim the server.
I tried restarting the NAS a couple of times, combined with reinstalling the Plex server.
Please, please, please! I beg you, please! Have mercy!

25

what is the IP address of the computer you are using?
what is the IP address of the Synology?

26

Hello,
I tried the incognito option. Does not work.
The IP of my computer is 182.168.50.109 and that of my Synology is 182.168.50.163. I noticed that my Plex was working on TV only when my Windows Plex server was on. After I uninstalled the Windows Plex Server, the Synology Plex Server was not visible. After reinstalling everything (and deleting the Plex user and Folder on Synology), the No soup for you message appeared.