I performed the upgrade a few days ago and have since tried to uninstall/reinstall a few times. The issue where the server denies access “No Soup For You” keep recurring after a short time. I’m on a Synology box and don’t have the files in the locations you describe for a standard Linux install. Will there be an update soon to fix this issue? Is can I get a copy of the previous version 1.14…?
Synology DS1817+
DSM 6.2.1-23824 Update 6
PlexMediaServer-1.15.1.791-8bec0f76c-x86_64
Dustin,
Today is your lucky day. 
While I don’t condone hijacking threads, since I’m the primary Synology dev (Trumpy and I are the support team), I can help.
I will spit this out from here and link back so others can follow.Sorry Chuck, didn’t mean to hijack the thread. Figured my issue was similar to the others. Thanks for helping me anyhow 
No problem! Let’s get it resolved and you back to enjoying your system.
Ok it just happened again about 11:25am my time… Here are my logs and some snapshots from my screen.
Server IP is 192.168.1.11
My Computer IP is 192.168.1.154
Do these logs reflect the “No soup for you” occurring?
I didnt’ look through them but I grabbed the logs just after this happened. I logged out and logged back in and downloaded the logs.
Dang it, Looks like the logs cut off at 11:27 as far as I can tell. I don’t see any No Soup For You. I’ll try to recreate it again… and be faster on grabbing those logs…
Ok if there is anything to be had, this should have it. Got the No Soup For You again at 11:39Plex Media Server Logs_2019-03-20_11-40-27.zip (3.7 MB)
Ok restarted, waited 30 seconds. Logged in, noticed it was displaying my server twice (Which is typical when this happens) tried to open the settings and got the No Soup For You. I signed out. Signed back in and it showed just 1 server so I got into settings and downloaded the logs. This should have something hopefully. Is there any way to extend the amount of logs kept?Plex Media Server Logs_2019-03-20_11-46-29.zip (3.4 MB)
OK, I’ll give that a shot and post back.
This morning I
Restarted the NAS, and stopped all the programs running on the NAS
Uninstalled PMS
Removed the Plex User
Installed PMS Version 1.15.2.793
Gave appropriate rights to the Plex User, and re-launched all my other programs.
After doing all that I havent had a problem yet after several hours of using Plex. It does have me log in more often than it used to but an extra button click is much better than what I had before.
Thanks for your help.
Never mind the problem came back. I often have to sign out, then sign back in and that seems to be the temporary work around.
See this Thread.
Seems to be an issue in the latest build for a few people.
Workaround for now seems to be roll back to the latest 1.4.x OR access your server with HTTPS as this seems to also avoid the problem.
Ok just started getting it using HTTPS as well.
Exact problem here, and ive also noticed that it will only happen if i have external users playing something off the PMS, when there is no activity the issue does not present itself, at least for me. and only on the admin account that can see activity.
It seems to work fine if you use the web app, which is a newer version than the local web app.
http://app.plex.tv/
I still have the issue. I have noticed the problem only seems to happen now when I have to sign in with a pin or if i switch users and only for the admin user. Once i sign in by entering a pin code my server displays twice and any activity is multiplied by 2. At that point when i try to open the settings menu i get the no soup for you message. Logging out and back in (not switching users) seems to fix the problem. Note, this does not happen when I am logged in via the website plex.tv
So much for testing! Why am I paying premium for this kind of buggy software still!
I CANNOT access the server settings before that “no soup” error comes up. They have killed my server
