Unfortunately, I have no other idea than trying it again (in the hope that it was a transient error on the plex.tv side.)
Delete your server from your account here: https://app.plex.tv/desktop/#!/settings/devices/pms
Then stop and restart your server.
Then use the claiming script from above again.
Tried it all again and the server just doesn’t show in the plex configuration at all.
Is there likely anything logged that will give a clue?
Where do we go from here? I’m extremely disappointed at the moment; the new version of plex dropped about a week after I bought a lifetime subscription and I’ve had nothing but trouble since. Now it’s completely useless and unusable.
There are some errors in the “plex media server.log” which may be relevant. A few “couldn’t resolve hostname” errors relating to plex.tv URLs. I can however resolve these via the command line so it’s not a network issue. Perhaps something going wrong internally?
Plex_Media_server.zip (35.8 KB)
This is concerning. In order to successfully claim your server and for the product to work as expected, it needs to be able to communicate with all of them.
All I can recommend is to again take a close look at your network. Firewall rules, DNS resolvers, their various black and/or white lists.
Maybe try to setup a second instance of Plex server on a desktop computer. Then compare if the same behaviour occurs like on your Raspberry server.
I have double checked everything. The issue started overnight. It was literally working fine, then the next morning it wouldn’t work. No settings, updates, or network changes occurred during that time. I can resolve those same addresses from the command line on 2 different PCs and on my phone both connected to the same network, and off the network. I’m very confident it isn’t my device or my network.
Check your resolv.conf file, what are the contents? You mentioned being able to resolve the domains from 2 different PC’s, but what about the one in question where the error is happening?
If your gateway isn’t in there, add it - Linux can be weird sometimes and remove it leaving just 127.0.0.1.
I can resolve the URL’s contained in the log file from the command line on the device having the issue (as well as the 2 other PC’s).
Resolv.conf is fine, and yes includes the gateway.
I have set it up on a Windows PC and it seems to add fine. Both these machines are on the same network and use the same network configuration (I’ve set them to use DHCP and the router passes the 1.1.1.1 and 8.8.8.8 DNS servers to them). I have zero other issues resolving anything.
@OttoKerner can you have a look at the logs because there is more than just resolve issues in there and the resolve issues may well be a consequence not a cause.
You would have to show the output on that device from dig or nslookup. Right now you have dns-rebinding stopping plex.direct and not resolving for plex.tv. Without that it can’t pull a CERT for the clients to connect to.
Jun 05, 2025 18:51:57.040 [140733198069984] DEBUG - Network: 192-168-0-200.abcdefghijklmnopqrstuvwxyz012345.plex.direct failed to resolve to 192.168.0.200 but instead yielded (null)
Jun 05, 2025 18:51:57.075 [140733198069984] DEBUG - CERT: Forcing refresh.
Jun 05, 2025 18:51:57.075 [140733198069984] DEBUG - CERT: secure connections newly enabled, fetching a cert.
Jun 05, 2025 18:51:57.075 [140733198069984] ERROR - [HttpHeader] invalid 'X-Plex-Device' header value (Raspberry Pi 5 Model B Rev 1.1
How did you manage to create a log file which uses a Windows character codepage, when your server is actually running Linux?
Me@raspberrypi:~ $ dig plex.tv
; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> plex.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12431
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;plex.tv. IN A
;; ANSWER SECTION:
plex.tv. 5 IN A 54.171.25.149
plex.tv. 5 IN A 34.251.50.163
;; Query time: 11 msec
;; SERVER: 192.168.0.1#53(192.168.0.1) (UDP)
;; WHEN: Mon Jun 09 17:13:49 ACST 2025
;; MSG SIZE rcvd: 68
It resolves fine from the command line on the same machine. It doesn’t resolve from within plex media server according to the log file.
I’ve been told this a couple of times, but the dig output above says differently no? The same thing happens if I change the DNS server to anything.
Me@raspberrypi:~ $ dig @1.1.1.1 plex.tv
; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> @1.1.1.1 plex.tv
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5303
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;plex.tv. IN A
;; ANSWER SECTION:
plex.tv. 42 IN A 34.251.50.163
plex.tv. 42 IN A 54.171.25.149
;; Query time: 7 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Mon Jun 09 17:19:41 ACST 2025
;; MSG SIZE rcvd: 68
Perhaps Notepad++ converted it when I opened it in Windows in order to paste it into the browser?
Am I correct in assuming PMS uses plex.direct in referencing itself in the same way some other devices use internal names like mymodem.modem for some internet routers?
And if that is the case how does it do this? Because this problem literally appeared overnight with ZERO system changes (I have quadruple checked).
If I try to resolve plex.direct with dig I do indeed get 0.0.0.0 (from ANY DNS source), which is why I presume it’s an internal thing, but if that’s the case it’s not my machine causing the issue but PMS, no?
Help! I’m having the same problem. Running fine on MAC/iPad/iPhone/AppleTV since 2021. but since the PMS update v.1.41.7.9823-59f304c16 May 24, 2025 have lost everything. Tried eveything in support but no luck. Sorry guys but i’m not really savey with all the jargon above, just hoping someone can solve this for us simpleton’s.
Read all about it here: https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/
And yes, DNS rebinding protection would only affect connecting to a local Plex server within the same LAN.
It has no influence on connections to *.plex.tv, nor on remote Plex servers.
I have the same problem
I cannot fix any option because the plex site shows no server in settings.
I changed my dns for cloudwaflare (before this change i wasn’t able to log in plex forum too. Not sure if related but the certificate was invalid for edge , firefox , etc before that).
Here are errors i see in my log :
04, 2025 06:14:37.494 [7532] INFO - CodecManager: obtaining decoder 'aac'
Jun 04, 2025 06:14:37.881 [6568] WARN - [HttpClient/HCl#1] HTTP error requesting GET https://plex.tv/api/codecs/aac_decoder?build=windows-x86-standard&deviceId=e85f0d53-4afd-482c-84ec-48d59ddeb2cc&oldestPreviousVersion=1%2E32%2E7%2E7621-871adbd44&version=46f74ab-560174306fe167a5978a79dd (60, SSL peer certificate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name 'plex.tv')
Jun 04, 2025 06:14:37.881 [11608] ERROR - Codecs: Failed to download XML for codec 'aac_decoder'
Jun 04, 2025 06:14:37.881 [11608] WARN - Codecs: Failed to download aac decoder; bailing out
Jun 04, 2025 06:14:42.149 [6568] WARN - [HttpClient/HCl#6] 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')
Jun 04, 2025 06:14:42.149 [6568] WARN - [HttpClient/HCl#7] 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')
Jun 04, 2025 06:14:42.149 [12312] ERROR - MyPlex: Failed to retrieve PIN: -60
Jun 04, 2025 06:14:42.149 [3248] ERROR - MyPlex: Failed to retrieve PIN: -60
Jun 04, 2025 06:14:42.176 [6568] WARN - [HttpClient/HCl#8] HTTP error requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxficate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name 'plex.tv')
Jun 04, 2025 06:14:42.184 [6568] WARN - [HttpClient/HCl#a] HTTP error requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxficate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name 'plex.tv')
Jun 04, 2025 06:14:42.186 [6568] WARN - [HttpClient/HCl#9] HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxficate or SSH remote key was not OK) (SSL: no alternative certificate subject name matches target host name 'plex.tv')
Jun 04, 2025 06:14:42.192 [12184] WARN - FeatureManager: Couldn't get features. Trying again soon.
Jun 04, 2025 06:14:42.198 [12304] INFO - Refreshing paths watched by LibraryUpdateManager
i see this error for all call to plex.tv.
I cannot log localy (with admin token). Is it still possible with current plex moves ?
I sadly discover here how dependant plex has become to something external to be used and i don’t know how to fix this.
my settings on my plex on local ip :
Same problem here. Happened overnight. Cannot access my libraries anymore. Tried many different things including server update (1.41.7.9823-70009823), restart, re-claim. PlexOnlineToken=“” in the preferences.xml is empty. Logfile has some 406-errors. Don’t know if they have been there before.
Interesting: Problem seemed to occur only with the main user. Now I don’t have access to the libraries with every user.
@ashley_r361
Your first dig shows udp 512 indicating something molested the packet. If you don’t have a reverse proxy or pi-hole then your router or isp is messing with the lookup. You are also running an un-supported Pi5 OS which may conflict with the binaries in Plex.
Everyone else jumping in here with a “me too”, if you don’t include the zip of your log files preferably from 3 minutes after you have restarted Plex Server then there isn’t much that can be done for you. Also a screenshot of Server>Settings>Network to show that you haven’t entered in incorrect info into the fields would be helpful.
If Plex can’t setup a secure connection to it’s servers (plex.tv) then it can’t validate if you have a Plex/Remote Pass and let the client connect.
I just set up Plex on a friends new iMac with Sequoia. It works great streaming music DNLA to a Linn Majik-DS. Then the next day he can’t find the PlexServer.
You’re propably right. I’m not too familiar with troubleshooting via forums. Just worried about a software that all of a sudden lost its functionality for me. I wished I could show you a screenshot of the server settings but as there is no such thing anymore, this is all I have (similar to rodgr).
Plex Media Server Logfile.zip (13.1 KB)
Server was slow starting so 3 minutes wasn’t enough for everything. Lets fix what did show up.
