Is this a bug? I realize there are way more important things that Plex does well, and reliably (including saving the “Automatically sign in” setting on two other iPads and an iPhone). But is this happening to anyone else? Plex Media Server v1.5.0.3501 is running on a Western Digital PR2100. I’m opening the app in Chrome on a Mac, and if I chec, there are definitely “local storage” cookies stored in Chrome for both the https://app.plex.tv and the http://192.168.100.11:32400 route to the player. I don’t get it.
@piantadosi said:
there are definitely “local storage” cookies stored in Chrome for both the https://app.plex.tv and the http://192.168.100.11:32400 route to the player. I don’t get it.
I’d add webloader.plex.tv as well as plex.tv into the list of cookies to be retained inbetween browser sessions.
But Chrome is not set to screen cookies, or delete any between sessions — so it should be accepting all cookies, even third-party. That’s why this is so confusing.
There is also 3rd party software wich erases cookies and other data.
Do you use anything like that?
Or maybe this functionality is integrated in your anti virus S/W?
No, none of that is active on this machine. Again, doesn’t happen on the device apps (iPads, iPhone), just Plex Web App.
Have you tested with Safari?
Is Chrome connected to a Google account, so its settings are saved and replicated across several devices? If so, could it be that the ‘backup’ portion of that task is not working, so that the settings are always overwritten?
Are you using any Web browser add-ons, like Adblock or Privacy[anything] etc ?
It’s happening with every browser I have tried — Chrome, Firefox and Safari. I checked the sync options between Chrome browsers on my laptop, which I use for Plex, and another Mac, which is used primarily for work. Chrome on both machines is set to sync apps, settings and extensions — no open tabs, bookmarks, autofill, passwords.
In the process I discovered it’s also happening on Chrome on that second Mac — the signed-in User is not retained between sessions. I don’t see how this can be a client issue; it has to be the server, right?
Normally not, because the login token is stored in the browser, not on the server.
Whatever happens, it must have to do with the login token getting removed or invalidated.
Which gives me an idea: is the clock setting correct on your NAS?
(check the `Plex Media server.log if it contains sensible time stamps)
If it has a NTP client, turn it on.
Thanks for taking the time to help, Otto. Unfortunately, no, the server time was correct and the NAS is connected to NTP. So I turned off all Chrome sync choices (and then just upgraded to the 1.5.1 release), and so far, so good. Not sure what fixed it, but I will keep my fingers crossed.
