Plex Home Admin account lost access to local server

Plex Media Server
1

Plex Server Version#: 1.26.2.5797-5bd057d2b May 10, 2022
Plex Web Version#: 4.76.1
Unraid Server Version#: Version 6.9.2 2021-04-07
Plex Server has been Running in Unraid Docker for several years with no issues.
Repository plexinc/pms-docker (Last Update:|May 16, 2022)

THE PROBLEM: Home Admin account (using the registered plex user email used to purchase the Plex Pass) does not see local plex server nor its media files (movies, music, photos, etc). Login to plex.tv works no issue.

Other user accounts DO see the local plex server AND all the media files.

PlexAmp from Android Phone (uses the same plex pass user account), DOES see the server and all its media files, even works remotely outside of the local network.

Login to Plex WebUI, then settings for the Home Admin. I do not see the SERVER section in Plex Web (Settings>Plex Web).

What setting could affect the Home User Account like this?

Thanks in advance!

Server Log shows Starting Plex Server appears ok (not sure what libusb_init failed, something to do with DVR? (Server Logs attached)

<[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 40-plex-first-run: executing…
[cont-init.d] 40-plex-first-run: exited 0.
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing…
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0.
[cont-init.d] 50-plex-update: executing…
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.
Critical: libusb_init failed>

Circumstance - Server locked up (no idea why) after running for months. Restarted server, no issues. Server appears to have started normally (Server Log shows: May 20 19:26:08 HunterNAS rc.docker: PlexMediaServer: started succesfully!)
Plex Docker running as usual and accessible from normal WebUI from Dashboard

2

No Server logs attached?

3

Yep, I can’t access them anymore! The Home Admin, for some reason, has no access to the server files. Attached is what I see from the Home Admin settings. I don’t have Settings > Manage > Troubleshooting menus any more… Feels like a security issue, but I’ve not changed passwords anywhere for a very long time…

msedge_2022-05-29_11-04-14
msedge_2022-05-29_11-04-14650×769 56.2 KB

4

The avatar in the browser does not match your avatar?

Are you sure you in the browser are logged in with the correct credentials?

5

That’s a fascinating question dane22. The top avatar (my face) is my business gmail account logged in. I’ve always used that account in the browser. The avatar in my plex account is what I loaded up - just another avatar I’ve used for personal things. How is the gmail account tied to the plex account?

I just verified that the email in my plex web UI is the correct account and password. If I login to Plex.TV and click account settings, I’m taken to my plex server (you can see my local IP address (198…), I select the user Avatar (same avatar you see in the plex server in the screenshot) I always do from the Plex Select User Login screen and the Plex Web UI displays. Should something else happen?

6

Got me here, and just noticed it, so was gripping for a straw here :wink:
I don’t use Google Auth myself, so clueless, but when said, search on your PMS for Preferences.xml file, and it will show you what your server is logged in as
Ref: https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/

7

@ Dane 22: If you can tell me the name of the log, I can access it from the backend of the server.

As to the prefferences.xml file, I had checked that, it has the correct info - email, plex_uid, plex_gid, etc…

8

Regardless of that, do nuke the entries mentioned in the article, and restart PMS afterwards

And relevant logs would be Plex Media Server.log but remember it rolls over

9

Ok, progress, but unable to get past claiming server.

I nuked the 4 items in the preferences.xml. When I restarted Plex, I was able to connect with he local server (HunterNAS) and now can see things like the logs you requested earlier (attached). It displays a message stating the server was unclaimed and I clicked claim. Then the Settings>General tab is displayed. The general tab shows two warnings. The first is “This server is unclaimed and not secure”. I clicked “CLAIM SERVER”, the button shows ‘busy’ for a second, then comes back and says “CLAIM SERVER”.

I also see a warning that states an update is available - Please Install Manually. Given I’m using a Docker on Unraid, I believe that the creator of the docker does that. I’d be ok, but I’ve never updated a Docker before, so would need instructions.

Also, Remote Access appears to be broken. (Not available outside of your network). It says, First sign in to access your server from anywhere, but clicking “Sign In” just takes me back to the general tab with “Claim Server” button.

Thanks in advance dane22, I appreciate the assist. I’d never have figured this out…

Screenshot:

chrome_2022-05-30_16-24-38
chrome_2022-05-30_16-24-38702×712 72.5 KB

Plex Media Server Logs_2022-05-30_16-14-03.zip (5.7 MB)

10

From your log:

May 30, 2022 16:04:41.487 [0x15157449cb38] WARN - [HttpClient] HTTP error requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxYqE88e (60, SSL peer certificate or SSH remote key was not OK) (SSL certificate problem: certificate has expired)

I’ve reset your server certificate, so restart PMS and try again, but before doing so, make sure that the time on your server is correct as well

11

Thanks for your continuing support dane22.

I verified the date/time -

2022-05-31_11-42-27
2022-05-31_11-42-27636×786 81.7 KB

I restarted PMS.
Opened Plex Web UI, clicked CLAIM SERVER
Same result - button goes away for a few seconds, then returns.
Lastest Log:
Plex Media Server Logs_2022-05-31_11-47-04.zip (4.9 MB)

Thanks in advance for your continued assistance, really appreciate it.

One thing I’ve noticed, there is a warning displayed relative to a version update ( Version 1.26.2.5797 An update is available. Please install manually.). Not sure if that affects this or not. Happy to do an upgrade, but I’m using the Plex Official Docker, so would rather the update come through that than making changes myself.

12

Hi dane22, I’m still having this problem where I can’t claim the server. Still seeing the error

WARN - [HttpClient] HTTP error requesting GET https://plex.tv/api/codecs/h264_decoder?build=linux-x86_64-standard&deviceId=486f1ccb-10a9-423e-bfda-b51aa1153708&oldestPreviousVersion=1.13.8.5395-10d48da0d&version=994f4ee-4302 (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name ‘plex.tv’)

I have no idea how to properly diagnose this or fix the problem. Should I do a complete reinstall? is the problem related to my account somehow? Trying to claim the server does not work (click button does nothing). I’ve looked at my hosts file, there are only 2 entries…

root@HunterNAS:/etc# cat hosts
# Generated
127.0.0.1       HunterNAS localhost
54.149.176.35   keys.lime-technology.com

Totally hosed, no idea what to do. Thanks in advance…

13

Are you using something in between, that maybe do https traffic for you?

14

Not that I know of. Just typical home router, to time warner for internet.

15

Hmm, and not an UNRAID dude…

Does OpenSSL exist on that box, and if not, can you add it?

Then type:

openssl s_client -showcerts -servername plex.tv -connect plex.tv:443

Then show the output

16

Sure! Here’s a sanitized version…

openssl s_client -showcerts -servername plex.tv -connect plex.tv:443

CONNECTED(00000003)
depth=2 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root CA
verify return:1
depth=1 C = US, O = DigiCert Inc, CN = GeoTrust TLS DV RSA Mixed SHA256 2020 CA-1
verify return:1
depth=0 CN = *.myfox.io
verify return:1
---
Certificate chain
 0 s:CN = *.myfox.io
   i:C = US, O = DigiCert Inc, CN = GeoTrust TLS DV RSA Mixed SHA256 2020 CA-1
-----BEGIN CERTIFICATE-----
CERT CHAIN DISPLAYED HERE
-----END CERTIFICATE-----
 2 s:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root CA
   i:C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert Global Root CA
-----BEGIN CERTIFICATE-----
SERVER CERT DISPLAYED HERE
-----END CERTIFICATE-----
---
Server certificate
subject=CN = *.myfox.io

issuer=C = US, O = DigiCert Inc, CN = GeoTrust TLS DV RSA Mixed SHA256 2020 CA-1

---
No client certificate CA names sent
Peer signing digest: SHA512
Peer signature type: RSA
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 4678 bytes and written 437 bytes
Verification: OK
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES128-GCM-SHA256
    Session-ID: 917C709CC1AA8B2D89489457BBEB7C7E5A4A80C96A3661FA1669C55CA6E537FD
    Session-ID-ctx: 
    Master-Key: 16AA367198B7DFB074BEA1C8A740B5D2D51846E4761508857D5590126C1EB5E27B8B7DD13F5235B234E3A36200085AAA
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 43200 (seconds)
    TLS session ticket:
    0000 - 7e cb 0c 4b 99 ce 28 de-46 5a 9c a5 c2 c5 9a f1   ~..K..(.FZ......
    0010 - c0 63 5c 53 5a 0d 88 7e-e5 5c 3d 28 aa c3 15 84   .c\SZ..~.\=(....
    0020 - 34 89 63 69 49 02 f7 05-61 67 0c 4e 21 80 77 17   4.ciI...ag.N!.w.
    0030 - 4f b1 f2 b5 b5 98 59 4f-df b2 5b 00 4c d0 5f 75   O.....YO..[.L._u
    0040 - 53 ae 41 14 42 f3 d7 15-dc 99 1a 5e 2f d8 27 5e   S.A.B......^/.'^
    0050 - 7c 07 21 dd c2 b8 8a 2a-47 e7 3e ca c3 c5 78 34   |.!....*G.>...x4
    0060 - a6 17 e4 fc 1a f0 1f 3e-be 03 26 2a ea 5f 7c c9   .......>..&*._|.
    0070 - c1 4b 47 5d e0 66 0b a7-ef 46 5f 9d 76 af d1 c9   .KG].f...F_.v...
    0080 - b4 66 0a 03 9f e2 1d df-a8 fc bd 3f c2 c3 55 e2   .f.........?..U.
    0090 - a4 30 ba a9 0d 6c 3b e0-44 4c 8b 26 e1 e2 4c 05   .0...l;.DL.&..L.
    00a0 - 5b 9d 53 fb b6 2e 74 71-57 e4 f9 ac 40 6e 57 35   [.S...tqW...@nW5
    00b0 - 84 9a be b3 c0 85 9f bc-24 de 2c 32 0e 02 e1 b7   ........$.,2....

    Start Time: 1655149378
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
---
17

Hmmm…

Check both host file, as well as DNS again, since when I run it, part of what’s returned is:

Server certificate
subject=C = CH, ST = Nidwalden, L = Stans, O = Plex GmbH, CN = *.plex.tv

issuer=C = US, O = DigiCert Inc, CN = DigiCert TLS RSA SHA256 2020 CA1

And you see:

Server certificate
subject=CN = *.myfox.io

issuer=C = US, O = DigiCert Inc, CN = GeoTrust TLS DV RSA Mixed SHA256 2020 CA-1
18

Sorry, not sure what I’m specifically checking for? My hosts file only has two entries, one for my local server IP and one which points to the LimeTech server for my server license.

19

What I’m saying is that when you get the certificate from plex.tv, you are getting the wrong certificate, and to be frank, you are the only one :slight_smile:

So something is making your server getting the wrong cert…

And it can be:

  • Bad setup on your server (Hostname or DNS settings)
  • Some proxy/firewall in between
  • Your ISP

But since you can post here, I’ll rule out your ISP, so we are back to your server

I get a cert that belongs to plex.tv
You get a cert that belongs to myfox.io

20

A post was split to a new topic: Can’t claim server