Yes. I did not wake it on May 7, so that fits how long it has been asleep
I have noticed similar happening over the last few months and every time it happens, the PlexOnlineToken
is empty in the Preferences.xml
. I donāt have the exact logs for when it happens since it seems to happen only when idle and by the time (2-3 days) I notice it, the logs have already been rotated.
Interesting find. Thank you for sharing. I will try and check this value on mine when it happens again.
@exuberantShadow It happened to me again today. I am running Windows, so instead of Preferences.xml, I checked my registry, and the PlexOnlineToken was NOT empty.
There are actually 2 types of unauthorized servers that I have seen:
-
The first one is simply an invalid token and a service restart fixes it.
-
The second one is an empty token which requires me to claim the server again to get it working.
Most of my unauthorized servers have been of the second variety with the first one occurring only once so far.
I donāt mean to hijack the thread but Iām having the āNot authorized You do not have access to the server,ā as well. I deleted the the 4 categories in the registry, uninstalled and reinstalled plex server, deleted the entire plex registry in two sections, deleted temp files, deleted local appdata too. I must of uninstalled and reinstalled about 15 times. I had a computer issue and reinstalled windows 10 and thats when the problem started. Iām using Windows 10 for now (waiting for 11, probably tomorrow) windows 10.0. build 19045. Plex server 1.32.2.7100-248a2daf0. Any help would be appreciated.
P.s. My computer is set to never sleep.
My logs are added below. Windows 11 is updating now but my server version is
1.32.2.7100-248a2daf0
There is a discrepancy in my ip address on subnet. I changed it back to the pre-crash ip. I thought I would check to see if that fixed the issue. So when you see the ip change from xxx.xxx.xxx.6 to xxx.xxx.xxx.x66 that was planned.
Thank you
EDIT: Updating to Windows 11 fixed the issue.
This seems to be related:
Jun 03, 2023 10:30:49.769 [0x7fb2bb730b38] DEBUG - [ViewStateSync] Starting Jun 03, 2023 10:30:49.769 [0x7fb2bb730b38] DEBUG - [ViewStateSync] Fetching user tokens
Jun 03, 2023 10:30:49.769 [0x7fb2bb730b38] DEBUG - [ViewStateSync/HCl#17f1] HTTP requesting GET https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
Jun 03, 2023 10:30:50.217 [0x7fb2da157b38] DEBUG - [HttpClient/HCl#17f1] HTTP/2.0 (0.4s) 401 response from GET https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
Jun 03, 2023 10:30:50.217 [0x7fb2bc501b38] ERROR - [ViewStateSync] MyPlex: Error 401 requesting XML from: https://plex.tv/api/v2/server/users/services?auth_token=xxxx
xxxxxxxxxxxxxxxx
Jun 03, 2023 10:30:50.217 [0x7fb2bc501b38] WARN - [ViewStateSync] MyPlex: Token was invalid, resetting security.
Jun 03, 2023 10:30:50.217 [0x7fb2bc501b38] DEBUG - [ViewStateSync] MyPlex: Got a token poked, let's act on it.
Jun 03, 2023 10:30:50.217 [0x7fb2da9c7b38] DEBUG - [EventSourceClient/pubsub/184.105.148.115:443] Stopping.
Jun 03, 2023 10:30:50.217 [0x7fb2bc501b38] DEBUG - [ViewStateSync/HCl#17f3] HTTP requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=
Jun 03, 2023 10:30:50.217 [0x7fb2da9c7b38] DEBUG - [EventSourceClient/pubsub/184.105.148.115:443] Failure: 125 - Operation canceled.
Jun 03, 2023 10:30:50.366 [0x7fb2da157b38] DEBUG - [HttpClient/HCl#17f3] HTTP/2.0 (0.1s) 200 response from GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxx
xxx
Jun 03, 2023 10:30:50.366 [0x7fb2bc501b38] DEBUG - [ViewStateSync/HCl#17f4] HTTP requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=
Jun 03, 2023 10:30:50.521 [0x7fb2da157b38] DEBUG - [HttpClient/HCl#17f4] HTTP/2.0 (0.2s) 200 response from GET https://plex.tv/api/v2/release_channels?X-Plex-Token=xx
xxxxxxx
Jun 03, 2023 10:30:50.522 [0x7fb2bc501b38] DEBUG - [ViewStateSync/HCl#17f5] HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=
Jun 03, 2023 10:30:50.671 [0x7fb2da157b38] DEBUG - [HttpClient/HCl#17f5] HTTP/2.0 (0.1s) 200 response from GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxx
Jun 03, 2023 10:30:50.672 [0x7fb2bc501b38] DEBUG - [ViewStateSync] No user tokens found; stopping
Jun 03, 2023 10:30:50.733 [0x7fb2cfe78b38] WARN - [ViewStateSync/MediaProviderManager] Unrecognized MediaProvider feature: availability
Jun 03, 2023 10:30:50.733 [0x7fb2cfe78b38] WARN - [ViewStateSync/MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Jun 03, 2023 10:30:50.733 [0x7fb2cfe78b38] DEBUG - [ViewStateSync/MediaProviderManager] we had 1 cloud providers online, we now have 1
Jun 03, 2023 10:30:50.733 [0x7fb2cfe78b38] DEBUG - [ViewStateSync/MediaProviderManager] cloud provider (Metadata) is online and available
Jun 03, 2023 10:30:49.769 [0x7fb2bb730b38] DEBUG - [ViewStateSync] Starting Jun 03, 2023 10:30:49.769 [0x7fb2bb730b38] DEBUG - [ViewStateSync] Fetching user tokens
Jun 03, 2023 10:30:49.769 [0x7fb2bb730b38] DEBUG - [ViewStateSync/HCl#17f1] HTTP requesting GET https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxx
xxxxxx
Jun 03, 2023 10:30:50.217 [0x7fb2da157b38] DEBUG - [HttpClient/HCl#17f1] HTTP/2.0 (0.4s) 401 response from GET https://plex.tv/api/v2/server/users/services?auth_token
=xxxxxxxxxxxxxxxxxxxx
Jun 03, 2023 10:30:50.217 [0x7fb2bc501b38] ERROR - [ViewStateSync] MyPlex: Error 401 requesting XML from: https://plex.tv/api/v2/server/users/services?auth_token=xxxx
xxxxxxxxxxxxxxxx
Jun 03, 2023 10:30:50.217 [0x7fb2bc501b38] WARN - [ViewStateSync] MyPlex: Token was invalid, resetting security.
Jun 03, 2023 10:30:50.217 [0x7fb2bc501b38] DEBUG - [ViewStateSync] MyPlex: Got a token poked, let's act on it.
Jun 03, 2023 10:30:50.217 [0x7fb2da9c7b38] DEBUG - [EventSourceClient/pubsub/184.105.148.115:443] Stopping.
Jun 03, 2023 10:30:50.217 [0x7fb2bc501b38] DEBUG - [ViewStateSync/HCl#17f3] HTTP requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=
Jun 03, 2023 10:30:50.217 [0x7fb2da9c7b38] DEBUG - [EventSourceClient/pubsub/184.105.148.115:443] Failure: 125 - Operation canceled.
Jun 03, 2023 10:30:50.366 [0x7fb2da157b38] DEBUG - [HttpClient/HCl#17f3] HTTP/2.0 (0.1s) 200 response from GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxx
xxx
Jun 03, 2023 10:30:50.366 [0x7fb2bc501b38] DEBUG - [ViewStateSync/HCl#17f4] HTTP requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=
Jun 03, 2023 10:30:50.521 [0x7fb2da157b38] DEBUG - [HttpClient/HCl#17f4] HTTP/2.0 (0.2s) 200 response from GET https://plex.tv/api/v2/release_channels?X-Plex-Token=xx
xxxxxxx
Jun 03, 2023 10:30:50.522 [0x7fb2bc501b38] DEBUG - [ViewStateSync/HCl#17f5] HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=
Jun 03, 2023 10:30:50.671 [0x7fb2da157b38] DEBUG - [HttpClient/HCl#17f5] HTTP/2.0 (0.1s) 200 response from GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxx Jun 03, 2023 10:30:50.672 [0x7fb2bc501b38] DEBUG - [ViewStateSync] No user tokens found; stopping
Jun 03, 2023 10:30:50.733 [0x7fb2cfe78b38] WARN - [ViewStateSync/MediaProviderManager] Unrecognized MediaProvider feature: availability Jun 03, 2023 10:30:50.733 [0x7fb2cfe78b38] WARN - [ViewStateSync/MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Jun 03, 2023 10:30:50.733 [0x7fb2cfe78b38] DEBUG - [ViewStateSync/MediaProviderManager] we had 1 cloud providers online, we now have 1 Jun 03, 2023 10:30:50.733 [0x7fb2cfe78b38] DEBUG - [ViewStateSync/MediaProviderManager] cloud provider (Metadata) is online and available
Perhaps the ViewStateSync process doesnāt handle token renewal?
@exuberantShadow I do not have the same errors in my system logs, that I can see. It appears I am not using a token???
May 18, 2023 16:58:28.844 [7840] DEBUG - [ViewStateSync] Starting
May 18, 2023 16:58:28.844 [7840] DEBUG - [ViewStateSync] Fetching user tokens
May 18, 2023 16:58:28.845 [7840] DEBUG - [ViewStateSync/HCl#3b] HTTP requesting GET https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
May 18, 2023 16:58:29.269 [10708] DEBUG - [ViewStateSync] No user tokens found; stopping
May 18, 2023 17:28:28.858 [2684] DEBUG - [ViewStateSync] Starting
May 18, 2023 17:28:28.858 [2684] DEBUG - [ViewStateSync] No user tokens found; stopping
May 18, 2023 17:58:28.864 [12956] DEBUG - [ViewStateSync] Starting
May 18, 2023 17:58:28.864 [12956] DEBUG - [ViewStateSync] Fetching user tokens
May 18, 2023 17:58:28.865 [12956] DEBUG - [ViewStateSync/HCl#bb] HTTP requesting GET https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
May 18, 2023 17:58:29.315 [15068] DEBUG - [ViewStateSync] No user tokens found; stopping
May 18, 2023 18:28:28.870 [1920] DEBUG - [ViewStateSync] Starting
May 18, 2023 18:28:28.870 [1920] DEBUG - [ViewStateSync] No user tokens found; stopping
May 18, 2023 18:58:28.880 [9824] DEBUG - [ViewStateSync] Starting
May 18, 2023 18:58:28.880 [9824] DEBUG - [ViewStateSync] Fetching user tokens
May 18, 2023 18:58:28.881 [9824] DEBUG - [ViewStateSync/HCl#143] HTTP requesting GET https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
May 18, 2023 18:58:29.342 [1276] DEBUG - [ViewStateSync] No user tokens found; stopping
May 19, 2023 11:02:33.746 [14628] DEBUG - [ViewStateSync] Starting
May 19, 2023 11:02:33.916 [14628] DEBUG - [ViewStateSync] Fetching user tokens
May 19, 2023 11:02:33.916 [14628] DEBUG - [ViewStateSync/HCl#16d] HTTP requesting GET https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
May 19, 2023 11:02:34.002 [2412] DEBUG - [ViewStateSync] MyPlex: using cached data for request for https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
May 19, 2023 11:02:34.003 [2412] DEBUG - [ViewStateSync] No user tokens found; stopping
May 19, 2023 11:32:35.159 [7068] DEBUG - [ViewStateSync] Starting
May 19, 2023 11:32:35.159 [7068] DEBUG - [ViewStateSync] No user tokens found; stopping
@stacula Thanks for the additional info. Are you saying your issue was resolved by updating from Windows 10->11? I have been considering that, but hoping with all this data, we could help Plex figure out the issue
@anon18523487 seeing anything noteworthy in all these logs?
Is there anything crazy we could do to figure this out? I would be happy to run like a custom build or something to try and debug. I do sw dev, so I am willing to help out. Thanks
Edit: When this happens, I have to quit the media server application, restart, and grab the logs. Seems like it would be useful if there was something I could do WHILE being locked out to try and identify what is happening.
This was only for the token being empty and thus requires a reclaim to fix. I still havenāt found anything in the logs when the token is invalid and just a restart fixes it.
Initially, I thought that was the fix, but after further testing, it seems thatās not the case, and it was just a coincidence. I like to keep my OS running pretty smoothly and hate bugs, malware and the such. After, reinstalling the OS again (maybe around 5 times in 2 weeks), I keep getting the plex ?bug? each time. Upgrading Win 10 to Win 11 only worked the single time. There is at least another thread about the issue in the forums:
The above thread shows an issue which I could reproduce. The three results I receive when opening PMS are either 1) not authorized 2) a spinning circle with text āInitializing serverā -which never stops until I refresh the page or 3) it opens Plex, I click my media + sign and it gives me a link to download PMS. The last one is when I open plex via the app.plex.tv
Iāve erased the PLEX registry either narrowly and completely. On the thread, there is discussion about running in administrative mode and an issue with revocation of server for certificate but I think thatās only a coincidence too because I get the same response from opening other apps in administrative mode.
If I figure anything out, I will update this thread. Iāve attempted to read the logs, I took mine down when I thought the problem was fixed due to computer info being in the logs.
Also, Iāve had the issue regardless if the registry had a token missing or not. It seems that youāve been able to at least reclaim the server which we have not.
@theguitarman I figured out a workaround, Iām including the it in a link. Itās only an abbreviated version but wrote more than expected and you should be able to parse it. I have to run but any questions you have I will answer.
@anon18523487 Any updates on this? Seems like there must be something I can do on my computer to determine why I donāt have access? Maybe a command line way to check the token?
I do not have an update. I have an issue filed internally with our devs to take a look.
@anon18523487 Is there a way to talk with the devs? There must be something I can do with this computer that has the issue to help them identify the root cause
If you have anything you want to share, just post it here and I will pass it along. I have an issue filed for them to review. If they need anything, Iāll let you know.
For the server with the token being empty, upon further investigation, it looks like thereās a duplicate server instance with the same name that shows as offline.
If I remove delete only that offline server, it seems to cause the empty tokens on the remaining online servers too.
I used to delete it previously without correlating with the server becoming unauthorized but now that I left the offline server as-is for a few weeks, the remaining servers have remained authorized without any issues. Another weird point is that the seemingly offline server always shows up with a different name (from one of the other online servers) after every attempt at removal and reauthorizing the online servers.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.