Server Version#:1.15.1.791
Player Version#:
Hi all I did the update and now my plex keeps saying No soup for you! I rebooted and still does the same thing any ideas?
Server Version#:1.15.1.791
Player Version#:
Hi all I did the update and now my plex keeps saying No soup for you! I rebooted and still does the same thing any ideas?
I am getting the same error. If i use the admin account and go to settings everything dissapears, i have to restart plex then normal users can see my library’s again.
Server Version#:1.15.1.791 and
Server Version#:1.15.2.791
at Debian 9
i have the same error. i got this after update to 1.15. first at beta. so i downgrade to 1.14 and it works.
now i upgrade to the stable version 1.15 an got the same error again.
logs are at debug level if someone want it. at a first look, i don’t see anything.
If the connection works, i see my server 2 times.
I am also having the same error, but in Linux just to be clear.
Yup. Seems we have an issue folks. 1.15.2… No soup for me.
Where can we download a previous version? There should be an option on the Download page for this. Cutting into my Star Trek time man.
i think, i have a 1.14 version on my server i you want, i can give you a dl link.
Have you all tried to use the hosted web app?
app.plex.tv
I have the same issue, screenshots of some of the javascript errors on another thread.
plex.tv works fine, but is by no means the preferred option.
Ive attached more details on this thread in the off chance a dev from plex ever reads these.
Safari and Firefox, Debian Linux as server. 1.15.1.710
I have just installed version 1.15.2.793, issue may be resolved. But sometimes the issue does not show up for the first use, will reply back here if the issue shows up again.
Not sure if it is the same, but I was seeing the same issue with my server running on a mac. I could get to my server just fine from the hosted app, but not my local app. The issue was resolved by logging out of Plex locally and logging back in. Might be worth a try.
Hi sgraham884,
Thankyou,
It was an issue for quite a long time - 3 weeks perhaps, multiple logouts of clients, server etc. Even cleaning out all the old cookies, trying different browsers etc. Not sure what the problem was/is but perhaps 1.15.2.793 has fixed it now. Ironically without having to log out.
Thanks again.
Same issue here
I have version 1.15.2.793 and now every time I log in, I get double the number of dashboards in the Activity drop-down. If I click on one of them, I get the error No Soup For you. If I log out, I can then log back in and everything works fine…ONCE. Then if I go back without logging back in, I get the same issue.
If I use the https://app.plex.tv/desktop I do not get the issue at all, but that does not come up when I double click on the server icon running in my task bar. It is inconvenient. I can work around it, but this just started happening after my lastest update.
Any thoughts or suggestions?
I’m also getting this, I reverted back to 1.13.x and it’s much improved, but still happens. I notice that when it happens my PMS has stopped completely as well. I restart PMS and can usually get back in.
I’m also experiencing the No soup for you! You do not have access to this server after upgrading to Version 1.15.2.793. I following the instruction in the link below to clear my plexonline username, token, mail, and home. Everything resets but when I try claiming the server again it gives me the same errors.
Anyone got an older version?
I did some clean up work, ensured that the dnsdomain name was correct (accessing via an internal DNS server, make sure on linux that /etc/resolv.conf only contains
domain your.domain
and not
search your.domain
domain your.domain
as you will get errors in the debug log about clients connecting to unknown address and it assuming they are remote connections. ps. you have to restart plex.
you can check if its a problem by running hostname --fqdn and if its not the hostname you are accessing it will cause the unknown address error.
Not sure if thats actually done anything useful but, less errors are always good.
This appears to have been fixed in 1.15.4.993. I was unable to install this update from my server Admin Settings page (no soup error), so I went to https://www.plex.tv/media-server-downloads/ and downloaded and installed it manually. The update succeeded and I am not getting the “No soup for you!” error anymore.
V 1.15.5.993 does fixed it for me too.
Looks like WebClient 3.95.2 and Plex 1.15.4.993 it looks like it has been fixed. I would like to thank the Plex developers for getting this defect fixed!!!