Hi - attached is the most current Plex Media Server log after restarting the PMS - similar error as before (DEBUG logging is enabled):
Aug 17, 2025 10:16:10.794 [281473498280160] DEBUG - MyPlex: updating with 36 access tokenshttps://plex.tv/api/v2/server/users?auth_token=xxxxxxxxxxxxxxxxxxxx https://plex.tv/api/v2/server/users?auth_token=xxxxxxxxxxxxxxxxxxxx (6, Couldn’t resolve host name) (Could not resolve host: plex.tv)https://plex.tv/api/v2/server/users?auth_token=xxxxxxxxxxxxxxxxxxxx https://plex.tv/api/v2/server/users/subscriptions?auth_token=xxxxxxxxxxxxxxxxxxxx
Please let me know if additional logs are needed.
Plex Media Server.log (321.9 KB)
Aug 17, 2025 10:16:10.794 [281473498280160] DEBUG - MyPlex: updating with 36 access tokens
Aug 17, 2025 10:16:10.796 [281473498280160] ERROR - [HttpHeader] invalid ‘X-Plex-Device’ header value (Raspberry Pi 4 Model B Rev 1.4 )
Aug 17, 2025 10:16:10.796 [281473498280160] DEBUG - [HCl#2] HTTP requesting GET https://plex.tv/api/v2/server/users?auth_token=xxxxxxxxxxxxxxxxxxxx
Aug 17, 2025 10:16:10.802 [281473493856480] WARN - [HttpClient/HCl#2] HTTP error requesting GET https://plex.tv/api/v2/server/users?auth_token=xxxxxxxxxxxxxxxxxxxx (6, Couldn’t resolve host name) (Could not resolve host: plex.tv)
Aug 17, 2025 10:16:10.802 [281473491747040] DEBUG - MyPlex: using cached data for request for https://plex.tv/api/v2/server/users?auth_token=xxxxxxxxxxxxxxxxxxxx
Aug 17, 2025 10:16:10.803 [281473491747040] ERROR - [HttpHeader] invalid ‘X-Plex-Device’ header value (Raspberry Pi 4 Model B Rev 1.4 )
Aug 17, 2025 10:16:10.803 [281473491747040] DEBUG - [HCl#3] HTTP requesting GET https://plex.tv/api/v2/server/users/subscriptions?auth_token=xxxxxxxxxxxxxxxxxxxx
ERROR 6 – Network configuration error to the Gateway (modem/router) and DNS resolver.
Right - but when I resolve plex.tv from the PMS server command line:
Results:
Server: 192.168.100.1
Non-authoritative answer:
so why is Plex reporting that error?
Thanks.
My Plex Server is behind a router using unbound and I used the following for configuring this setup (all was working until today):
https://www.reddit.com/r/firewalla/comments/1610c2q/updating_unbound_for_plex/
I confirmed plex.direct is resolving to ‘0.0.0.0’ as well from the Plex Media Server command line with this setup.
John
jber790
August 18, 2025, 12:50am
45
Hi @ChuckPa - just a follow-on to this - I followed this thread’s test/steps to confirm that plex.tv is reachable:https://www.reddit.com/r/PleX/comments/177cxcv/plex_web_app_not_claiming_server/
When I ran “wget https://plex.tv/claim” , this is was the output (seems plex.tv was moved to account.plex.tv):
wget https://plex.tv/claim https://plex.tv/claim https://www.plex.tv/claim/ [following]https://www.plex.tv/claim/ https://account.plex.tv/claim/ [following]https://account.plex.tv/claim/
>>
Any ideas for how I can get this working again, would deleting/reclaiming my server/certificate fix this?
John
wget uses a raw get of the URL given.The claim endpoint expects a HTTP(s) request and only accepts such as I show here.
[chuck@lizum tv2.2017]$ curl https://plex.tv/claim
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
[chuck@lizum tv2.2018]$
Change the Pi’s DNS server IP to directly use 1.1.1.1 or 9.9.9.9
@ChuckPa - Thanks I confirmed that 1.1.1.1 is being used:
curl https://plex.tv/claim
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
john@jb
[HttpClient/HCl#45] HTTP error requesting GET https://plex.tv/users/8e8b6b93169eb372/avatar?c=1755485140&size=60 (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
Attached is the current current Plex Media Server log.
Am still unable to access plex.tv
J
Plex Media Server.log (406.4 KB)
Turn off the Wireless adapter..
Use only one with PMS . The multipath will drive it nuts because you’ve defined two subnets.
I would use wired only.
Make eth0 as the default gateway.
Restart the box and try again
HI @ChuckPa - I disabled the wireless interface and restarted Plex. It still did not connect, so I enabled it and restarted it again and my Plex Media server connected for Remote Access. Not sure what made this work, but attached is the most recent Plex Media Server log.
JohnPlex Media Server.log (367.6 KB)
There is definitely something whacky with your Ubuntu installation.
I’ve been fighting my way through your logs – which look like this
I have to translate them
Let’s make certain your machine is properly configured.
Check the current locale which should look something like this:
[chuck@lizum ~.2052]$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
[chuck@lizum ~.2053]$
If not, confirm you have this file and it’s defined
[chuck@lizum ~.2002]$ cat /etc/default/locale
# File generated by update-locale
LANG="en_US.UTF-8"
[chuck@lizum ~.2003]$
If this isn’t right for your region and language
sudo update-locale
sudo locale-gen
Restart the entire machine
Pull a fresh set of logs and see if we get readable text
Hi @ChuckPa - that is strange. Here is the output from my Plex server:
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=
I do have a locale file in /etc/default/locale →
cat /etc/default/locale
# Default Ubuntu locale
LANG=C.UTF-8
I updated this using update-locale and locale-gen and restarted the machine.Server Log after restart.
cat /etc/default/locale
# Default Ubuntu locale
LANG=en_US.UTF-8
Plex Media Server.log (203.4 KB)
Whatever you are downloading to is blowing it..
How about making a tar.gz of the Logs directory for me and attaching it ?
As for the DNS – still totally failing.
look at netstat -rn
It should be pointing to the LAN IP of your modem/router via the ethernet adapter (eth0)
This is mine for br0
[chuck@lizum ~.1998]$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 br0
This tells me…
All IP addresses,
Gateway (forwarding IP) 192.168.0.1
All networks not local
It’s a gateway device
MSS & WIndow are 0 (nothing to add)
IRTT (round trip time) 0
Interface br0
If this needs changing, it’s in the Settings - Network - Adapter
@ChuckPa - Attached is the PMS logs (.zip). Here is the output of network -rn from the Plex server:
netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.5.1 0.0.0.0 UG 0 0 0 eth0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
172.18.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-06c7660abb93
192.168.5.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.5.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
My Plex server is using the 192.168.5.0/1 as the gateway which is the VLAN gateway IP from the router/switch this Plex server is connected to.
I have been disabling the wifi adapter on/off and this seems to allow Remote Access.Plex Media Server Logs_2025-08-17_23-15-27.zip (1.2 MB)
and with the wireless adapter enabled:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.5.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 192.168.204.1 0.0.0.0 UG 0 0 0 wlan0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
172.18.0.0 0.0.0.0 255.255.0.0 U 0 0 0 br-06c7660abb93
192.168.5.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.5.1 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
192.168.204.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
192.168.204.1 0.0.0.0 255.255.255.255 UH 0 0 0 wlan0
John
I am still getting the junky logs but
You now have DNS.
I see where you got a new certificate yesterday.
DNS is resolving correctly.
All the requests to Plex.tv have caused the server to be throttled.
Stop PMS and wait. It will resolve itself in about an hour .
After an hour, start it.
I will be awake for a bit (east coast) .
Hi @ChuckPa - I stopped the Plex Media Server overnight and started it again this morning. Attached are the logs - not sure why they are not encoding correctly - I am using the Upload option(up arrow) in this forum post?Plex Media Server Logs_2025-08-18_07-52-04.zip (1.2 MB)
FYI - I am seeing this encoding issue on my end as well if I open any of the archived logs from Notepad. However, if I open the log files in Notepad++ - they display in English - not sure what is happening with the encoding of these logs??
J
J,
Did you shut it down afterward? (it shows about 13 hours since last contact as I write this)
Hi @ChuckPa - yes, I shut down the Plex server last night around 11:45 PM PST and left it off overnight until around 8:00 AM PST today (08-18). So far, no errors but still unclear what action cleared the original reconnect yesterday evening (wifi adapter in the Plex server is still enabled as of this post). Anything else you can see in the logs (attached current log set)?
Also - any ideas/suggestions for fixing the encoding of the PMS logs - very strange?
Thank you.Plex Media Server Logs_2025-08-18_23-42-24.zip (1.8 MB)
It’s not broken – so let’s not look for trouble (ain’t broke – don’t fix it. haha)
Re why your machine doesn’t like the character set encoding.
AS ‘root’
create /etc/systemd/system/plexmediaserver.service.d/override.conf
In it, put the following
[Service]
# Add LC_ALL to fix logfile encoding
Environment="LC_ALL=C"
Now restart PMS
My machine has this (which calls out a specific character set)
[chuck@lizum targets.2003]$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
Yours does not.
Perhaps play with setting your local to the correct country instead of “C” ?
@ChuckPa - thanks for the locale setting override - I tried creating this using both LC_ALL=C and LC_ALL=en_US.UTF-8 and the logs still show in chinese…very strange. For now, I will leave the configuration as is…I can view the logs in a different editor which renders in English.
For reference here is the current output for locale:
$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
Thanks!
system
November 17, 2025, 3:03pm
60
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
