Fresh windows 10 install
Fresh Plex server install.
If windows is restarted plex functions perfectly
If windows sleeps and is resuned from sleep, plex shows as running in the system tray, but the web ui shows "not authorised when attempting to view a library.
Exiting the plex server and relaunching it fixes the issue.
Found this reddit thread and have tried the hack around fixes of scripts and scheduled tasks without success. (6) Plex Media server not authorized after wake from sleep : PleX (reddit.com)
Oh, I lost track of that thread. Can you get me both the server logs and client logs after waking your server up from sleep? Let me know what time you are waking it up?
I’m seeing this same thing on a Windows 11 22H2. It used to work for a bit after initial Plex installation but now does exactly what the author describes. I’m attaching my server logs. I’m not sure where to get the client logs but I saw it from the plex web page and on my Roku that all my libraries were unavailable after the system woke up. I woke the system up at 6:42pm on 12/4/2022. I appreciate you looking at this. It is very annoying to have to RDP in when it used to work right after waking up. I’d just prefer to not pay for the power usage when I typically only use the Plex server in the evenings. Plex Media Server Logs_2022-12-04_19-32-17.zip (1.1 MB)
I am having this issue as well. Logged in and it says I am no authorized. Was logged in last week with no issues. I followed all the steps to reset this on my mac from the plex.support page and still nothing. I am a life time member this has never happened to me before until the data breach. Help me Plex support you’re my only hope
I have having the exact same issue. Whenever the computer awakes from sleep no app can connect, including opening on the server itself. Returns not authorized. Have to restart the server to get it to work.
I have had the same problem for a few months now. For the last few years I’ve operated my server by hibernating instead of shutdown. This allows me to waken the server remotely. This always worked perfectly until sometime in autumn 2022. Now after waking the server I get the “not authorised” message when trying access my library. To get access I either have to reboot the server or log out and log in again. This requires going to the server which is two floors up. I’ve tried the registry edit suggested by plex support followed by reclaiming the server but that fix was short-lived.
Where do these logs save to? I’m the original author of the Reddit thread linked in the main post, I’m still having this issue persistently, regardless of how many updates that have been pushed.
While the issue is persistent, I must stress it’s not consistent. It’s like one in every ten instances of me waking the PC up that hosts my media server can I not connect to it.
I am able to verify that it affects connections across the board - if it decides to have its moment, no app, not even opening the IP locally in the browser on the same machine, can connect to the server until I just exit the media server application and re-open it again.
I’ll get logs next time it happens if you detail what you need and where I get it from!
In your server settings, enabled “verbose logging”. Next time your server is inaccessible, restart PMS, then grab the logs following this guide → server logs.
Just to chime in I’ve just recently started having this happen also maybe 2 weeks ago and has happened about 4 times. Will take logs next time it occurs to @r_chsr point it’s been inconsistent but definitely not a 1 in 10 type bug seems about 5 in 10 or so. Restart of OS for me fixes the problem until next occurrence. I don’t usually put my system to sleep so not a hibernation thing for me.
So I did send in logs just now but I think I can recreate the scenario. If you have multiple user accounts it seems logging into a secondary account and returning will result in the error. I suppose thats the reason (for me) it was a little unpredictable; my wife only uses my office computer about once a week. Not a fix but I’m going to have her just use my account for now.
Edit: Also looks like I did have Plex starting up on her account for some reason; leaning towards that; disabled that on startup on her account and about to test again.
Edit 2: So this seems to have fixed my issue. I’m assuming that when her non-setup account was started I was pointing to the default local ip which wouldn’t work because was not logged into her instance. At least on mine when I restart my computer my account is on autologin which means her instance wouldn’t have started therefore restoring my access to the shared local ip. (This is just my wild guess but things are working now and she can login to her windows account and not cause issues).
Any status update from others? I’m not using multiple Plex nor Windows accounts, so the previous post doesn’t seem to apply.
I recently discovered that my neighbor also uses Plex for his local media library, and to my surprise he said he has the same issue with server over the past year. Why is this going unaddressed for so long?
I have often the same issue when I wake up my Windows 11 PC. I generally have the client open when PC goes to sleep (client on the same machine as server). Happens when PC has been to sleep for while not exactly sure. I have to restart both client and server.
Just confirming that I too have this exact same problem.
After waking my computer up from hibernate either remotely or in person I often, but not every time? get this Not Authorized message when trying to access Plex. Shutting down plex on the host computer and re-starting it fixes the issue and all is back to normal. I say it happens about 1 out of every 3 or 4 times, so no every time. Very annoying however! I’ve had this for at least a year now and finally decided to look it up and glad to see I’m not the only one… Please fix
I am â– â– â– â– â– â– â– sick of this fking error! Every time I go to use my Plex I have to run through the bullshit fix of deleting registry entries and claiming my own fking server! When the fk are you going to fking going to fix this!
