Server Version#: 1.15.1.780 on Ubuntu 16.04.6 LTS
I did a upgrade to the latest version of plexmediaserver, since, the process doesn’t resolve the plex.tv/downloads.plex.tv domains for some reason.
I can manually resolve the domains with nslookup without problem, but the server won’t.
Some related logs:
Mar 12, 2019 23:44:40.637 [0x7f0c9dffb700] DEBUG - AutoUpdate: requesting check endpoint: /updater/products/5/check.xml?build=linux-x86_64&channel=8&distribution=debian&version=1.15.1.780-a27ffa5be, download: NO Mar 12, 2019 23:44:40.637 [0x7f0c9dffb700] DEBUG - Downloading document https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=8&distribution=debian&version=1.15.1.780-a27ffa5be Mar 12, 2019 23:44:40.637 [0x7f0c9dffb700] DEBUG - HTTP requesting GET https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=8&distribution=debian&version=1.15.1.780-a27ffa5be Mar 12, 2019 23:44:40.642 [0x7f0c9dffb700] ERROR - Error issuing curl_easy_perform(handle): 6 Mar 12, 2019 23:44:40.642 [0x7f0c9dffb700] WARN - HTTP error requesting GET https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=8&distribution=debian&version=1.15.1.780-a27ffa5be (0, No error) (**Could not resolve host: plex.tv**) Mar 12, 2019 23:44:40.642 [0x7f0c9dffb700] ERROR - HTTP -6 downloading url https://plex.tv/updater/products/5/check.xml?build=linux-x86_64&channel=8&distribution=debian&version=1.15.1.780-a27ffa5be Mar 12, 2019 23:44:40.642 [0x7f0c9dffb700] INFO - AutoUpdate: error getting data from plex.tv
Mar 12, 2019 23:46:24.928 [0x7f0c9dffb700] DEBUG - HTTP requesting GET https://downloads.plex.tv/codecs/a22632d-2115/linux-x86_64-standard/libaac_encoder.so Mar 12, 2019 23:46:24.932 [0x7f0c9dffb700] ERROR - Error issuing curl_easy_perform(handle): 6 Mar 12, 2019 23:46:24.932 [0x7f0c9dffb700] WARN - HTTP error requesting GET https://downloads.plex.tv/codecs/a22632d-2115/linux-x86_64-standard/libaac_encoder.so (0, No error) (Could not resolve host: **downloads.plex.tv**) Mar 12, 2019 23:46:24.932 [0x7f0c9dffb700] ERROR - Codecs: Download failed: Failed to download 'https://downloads.plex.tv/codecs/a22632d-2115/linux-x86_64-standard/libaac_encoder.so': -6 Mar 12, 2019 23:46:24.932 [0x7f0c9dffb700] ERROR - Error configuring transcoder: Encoder install failed: aac
Where is this running please?
VM, container, or native?
DNS Lookup failures are associated with the host, not Plex.
Native on a Intel Nuc.
Strange thing is that nslookup in CLI works just fine. I thought also that it shouldn’t be a Plex specific thing, but I can use curl to fetch those URLs that are failing inside of Plex without any problem. Any idea?
Could the error message be wrong?
Did some more digging. When I restart plexmediaserver, it seems that it get some requests through, but from one second to another, it stops resolving the domain. Log:
Mar 13, 2019 07:49:18.674 [0x7fdcaeffd700] DEBUG - Starting file watcher for com.plexapp.system
Mar 13, 2019 07:49:18.675 [0x7fdcaeffd700] DEBUG - Spawned plug-in com.plexapp.system with PID 13018
Mar 13, 2019 07:49:18.675 [0x7fdcaeffd700] DEBUG - [com.plexapp.system] Sending command: GET /:/prefixes
Mar 13, 2019 07:49:18.941 [0x7fdce6ada700] DEBUG - HTTP 200 response from GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Mar 13, 2019 07:49:18.949 [0x7fdd02f9b700] DEBUG - HTTP 200 response from GET https://plex.tv/api/codecs/aac_decoder?build=linux-x86_64-standard&deviceId=xxxxxxxxxxxx&oldestPreviousVersi$
Mar 13, 2019 07:49:18.950 [0x7fdd02f9b700] DEBUG - HTTP requesting GET https://downloads.plex.tv/codecs/a22632d-2115/linux-x86_64-standard/libaac_decoder.so
Mar 13, 2019 07:49:19.046 [0x7fdd02f9b700] DEBUG - HTTP 200 response from GET https://downloads.plex.tv/codecs/a22632d-2115/linux-x86_64-standard/libaac_decoder.so
Mar 13, 2019 07:49:19.048 [0x7fdd02f9b700] DEBUG - Codecs: Downloading current version of mpeg4 decoder
Mar 13, 2019 07:49:19.048 [0x7fdd02f9b700] INFO - CodecManager: obtaining decoder ‘mpeg4’
Mar 13, 2019 07:49:19.048 [0x7fdd02f9b700] DEBUG - HTTP requesting GET https://plex.tv/api/codecs/mpeg4_decoder?build=linux-x86_64-standard&deviceId=b2e65f0a-0a4e-473d-8c6f-ce1c20049ce2&oldestPreviousVersion=1%$
Mar 13, 2019 07:49:19.137 [0x7fdcaffff700] DEBUG - HTTP 200 response from GET https://plex.tv/servers/c8cbee6829aa247753f866237bd4c52f9ec5bba5/access_tokens.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1$
Mar 13, 2019 07:49:19.137 [0x7fdcaffff700] DEBUG - MyPlex: updating with 16 access tokens
Mar 13, 2019 07:49:19.138 [0x7fdcd57fa700] DEBUG - HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Mar 13, 2019 07:49:19.142 [0x7fdcd57fa700] ERROR - Error issuing curl_easy_perform(handle): 6
Mar 13, 2019 07:49:19.142 [0x7fdcd57fa700] WARN - HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (0, No error) (Could not resolve host: plex.tv)
Mar 13, 2019 07:49:19.142 [0x7fdcd57fa700] ERROR - Error parsing content.
Mar 13, 2019 07:49:19.142 [0x7fdcd57fa700] ERROR - Error parsing XML: Error parsing file.
Mar 13, 2019 07:49:19.142 [0x7fdcd57fa700] DEBUG - HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Mar 13, 2019 07:49:19.146 [0x7fdcd57fa700] ERROR - Error issuing curl_easy_perform(handle): 6
Mar 13, 2019 07:49:19.146 [0x7fdcd57fa700] WARN - HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (0, No error) (Could not resolve host: plex.tv)
Mar 13, 2019 07:49:19.146 [0x7fdcd57fa700] ERROR - Error parsing content.
if you get some but not others, your DNS is timing out.
IF not google, switch to it.
Compare ping times to your ISP DNS with 8.8.8.8 and 8.8.4.4.
Take the fastest.
I had the same issue. Turns out that DNSSEC-Trigger was causing the issue. It was overwriting the resolv.conf file completely with the localhost address (127.0.0.1).
I only found this out after trying to update and wget a package, and wget could not resolve downloads.plex.tv (and I couldn’t browse to the site in firefox either).
I hope that helps… not for me to figure out this DNSSEC thing.
system
Closed
July 25, 2019, 9:13pm
7
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.