# HTTP error requesting GET https://plex.tv/ (Could not resolve host: plex.tv)
**URL:** https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492
**Category:** Remote Access
**Tags:** server-linux
**Created:** [May 19, 2022, 11:49pm UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492 "2022-05-19T23:49:22Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@Tony\_T](https://forums.plex.tv/u/Tony_T)
#### Post date: [May 19, 2022, 11:49pm UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/1 "2022-05-19T23:49:22Z")
Getting HTTP error requesting GET [https://plex.tv/](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
---
### Author:  [@Volts](https://forums.plex.tv/u/Volts)
#### Post date: [May 20, 2022, 12:06am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/2 "2022-05-20T00:06:45Z")
Are you referring to the DNS error / host not found messages from your other post? Does this need to be a fresh post?
> [@](#):
>
> $ curl plex.tv
> Moved Permanently
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.
---
### Author:  [@Tony\_T](https://forums.plex.tv/u/Tony_T)
#### Post date: [May 20, 2022, 12:31am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/3 "2022-05-20T00:31:57Z")
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](https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx) (6, Couldn’t resolve host name) (Could not resolve host: plex.tv)
So, I posted here.
---
### Author:  [@Volts](https://forums.plex.tv/u/Volts)
#### Post date: [May 20, 2022, 12:40am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/4 "2022-05-20T00:40:01Z")
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`
---
### Author:  [@Tony\_T](https://forums.plex.tv/u/Tony_T)
#### Post date: [May 20, 2022, 12:57am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/5 "2022-05-20T00:57:56Z")
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
---
### Author:  [@ChuckPa](https://forums.plex.tv/u/ChuckPa)
#### Post date: [May 20, 2022, 1:09am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/6 "2022-05-20T01:09:15Z")
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.
```auto
[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]$
```
---
### Author:  [@Volts](https://forums.plex.tv/u/Volts)
#### Post date: [May 20, 2022, 1:12am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/7 "2022-05-20T01:12:10Z")
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.
---
### Author:  [@ChuckPa](https://forums.plex.tv/u/ChuckPa)
#### Post date: [May 20, 2022, 1:15am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/8 "2022-05-20T01:15:12Z")
> [@Tony\_T](#):
>
> $ curl plex.tv
> Moved Permanently
This result means DNS is working and is as expected.
Plex.tv deliberately lies if you don’t give it any credentials 😈
Ping is turned off. (you might get one but unlikely)
```auto
[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]$
```
---
### Author:  [@Tony\_T](https://forums.plex.tv/u/Tony_T)
#### Post date: [May 20, 2022, 1:42am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/9 "2022-05-20T01:42:27Z")
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
---
### Author:  [@ChuckPa](https://forums.plex.tv/u/ChuckPa)
#### Post date: [May 20, 2022, 1:43am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/10 "2022-05-20T01:43:22Z")
if you reinstall 1.26.1, does the error return ?
Which “1.26.1” do you have ? There have been several.
```auto
[chuck@lizum ~.2004]$ dpkg -l | grep plexm
ii plexmediaserver 1.26.1.5798-99a4a6ac
```
---
### Author:  [@Tony\_T](https://forums.plex.tv/u/Tony_T)
#### Post date: [May 20, 2022, 1:44am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/11 "2022-05-20T01:44:29Z")
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
---
### Author:  [@Volts](https://forums.plex.tv/u/Volts)
#### Post date: [May 20, 2022, 1:45am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/12 "2022-05-20T01:45:09Z")
> [@Tony\_T](#):
>
> only other explanation is that my system fixed itself
There was an eclipse, maybe that was it
---
### Author:  [@Volts](https://forums.plex.tv/u/Volts)
#### Post date: [May 20, 2022, 1:52am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/13 "2022-05-20T01:52:40Z")
> [@Tony\_T](#):
>
> Did not reinstall 1.26.1.5798 after that
If you think it was a Plex bug, doing so would provide valuable information.
I don’t think it was Plex. 🙂
---
### Author:  [@ChuckPa](https://forums.plex.tv/u/ChuckPa)
#### Post date: [May 20, 2022, 1:57am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/14 "2022-05-20T01:57:52Z")
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
---
### Author:  [@Tony\_T](https://forums.plex.tv/u/Tony_T)
#### Post date: [May 20, 2022, 11:58am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/15 "2022-05-20T11:58:08Z")
Reinstalled Version 1.26.1.5798, and now that’s working.
Maybe it was the eclipse, (or most likely something with my system).
---
### Author:  [@system](https://forums.plex.tv/u/system)
#### Post date: [August 18, 2022, 11:58am UTC](https://forums.plex.tv/t/http-error-requesting-get-https-plex-tv-could-not-resolve-host-plex-tv/793492/16 "2022-08-18T11:58:55Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.