mirror of
https://github.com/tubearchivist/tubearchivist-plex.git
synced 2026-03-23 20:37:11 +00:00
[GH-ISSUE #85] [Bug]: Scanner urlopen error Name does not resolve #32
Labels
No labels
bug
bug
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tubearchivist/archived-tubearchivist-plex#32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kuzi-moto on GitHub (Nov 27, 2024).
Original GitHub issue: https://github.com/tubearchivist/tubearchivist-plex/issues/85
I've read the documentation.
Operating System
TrueNAS Scale ElectricEel-24.10.0.2
Your Bug Report
Describe the bug
After installation and configuration, the scanner is unable to detect any media.
Steps To Reproduce
Expected behavior
Downloaded YouTube video to appear in library.
Relevant log output
Anything else?
I have double and triple-checked that the URL is indeed correct. I installed dnsutils in the container, and made sure that the container could resolve the path.
My DNS server is my OPNsense router running AdGuard Home. All subdomains on example.com point to my reverse proxy running Traefik which provides LetsEncrypt certificates for SSL.
I use split DNS, so anything on the internal network should route to the reverse proxy's internal IP. But if somehow it ignores my internal DNS server and uses a public one that provides my external IP address, I have NAT reflection enabled to forward the request to my reverse proxy as well.
It's weird because when I attempt to scan the library files, I can see several DNS requests for mydomain.example.com from the host running Plex. I wonder if the scanner is ignoring my system's DNS settings?
Sorry if this problem is not directly related to the TubeArchivist plugin, feel free to direct me somewhere else.
@lamusmaser commented on GitHub (Nov 27, 2024):
Let's go over a few starting things.
First, this communication is from Plex to TA. You listed that you can see some DNS traffic coming from the Plex host, which is what I would expect. The dnsutils "in the container" ‐ which container?
The rest looks like it should work. The error is very specific, so it has to be something from Plex's side going out to TA.
One thing to note is that Plex may have its own resolution service, since it is built with Python. That could cause it to not resolve based on the local resolver, but I'm hesitant to say this is the issue if you are seeing some DNS requests from that host.
@kuzi-moto commented on GitHub (Nov 28, 2024):
The Plex container, using nslookup to resolve mydomain.example.com.
Yeah I can't seem to figure it out 🤷♂️ I changed the URL to google.com just to try and that seemed to work, or it at least returned a different error.
What a strange issue...
@kuzi-moto commented on GitHub (Nov 28, 2024):
Well here's something interesting... I tried setting my TrueNAS nameserver to 1.1.1.1 and restarted my Plex container. Scanned the library files and it worked fine!
Guess there is some weird issue between Plex and my DNS server configuration that I'll have to figure out.
I suppose we can consider this one case-closed as it doesn't have anything to do with TubeArchivist.