Server Version#: Not sure, since the Plex Web app says my server doesn’t exist if I try to view settings.
Player Version#: See Above
I’m running under Windows 10 Pro x64 and the server was set to update automatically the last time I was allowed to see the settings.
What I am seeing
EVERY time I click on the bookmark for my Plex (http://127.0.0.1:32400/web/index.html) I am presented my user list. I choose myself (the admin) and enter my PIN. The first time I do this after starting the browser I get a “no soup for you” page and my server IS NOT EVEN LISTED in the server options! If I refresh the page and log in again, I get to me home screen OK. I can play anything shown on the home screen, too. However, clicking on a library just flashes the content and re-displays the home screen. Clicking on settings brings back the “no soup for you” page and my server has been removed from the list!
I noticed the initial log in problem a few days ago, but today the settings issue started. Not sure what is going on with the Plex web app, but it is not good.
Oh, I have no problems using my Plex server from any of my Roku or FireTV apps. I don’t have any others to test, or I would check them for more info, too.
’
Hmmm… I just tried going indirect, through https://plex.tv and that WORKS. But I it isn’t working correctly when connected directly to the plex in the same computer. Could it be a new http vs https issue? Or does Plex just want to monitor everything I do more proactively?
I think that’s where I ended up by starting at plex.tv, isn’t it?
Anyway, the point is that when I right-click the plex icon and choose ‘Open Plex’ I should be able to manage my server from whatever open, should I not?
I would not use the word “resolved” since the problem was only hidden/worked-around. If this is another feature that Plex is removing, while I would rather not lose it (connecting locally “feels” much faster) I believe that Plex should display something more helpful than “no soup for you.”
But truly, I hope they actually fix the problem rather than just eliminate another feature.
Typically Chrome. When I saw your question, I tried Firefox and the initial login was … different. Instead of being asked to choose a user and then enter the PIN for my admin account, I was taken directly to the server I manage for my parents (600 miles away) instead of the local machine whose address I used (4 feet away – I’m not physically at the Plex server right now). However, after I manually re-selected the machine I initially connected to, I was able to use the setup screen and at no time saw a “no soup for you” message.
So for me the problem has been narrowed down to the Plex web app in Chrome when connected directly to the PMS instead of going through app.plex.tv
Before I answer, please remember that I was able to log in and use the settings just two days ago from four different computers using Chrome (the Plex machine itself, my home desktop and two desktop at my office.) Today it simply no longer worked and just gave me the “no soup for you page” AND removed my Plex server from the list of servers. I don’t mean it marked it inaccessible – it was COMPLETELY REMOVED FROM THE LIST (though a complete page refresh, which required a new login that fails about 50% of the time with “no soup for you”)
Non-default browser preferences? Of course, but I no longer have any idea what I have changed in the days since Chrome was first released and/or what default are or have become over the years.
Chrome extensions? Yes, though I think many came with Chrome because I didn’t ask for all of these: Adblock Plus, Adobe Acrobat, Download Vimeo Videos Premium, Force Background Tab, Google Docs Offline, Honey, InvisibleHand, LinkedIn Sales Navigator, Morning Espresso, Tab Position Customizer, Tamper Monkey, WOT, Chrome Remote Desktop, Docs, Games of Life, Link All, Plex NAS Launcher, Sheets, Slides.
And Chrome is synchronized across my computers, so the Plex server computer has the same set.
I hope Google Docs offline included docs, sheets and slides, because I am certain I never installed those. Everything else, I remember.
Tampermonkey was disabled, so I removed it. Adblock was enabled for plex.tv (but not enabled for my local plex server) so I disabled it and restarted the browser. I still get “no soup for you” when I first connect (after entering my PIN, which for some reason Firefox didn’t need.)
This time it took four page reloads before I got beyond the “no soup for you” but, once again when I tried “Settings” my server was totally removed from the known server list and I got “no soup for you” again.
I know you are trying to help, but a customer really should not need to jump through all these hoops just to have a purchased product work the same way today that it worked yesterday. Just sayin’.
I performed your test, but with one slight change: After “Save Changes” I exited from Chrome and then restarted it from scratch to ensure a “total” reset.
It connected right up, directly to my local Plex server, and I am able to view the settings. For the moment at least, “no soup for you” appears to be a thing of the past. Of course, there’s a new update available, so who knows what will change next!
Thanks for your patience and persistence!
PS: Good thing I tried your suggested test BEFORE getting the update because there is no longer a “Turn off Settings Sync” option on the Web Client|General|Advanced page! However, there are now four Web Client panels/pages where there were only three offered when I performed the test. So… Did the update to PMS 1.15.1.710 change this or did following the suggested steps cause the changes I am seeing? Very curious.
and its back. It worked for about a week, but this morning I am back to exactly where this thread started, but with version 1.15.1.710 of the server.
Probably unrelated, but over the past weekend, my Plex server mysteriously quit and after one Windows update, failed to start. However, once noticed I was able to start it manually with no noticeable problems. I made a quick brose through the plex logs (and the Windows Event logs) to see if I could find any hints about why Plex stopped, but I saw nothing about Plex exiting. Strange and unsettling.
Otto, I know you are trying to help and you are probably not the single person responsible for the local/hosts app, so most of this is not for you – it is for any actual Plex workers who might be willing to divulge the secrets necessary actually explain WHY I (and others) am seeing this mercurially good/bad/good behavior from the local app.
That said, the linked article actually makes what I’ve seen even more confusing…
The Plex Media Server version HAS NOT CHANGED yet, when the version was first updated to the current value, the local app worked great. Then, for a while today it didn’t work at all (just like my original post) When I came home after work, the local app is working again and the PMS version STILL HAS NOT CHANGED.
So… What DID change?
The linked page says that the local app does not require and internet connection, ergo it must not be using anything that it does not already have locally. Or the linked page is wrong and an internet connection is ALWAYS required and some components of the app are ALWAYS retrieved from the internet – this is what I believe to be true. Otherwise, how is the local app suddenly failing and then magically repairing itself without ever accessing the internet or updating the PMS? There is something going on here with the local app that has not been revealed because unless something was updated yesterday to break the local app and again today to fix it, the only thing I can see that remains is divine intervention.
Finally, it seems it would almost always be better to use the LOCAL app FIRST because it is a tried and true version, rather than a bleeding edge version that may not work as one expects and may even have issues with the particular version of PMS locally installed. I write software for industry, power plants, etc. and we would NEVER recommend that the day-to-day operation of anything use the most up-to-date version of anything because the most up-to-date version of anything is 99% certain to need more testing than it has received to find the bugs. Just ask Microsoft about their last six months of Windows 10 updates.
Very similar problem, here. I run the Plex server on my Mac, and I use the Chrome browser to cast music to a Chromecast device. This has been working fine for months. Yesterday, it started doing what you described: It only shows me the home screen, no matter what I do. Can’t use any playlist, or album, nothing.
After reading the posts here, I changed my URL from http://127.0.0.1:32400/web/index.html to https://127.0.0.1:32400/web/index.html. That worked!
Still having the issue with “no soup for you” when I try to manage my Plex Media Server on Windows 10 by right-clicking on the Plex icon in the system tray and choosing “Open Plex”!
Sorry but it is simply UNACCEPTABLE that I cannot manage my local plex, directly on the plex computer by using a menu FROM PLEX ITSELF ! What kind of program cannot even open its own interface locally? If I want to run a Plex server that has no internet access, just for use in my own home, is there ANY valid reason why I should not be able to manage it?
Any crap about using the “more reliable app.plex.tv” method is just that. Crap. If the product was not delivered with a functional interface, then the product is BROKEN and the interface should be fixed. Period.
I wonder if the Plex folks are even bothering to look into this – after all it will take valuable time away from removing useful features like channels in favor of adding more subscription junk instead of building better support for maintaining and managing our personal libraries, which is why most of us paid for plex in the first place.
Sorry, I’m a bit frustrated after so many weeks of the same annoying issue with no progress except for lame “work-arounds.”
