"Your credentials have expired. Please sign in again." happens on every refresh of my plex server

This has been increasing in frequency to the point now where I can no longer play anything in my library because it wants my credentials on every refresh of the page. There is nothing different or wrong in my browser settings. Please help.

UPDATE

This is only apparently happening on the https://app.plex.tv/desktop#! url and not the http://127.0.0.1:32400/web/index.html#! local one.

Use a regular web browser, (i.e. avoid web browsers which impede the function of web apps by applying filters and interfere with their communication)
Disable web browser add-ins.
Tell the web browser to not throw away cookies from the domain plex.tv
Tell the same to some 3rd-party tools which you might have installed, like “CCleaner” and similar.

Chrome, no plugins, browser has normal settings for cookies, no 3rd party tools.

Something must be interfering, thus making the login session invalid all the time.
The above listed are the most common culprits.

Are you using some 3rd party anti-virus software?
Any internet filters?
VPNs?

Windows defender is all, no internet filters, no VPNs.

This all used to work fine, I’ve made no changes at all to any of my systems other than windows updates, chrome updates and plex updates.

Try to use an “incognito” browser tab.
If this behaves differently, try blowing away your browser cache.

Are you using an email address + password to log into your Plex account or are you using one of the other login options (Facebook, Google, Apple)?

I second Otto, sounds like a potential cache issue on the browser.

Something I’ve noticed is that it was somehow forcing an insecure connection - adding https:// was jumping back over to the insecure version. This was happening even in incognito mode. However starting fresh on the secure version from the start doesn’t cause the credential loop.

So something about a tab first visiting the insecure version is poisoning it and forcing it back to the insecure http version and that version goes into the credential loop.

So, I guess this solves my problem. Just avoid the insecure url. But it isn’t like I wanted to go to the insecure version. No idea why or how it got there. But as long as I start fresh it is fine.

/shrug

1 Like

This is the fix, I also had to add secure=1#! to the URL string as it was defaulting to secure=0 so there is a bug somewhere.

Here is something to be aware of:
if you have the web app running, and there is a connection issue occuring (either the network connection to the server is going down or the server itself), then the web app will offer you to revert to an unsecure connection.

If the server going down was expected, don’t click on that button! Because it will “stick” and the web app will always try an unsecure connection from then on – until you tell it explicitly to go “secure” again with the above mentioned URL change.

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