HTTP error requesting GET https://plex.tv/ (Could not resolve host: plex.tv)

Plex Media Server Remote Access
1

Getting HTTP error requesting GET https://plex.tv/ when attempting to Match or Fix Match

curl reports:
$ curl plex.tv
Moved Permanently

Ping, however, does get a response:
PING www.plex.tv (172.64.153.236) 56(84) bytes of data.

64 bytes from 172.64.153.236 (172.64.153.236): icmp_seq=1 ttl=56 time=35.7 ms

Version 1.26.1.5798

2

Are you referring to the DNS error / host not found messages from your other post? Does this need to be a fresh post?

That’s 100% normal. It means curl was able to look up the host, made a successful connection, and got a response.

172.64.153.236 is associated with Plex.

3

Thought this was a library management issue first, so I posted in the metadata and adding files section first, but now it appears to be a PMS issue with:
[HttpClient] HTTP error requesting GET Sign In | Plex (6, Couldn’t resolve host name) (Could not resolve host: plex.tv)

So, I posted here.

4

Linux (what distro) on a Pi?
Docker involved?

What’s in /etc/resolv.conf?
If it’s a systemd system, is systemd-resolv listening on 127.0.0.53?
What’s the output of dig plex.tv A plex.tv AAAA +nofail

5

I just updated to the 1.26.2 beta, and now plex.tv host name is resolved.
I had previously re-installed the 1.26.1 and that did not resolve the issue.
Can’r confirm, but possibly a bug in 1.26.1

6

DNS lookup failures (failure to find plex.tv) is not a PMS bug.
That’s a system / network / ISP type problem

open a terminal window: nslookup plex.tv

You should get back answers like this if your DNS is resolving correctly.

[chuck@lizum ~.2002]$ nslookup plex.tv
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	plex.tv
Address: 54.171.30.185
Name:	plex.tv
Address: 18.200.219.245
Name:	plex.tv
Address: 63.34.174.176
Name:	plex.tv
Address: 52.49.172.158
Name:	plex.tv
Address: 52.209.234.37

[chuck@lizum ~.2003]$
1 Like
7

Yes agreed. That’s why I asked about the system setup too. OP mentioned Unbound in the other thread. My guess is that the system’s DNS configuration wasn’t complete when Plex couldn’t complete resolution.

8

This result means DNS is working and is as expected.

Plex.tv deliberately lies if you don’t give it any credentials :smiling_imp:

Ping is turned off. (you might get one but unlikely)

[chuck@lizum ~.2003]$ ping plex.tv
PING plex.tv (54.171.30.185) 56(84) bytes of data.
^C
--- plex.tv ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2042ms

[chuck@lizum ~.2004]$
9

Agreed, should not be a PMS bug,
But only other explanation is that my system fixed itself in the short period from when I updated from 1.26.1 (which had this issue all day) to 1.26.2 beta, as it is now fixed

10

if you reinstall 1.26.1, does the error return ?

Which “1.26.1” do you have ? There have been several.

[chuck@lizum ~.2004]$ dpkg -l | grep plexm
ii  plexmediaserver                                             1.26.1.5798-99a4a6ac
11

1.26.1.5798
re-installed 1.26.1.5798, error persisted.
installed 1.26.2.5797, fixed
Did not reinstall 1.26.1.5798 after that

12

There was an eclipse, maybe that was it

1 Like
13

If you think it was a Plex bug, doing so would provide valuable information.

I don’t think it was Plex. :slight_smile:

14

Reinstalling 1.26.1.5798 would provided the needed datapoint & confirmation.

As you see, I’ve been running this version for some time but that’s not to say it’s perfect in all network configurations either

1 Like
15

Reinstalled Version 1.26.1.5798, and now that’s working.
Maybe it was the eclipse, (or most likely something with my system).

16

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