DNS Resolution Problem Preventing Claiming Plex Server on TrueNAS Scale 22.12.2

[Zeshue]

I just upgraded to Bluefin 22.12.2 a couple of days ago and had to delete and re-create a bunch of TrueCharts apps due to the newer versions being incompatible with the previous configs which was annoying, but fine. Everything was going well until I did this to my plex app. When it started up (with the claim token within the 4 minute window they give you), it failed to validate the claim, and the "Claim Server" button on the Settings -> General screen does a little animation when clicked but doesn't do anything else. I figured out that I can start an incognito session in Chrome and the button will work once from there. But I still get the same issue where it tells me that "There was a problem signing into Plex". Looking at the logs, it appears like the issue is coming from an issue with resolving plex.tv, which appears several times throughout the logs. Below are some examples:

WARN - [HttpClient/HCl#d3] HTTP error requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxjb8HMK (6, Couldn't resolve host name) (Could not resolve host: plex.tv)

HTTP error requesting GET https://plex.tv/updater/products/5/...ribution=debian&version=1.31.1.6733-bc0674160 (6, Couldn't resolve host name) (Could not resolve host: plex.tv)

WARN - [HttpClient/HCl#cc] HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxe host name) (Could not resolve host: plex.tv)

WARN - [HttpClient/HCl#cb] HTTP error requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxe host name) (Could not resolve host: plex.tv)

WARN - [HttpClient/HCl#c9] HTTP error requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxe host name) (Could not resolve host: plex.tv)

I thought this might have just been an issue with the TrueCharts version (1.31.1.673_13.0.6), but I'm also having the exact same issue with the official version as well (1.32.0.6918_1.7.37), so I'm kind of at a loss for what's going on. I have tried disabling everything that I could think of that could possibly mess with the network connection (pihole, traefik, k8s-gateway) to no avail, and I was using only default config parameters for Plex (other than the paths to my media) so I don't think it's that either. If anyone has any ideas of what's going on or has experienced this themselves, I would love to hear your thoughts and/or possible workarounds for this issue.

 

[shortbloke]

I've been fighting the same issue. For me I fixed it by using the TrueCharts version and editing the configuration and setting: DNS Configuration -> Options -> Name: ndots Value: 1. I don't think this configuration was in an older version of this package, but creating a new plex instance it defaults to "2".

 

[brianlovelace]

Hey there @Zeshue have you figured this out?

Having the same issue after I updated to 22.12.2

 

[Zeshue]

I was able to fix this by removing all value from the "Additional Domains" from the Networking -> Global Configuration settings. Hope this helps anyone else with this issue!

 

[kuruption]

I noticed this issue with the charts from Truecharts, both in the Plex and the Overseerr apps.

I filed a ticket but was scolded by Truecharts admins for pointing out that ndots is probably the root cause, "Users shouldn't be modifying ndots!" although setting it to 1 clearly fixes the issue, and even after pointing out the default is 1 in TrueNAS (and Linux in general, check the man page) they incredulously banned me from their github after proclaiming it must be a misconfiguration of my DNS without allowing me to retort.

Anyway, I did as @Zeshue recommended and removed my domains from additional domains, which works but is at best a work around. I also pointed out that some Truecharts charts, like their Plex chart!!!!, allows users to modify ndots in the advanced settings... but again got scolded I shouldn't be doing that.

So with that said, you could install the Truecharts Plex chart, change ndots (despite them recommending you don't do that), and it'll fix the issue for Plex, but it won't fix other single-dot domain name resolution from any other app you may have installed.

 

[Lafunamor]

Can you explain a bit in more details @kuruption ? I'm not able to follow and I have this issue with prowlarr. It's for some reason not able to properly resolve DNS in some cases... I can dig them manually but nslookup and curl fail.