Server can't talk to plex.tv - lots of curl errors in log

Server Version#: 1.24.5.5173
Running on up-to-date Arch linux, with various players connecting via LAN. Was working for a year plus, stopped about two weeks ago. I’ve updated twice in that time frame.

Plex Media Server starts, and I can access the web player via a browser on another machine. Local server is listed, but shown as unclaimed (at one point early on I removed it from the trusted servers intending to re-add it), but when I use the Claim Server button it spins very briefly and returns to saying Claim Server. The warning triangle next to the server name never goes away. And of course I can’t access any content on the server.

Plex Media Server.log shows lots of lines like this:

Oct 30, 2021 11:17:29.942 [0x7f6f664edb38] DEBUG - AutoUpdate: requesting check endpoint: /updater/products/5/check.xml?build=linux-x86_64&channel=16&distribution=redhat&version=1.24.5.5173-8dcc73a59, download: NO
Oct 30, 2021 11:17:29.942 [0x7f6f664edb38] DEBUG - Downloading document https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=16&distribution=redhat&version=1.24.5.5173-8dcc73a59
Oct 30, 2021 11:17:29.942 [0x7f6f664edb38] DEBUG - HTTP requesting GET https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=16&distribution=redhat&version=1.24.5.5173-8dcc73a59
Oct 30, 2021 11:17:29.943 [0x7f6f664edb38] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 30, 2021 11:17:29.943 [0x7f6f664edb38] WARN - HTTP error requesting GET https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=16&distribution=redhat&version=1.24.5.5173-8dcc73a59 (6, Couldn’t resolve host name) (Could not resolve host: plex.tv)
Oct 30, 2021 11:17:29.943 [0x7f6f664edb38] ERROR - HTTP -6 downloading url https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=16&distribution=redhat&version=1.24.5.5173-8dcc73a59
Oct 30, 2021 11:17:29.943 [0x7f6f664edb38] INFO - AutoUpdate: error getting data from plex.tv

On the server I can successfully use “dig -4 plex.tv” and “dig -6 plex.tv”; they both return a status of NOERROR and proper results. A “dig plex.tv A plex.tv AAAA” likewise returns results and NOERROR. If I paste the URL from the GET in the log’s error line after curl, that also seems to work.

So as far as I can tell, from a bash prompt name resolution works just fine. But the Plex Media Server isn’t getting results. I’m not sure what tree to bark up next. Any ideas would be most appreciated.

DNS Timeout perhaps?

Try as a small test and switch DNS to using Google (8.8.8.8 and 8.8.4.4)

Thanks for the thought. I’ve tried that, and just tried again to make sure I wasn’t mis-remembering anything. Same result. The Claim Server button click-spin-return to Claim Server button time is very fast, less than a second, so it doesn’t seem like a timeout.

For what it’s worth I’m running an unbound instance, forwarding non lan queries to 8.8.8.8. But always worth trying to take unbound out of the picture for testing purposes. And I said previously, name resolution seems to be working correctly, AFAICT.

I am still mystified.

I have a feeling, that your setup might be a tad complex. and you haven’t told us about that in details.

But when said, try this for a start regarding Claiming:

Hmmm. I will give that link a shot.

Not trying to hide anything or be particularly complex. I just have a linux server running plex, samba, and unbound as a dns caching resolver. That’s it. I can upload logs if that would be helpful, but it’s just successful lan connections from my web browser player that I’m testing with, and a bunch of the errors I’ve already posted. It was all working. The only thing I can think of that changed was that my cable router died, and I replaced it with a known quantity Motorola. Comcast is the provider. Google Wifi talks to the router and is the dhcp server on the network.

I ran claimpms.sh and got the following:

Comparing entered passwords
Comparing entered passwords ok
Validating IP address
Getting PMS Server Identifier
Getting PMS Server Identifier ok
Getting User Token from plex.tv
Getting User Token from plex.tv ok
Getting PMS Claim Token
Getting PMS Claim Token ok
Claiming server
Fatal error happened
HTTP returned Status 500

So still searching for things to try.

@jtosburn

May I see a tar.gz of the Logs directory?

Best log to grab would be

  1. Restart Plex
  2. Wait 2 minutes
  3. Stop Plex
  4. Now grab the tarball

@ChuckPa

PMS_Plugin_Logs.tar.gz (7.1 KB)
Logs.tar.gz (16.2 KB)

That’s stopping Plex. Clearing old logs. Start Plex, wait two minutes. Connect via web client from another machine on the LAN. Attempt to claim the server. Stop Plex.

Appreciate you taking a look.

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