I would like to see if there is anyone in the user community who is willing to help us investigate a problem.
The host Linux system works normally for all DNS resolving
For reasons unknown, PMS cannot always resolve DNS (e.g… plex.tv)
This appears to occur more with Docker hosts than native installation hosts.
The issue can be confirmed by examination:plex.tvnslookup plex.tv on the shell command line works.
If anyone is experiencing this condition, and can help us (either remote SSH or Teamviewer), please let me know.
Thanks,
3 Likes
Hi, I experienced this issue on 1.23.x. I will try to help as best I can. Please let me know what I can do to help. Thx
Chuck
I am having all types of issues with PMS 1.23.x
I am happy to help.
Thanks
Hans
Hi and thanks for responding.
To get started,
I would like to see your PMS log s ZIP file which capture the DNS problems you’re having .
I’d also like to see your /etc/resolv.conf, and ifconfig output -or-
IPv4 status – WAN and LAN
IPv6 status – WAN and LAN
(Do you have IPv4 internal / external as well as IPv6 internal / external )
@voorhees98
I found your logs in the other thread.
May 21, 2021 20:52:13.492 [0x7fc51c0aab38] DEBUG - NetworkInterface: Watching for changes on the interfaces.
May 21, 2021 20:52:13.493 [0x7fc51fdc40b0] DEBUG - Detected primary interface: 192.168.4.94
May 21, 2021 20:52:13.493 [0x7fc51fdc40b0] DEBUG - Network interfaces:
May 21, 2021 20:52:13.493 [0x7fc51fdc40b0] DEBUG - * 1 lo (127.0.0.1) (loopback: 1)
May 21, 2021 20:52:13.493 [0x7fc51fdc40b0] DEBUG - * 3 eth0 (192.168.4.94) (loopback: 0)
May 21, 2021 20:52:13.493 [0x7fc51fdc40b0] DEBUG - * 4 eth1 (169.254.165.159) (loopback: 0)
May 21, 2021 20:52:13.493 [0x7fc51fdc40b0] DEBUG - * 1 lo (::1) (loopback: 1)
May 21, 2021 20:52:13.493 [0x7fc51fdc40b0] DEBUG - * 3 eth0 (fe80::211:32ff:fed1:6efd%eth0) (loopback: 0)
May 21, 2021 20:52:13.493 [0x7fc51fdc40b0] DEBUG - Creating NetworkServices singleton.
May 21, 2021 20:52:13.493 [0x7fc51fdc40b0] DEBUG - NetworkServices: Initializing...
Would you consider turning off (disable) IPv6 in Control Panel - Network - eth0 ?
Please at least make your presence known if you have this problem, independent of your ability to assist in diagnosis.
1 Like
I am having this issue as well. Not Docker.
nameserver 127.0.0.53
ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
Log filesPlex Media Server Logs_2021-05-26_16-07-47.zip (1.1 MB)
After some investigating, we’re onto something.
Please do the following:
dig plex.tv AAAA
and report the result. You should get
NOERROR response with an SOA record
a SERVFAIL message
This is a good reply.
[chuck@lizum ~.502]$ dig plex.tv AAAA
; <<>> DiG 9.11.31-RedHat-9.11.31-1.fc33 <<>> plex.tv AAAA
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21718
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;plex.tv. IN AAAA
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Wed May 26 21:30:43 EDT 2021
;; MSG SIZE rcvd: 36
[chuck@lizum ~.503]$
Next, Please tell us your modem/router vendor.
We think we’re seeing a commonality and would like to gather more information before digging into it futher.
Here is the response.SERVFAIL , id: 58780
;; OPT PSEUDOSECTION:
;; Query time: 20 msec
Modem: Comcast CBR-T (Bridge mode)
Volts
May 27, 2021, 9:23am
11
fremenusul:
with eero Secure
That definitely converts NXDOMAIN (A and AAAA) responses into SERVFAIL. I can’t convince myself it’s reasonable behavior, so I don’t use eero Secure+.
I had a similar issue a few years ago with the DNS resolver in VirtualBox. It was returning some failure code for all AAAA queries and breaking things. I stopped using that resolver …
Yes was the same issue here (see another thread).
I was having the same issue. I was running plex in docker through my vpn container. I followed the logout login procedure listed on the other thread by @trumpy81 including renaming the preferences.xml file.
After doing this and logging in on the local machine (ubuntu) web browser it took me through a few setup screens for the plex server and i was back in business.
The odd thing is apps (ios, tvos, and such) were able to see my server/media I just couldn’t get to it via the web app.
Here is my dig result from the host machine:
zach@dockerhost:$dig plex.tv AAAA
; <<>> DiG 9.16.1-Ubuntu <<>> plex.tv AAAA
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17693
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;plex.tv. IN AAAA
;; Query time: 8 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu May 27 08:11:43 EDT 2021
;; MSG SIZE rcvd: 36
I would also run it from within the container but it looks like dig isn’t available in the docker image.
Ridley isolated the problem last night and worked around it.
It appears to be isolated to folks who use eero devices.
A verification build of PMS is being built now.
I will have links for folks ASAP.
The error can be verified by
dig plex.tv AAAA
If you get status=NOERROR then all is OKstatus=SERVFAIL then you are impacted.
1 Like
Awesome! Looking forward to the patch!
@ChuckPa FYI I turned off eero secure and plex started working again. There is something going on there for sure.
Please file a trouble report with Eero.
The more folks who report it will hopefully escalate the priority in getting the firmware fixed.
Thanks. I emailed them. I’ll leave secure off for now.
It’s great you were able to determine the issue. I have eero, and eero secure. What should I ask them to fix exactly on their end? I would be happy to email them, but I am not exactly sure from reading this as to what to ask them to fix.
I installed beta v1.23.2.4600 and it seems to be working. I will keep an eye on it. Thanks so much for the fix.
