Not Authorized

Plex Media Server Desktops & Laptops
1

I’ve had Plex installed on my desktop computer for 6 years no problem. I have one user account. I only access from my own desktop computer and a few TV’s in the house. Today I got a stuck loading screen on the Home page, and my Movies/TV libraries say “Not authorized. You do not have access to this server".

I tried restarting the server a few times.
I tried logging out and back in to my user account.
I tried restarting my (Windows) computer.

Unfortunately those were all unsuccessful.

I followed the steps in this article and deleted the specified registry keys in Windows: https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/
Then I clicked the “Open Plex…” option from the System Tray, but unfortunately all it does is keep reloading the “Getting ready…” screen.

I found this topic about a new requirement to “claim your server”: New Claiming Requirement for Windows
I tried opening the “Setup Plex.html” file, but all that does is create another looping screen with.

I’m not sure what to do and any help is appreciated.

Here is an excerpt from the log file when it’s doing some of the looping:

Oct 03, 2024 23:32:07.333 [11284] DEBUG - Request: [127.0.0.1:51458 (Loopback)] GET /myplex/launch (2 live) #120 GZIP Token ()
Oct 03, 2024 23:32:07.334 [2376] DEBUG - [Req#120/HCl#d0] HTTP requesting POST https://plex.tv/api/v2/pins?strong=true
Oct 03, 2024 23:32:07.335 [13788] DEBUG - Completed: [127.0.0.1:51458] 200 GET /myplex/launch (2 live) #120 GZIP 2ms 3488 bytes (pipelined: 13)
Oct 03, 2024 23:32:07.551 [12076] WARN - [HttpClient/HCl#d0] HTTP error requesting POST https://plex.tv/api/v2/pins?strong=true (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name 'plex.tv')
Oct 03, 2024 23:32:07.551 [2376] ERROR - [Req#120] MyPlex: Failed to retrieve PIN: -60
Oct 03, 2024 23:32:08.458 [11284] DEBUG - Request: [127.0.0.1:51458 (Loopback)] GET /myplex/launch (2 live) #121 GZIP Token ()
Oct 03, 2024 23:32:08.458 [6120] DEBUG - [Req#121/HCl#d1] HTTP requesting POST https://plex.tv/api/v2/pins?strong=true
Oct 03, 2024 23:32:08.459 [8516] DEBUG - Completed: [127.0.0.1:51458] 200 GET /myplex/launch (2 live) #121 GZIP 1ms 3488 bytes (pipelined: 14)
Oct 03, 2024 23:32:08.711 [12076] WARN - [HttpClient/HCl#d1] HTTP error requesting POST https://plex.tv/api/v2/pins?strong=true (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name 'plex.tv')
Oct 03, 2024 23:32:08.711 [6120] ERROR - [Req#121] MyPlex: Failed to retrieve PIN: -60

And

ct 03, 2024 23:25:03.187 [2376] ERROR - [Req#be] MyPlex: Failed to retrieve PIN: -60
Oct 03, 2024 23:25:04.115 [11284] DEBUG - Request: [127.0.0.1:51347 (Loopback)] GET /myplex/launch (2 live) #bf GZIP Token ()
Oct 03, 2024 23:25:04.116 [6120] DEBUG - [Req#bf/HCl#73] HTTP requesting POST https://plex.tv/api/v2/pins?strong=true
Oct 03, 2024 23:25:04.117 [13788] DEBUG - Completed: [127.0.0.1:51347] 200 GET /myplex/launch (2 live) #bf GZIP 1ms 3488 bytes (pipelined: 5)
Oct 03, 2024 23:25:04.330 [12076] WARN - [HttpClient/HCl#73] HTTP error requesting POST https://plex.tv/api/v2/pins?strong=true (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name 'plex.tv')
Oct 03, 2024 23:25:04.330 [6120] ERROR - [Req#bf] MyPlex: Failed to retrieve PIN: -60
Oct 03, 2024 23:25:05.257 [11284] DEBUG - Request: [127.0.0.1:51347 (Loopback)] GET /myplex/launch (2 live) #c0 GZIP Token ()
Oct 03, 2024 23:25:05.257 [10080] DEBUG - [Req#c0/HCl#74] HTTP requesting POST https://plex.tv/api/v2/pins?strong=true
Oct 03, 2024 23:25:05.259 [8516] DEBUG - Completed: [127.0.0.1:51347] 200 GET /myplex/launch (2 live) #c0 GZIP 2ms 3488 bytes (pipelined: 6)
Oct 03, 2024 23:25:05.469 [12076] WARN - [HttpClient/HCl#74] HTTP error requesting POST https://plex.tv/api/v2/pins?strong=true (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name 'plex.tv')
Oct 03, 2024 23:25:05.469 [10080] ERROR - [Req#c0] MyPlex: Failed to retrieve PIN: -60
Oct 03, 2024 23:25:06.418 [11284] DEBUG - Request: [127.0.0.1:51347 (Loopback)] GET /myplex/launch (2 live) #c1 GZIP Token ()
Oct 03, 2024 23:25:06.418 [6120] DEBUG - [Req#c1/HCl#75] HTTP requesting POST https://plex.tv/api/v2/pins?strong=true
Oct 03, 2024 23:25:06.419 [13788] DEBUG - Completed: [127.0.0.1:51347] 200 GET /myplex/launch (2 live) #c1 GZIP 1ms 3488 bytes (pipelined: 7)
Oct 03, 2024 23:25:06.643 [12076] WARN - [HttpClient/HCl#75] HTTP error requesting POST https://plex.tv/api/v2/pins?strong=true (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name 'plex.tv')
2

I got this resolved.

This comment helped a lot: Plex wont start normally after a clean reinstall and is stuck on getting ready - #15 by arythion

I manually set the DNS servers for my IPV4 adapter in Windows to 1.1.1.1 and 8.8.8.8 and then I opened the Setup Plex.html file again. It got hung up after a while, but when I reloaded the page I could see everything again. Not sure what was going on there.

3

From the log files you posted above, most likely something got in-between the Plex client and plex.tv and decrypted the data packets.
Since Plex clients detect that, they refuse to use such data packets, because they could have been manipulated.
Most likely, there is a firewall which is decrypting all data and inspecting it. Then it’s encrypting them again (using a different certificate) and sending them to your home network. That is what is detected in those logs above.

By changing the DNS server, you somehow got around this snivelling firewall.
If you were located in a corporate network, I would expect something like this. But if this is a private home network connection, it poses serious questions about the ethics of your ISP.

1 Like
4

Hmm that’s really interesting Otto, thanks for the response and info. It’s a private home network and it makes me curious what’s going on there.

5

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