Plex media server 1.23.0.4438 unable to access server content (could not resolve host plex.tv)

Plex Media Server
63

I’m in a similar situation, running on bare Arch Linux, but without IPv6. Your comment about the resolv.conf lead me to investigate further.

In the end, I symlinked resolv.conf to systemd-resolved, as suggested in the Arch Linux wiki. This seems preferable to me to maintaining a separate DNS configuration in that file. So far I’m not getting any curl errors.

So it seems like PMS is using resolv.conf directly as of version 1.23, instead of querying the OS to do DNS resolution. Probably nothing to do with IPv6 in the case of Arch Linux.

64

If you’re on a system with systemd-resolved and you don’t have an /etc/resolv.conf, I think that’s the best solution.

That’s basically correct.

We did similar research in this thread. I think you’ve already done the “right” thing. Plex is also going to add another fallback mechanism.

Name resolution issues causing inability to claim server - Arch Linux - #37 by Ridley

1 Like
65

Perfect!

I had not found that thread, because I did my initial googling before it was started. I’m glad we came to the same conclusion and the threads are linked now.

1 Like
66

I guess I picked the wrong time to migrate to a new server. I have wasted countless hours on this over the past week. I tried the latest docker tag and same resolve issues others are reporting. I installed 1.22.3.4523-d0ce30438 and resolve issues are gone. I see people reporting that it’s fixed in this thread, but it’s not in the latest image. Please get this under wraps. I’ve been a plex pass user for years and I’m pretty disappointed with the extent of this issue. No I’m not using an eero and no I did not have these issues on my old FreeBSD server.

May I also suggest you pull your docker images that have this issue. It might save someone else hours of their life that they will never get back.

2 Likes
67

What specific symptoms are you referring to? The original issue for this thread had been solved, including for the latest versions (I’m running 1.23.3.4706-f48049cad).

It was an issue with incorrect DNS results being returned in some situations (eero secure bring one of them). Plex devs worked around this issue in their code, even though the problem wasn’t caused by them.

I would suggest you perform some testing and report your findings here and ask for some help.

1 Like
68

I was getting the same errors as the OP. That was how I stumbled on this thread. This is a Plex issue if only certain builds have issues. Out of all the apps I use, Plex is the only one affected and the only one I had issues with when I migrated to a different hosting server. So naturally I thought it was on my end with permissions on my data.

When you use the beta or public tags for the docker image it will pull the latest package. You can watch it pull and it install it, but as soon as the server starts it no longer can resolve. I just did another experiment. Now when I load the latest tag it works as it’s supposed to where as last night it would not. I wonder if 1.22.3.4523-d0ce30438 was enough to at least get my new server claimed properly.

I spoke too soon. Getting resolve issues on the latest docker image. I see you are using 1.23.3.4706-f48049cad which has fixed your issue, but that version has yet to be pushed to their docker repo. I’ll just use 1.22 for now.

FWIW I do use cloudflare dns for my domain, but nothing has changed there.

69

I just installed v1.23.3.4707-ebb5fe9f3 and still getting the same errors. Rolling back to 1.22.

Jun 21, 2021 11:36:06.531 [0x7f1f7a34fb38] ERROR - Error issuing curl_easy_perform(handle): 6
Jun 21, 2021 11:36:06.531 [0x7f1f7a34fb38] WARN - HTTP error requesting GET https://metadata-static.plex.tv/4/gracenote/4bfe35fdbc8e161c2f2e1ee6185c3542.jpg (6, Couldn't resolve host name) (Could not resolve host: metadata-static.plex.tv)
70

This specific DNS resolver issue is only fixed in 1.23.4 - which should hit beta soon.

71

Awesome! Thank you very much for reporting back

72

I just updated to 1.23.4.4712-1f0ed4aea and I’m still get resolve errors in the logs.

Jun 24, 2021 23:33:12.730 [0x7f497f2ddb38] DEBUG - HTTP requesting GET https://plex.tv/api/codecs/h264_decoder?build=linux-x86_64-standard&deviceId=06851aa7-7089-495f-86e3-dc9cc59a8eec&oldestPreviousVersion=legacy&version=fa235d6-3858
Jun 24, 2021 23:33:12.731 [0x7f497f2ddb38] ERROR - Error issuing curl_easy_perform(handle): 6
Jun 24, 2021 23:33:12.731 [0x7f497f2ddb38] WARN - HTTP error requesting GET https://plex.tv/api/codecs/h264_decoder?build=linux-x86_64-standard&deviceId=06851aa7-7089-495f-86e3-dc9cc59a8eec&oldestPreviousVersion=legacy&version=fa235d6-3858 (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
74

Still same problem on QNAP 1.23.4.4712-1f0ed4aea. I need to edit my resolv.conf in order to get it to work.
I also get “A required codec could not be found or failed to install” on multiple films. Even those that I could start and watch 10 mins of. Suddenly I get the error and can’t even watch from the beginning again.
I had to revert to 1.22.3.4392 and everything works fine again.
(Have tried clean installs to no avail).

75

Same here as well. Docker with 1.23.4.4712-1f0ed4aea produced the plex.tv issues, can’t claim server or find it with plexamp, etc.
Reverting to 1.22.3.4392 fixed it.

76

Well… tried to install 1.23.5.4801-bc4dd58bb-x86_64.qpkg on QNAP today. I got the “codec not found” error until i put 8.8.8.8 in resolv.conf after which it worked again.

77

I’m still experiencing this issue. I’ve reset my DNS to 1.1.1.1 and 8.8.8.8, neither of which had any effect. I can load plex.tv just fine otherwise via getent hosts plex.tv, curl plex.tv, and firefox.

version: 1.24.1.4931, raw install on Arch. It does not seem to be resolved in 1.24?

78

Actually, I was just able to get it to finally submit (claim media server action) by flushing my dns cache. Looks like I was using systemd-resolve, which I flushed using

sudo systemd-resolve --flush-caches

I realized my whole system was not resolving a new ip for plex.tv because nslookup plex.tv would timeout even though I can get to the site via firefox. Restarting the service was not sufficient.

79

I am still having this issue.

v1.24.2.4973-2b1b51db9 via the linuxserver image.

Can curl plex.tv from within the container, and have tried the FALLBACK_NAMESERVER env to no avail. Other containers on the system have no dns issues.

Edit: Reverting to v1.22.3.4523-d0ce30438 fixes the issue. This is definitely a regression within Plex.

80

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