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 NAS & Devices
1

Server Version#:
Player Version#:

Hello,

I’m currently using a MyCloud PR4100 NAS for my Plex Server and I keep getting the following message when trying to link the server to the Plex app for the first time:

““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 have done multiple formats and re installs of the Plex App on the MyCloud Device and have used different plex accounts. I have also gone to the extent of purchasing another MyCloud PR4100 and a Synology DS920+ to see if it was a hardware error. After failing to link the NAS to the Plex app on both, I’ve come to the conclusion that it is an IP error. I have limited knowledge about IP things so I’m unable to diagnose this myself.

Please help, I’ve been stuck on this for a month now.

Thank you!

2

That should mean the server is signed into as admin of a different account. I would look at the server logs to see what account the server is signing itself into when it starts up.

Since you seem to be starting from scratch then I would deleted the preferences.xml file in the PMS folder that contains that login info then restart server. https://support.plex.tv/articles/202915258-where-is-the-plex-media-server-data-directory-located/

3

I am encountering the same problem. I’ve tried deleting the Preferences xml file and even the entire PMS directory, which did not help. The content of the Preferences.xml file (somewhat redacted) is just

<?xml version="1.0" encoding="utf-8"?>
<Preferences OldestPreviousVersion="1.20.2.3402-0fec14d92" MachineIdentifier="6ddb..." ProcessedMachineIdentifier="9aaf..." AnonymousMachineIdentifier="cf50..." MetricsEpoch="1"/>

No account seems to be configured. I’ve looked at the logs and have no idea what I should be looking for; grepping for user or something just turns up the crash reporter process launching with --userId=NOUSERID which isn’t helpful.

4

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