Can't connect to Plex directly due to Unbound Topic is solved

Having issues with your DietPi installation or found a bug? Post it here.
danmo117
Posts: 18
Joined: Wed Jun 03, 2020 4:01 pm

Can't connect to Plex directly due to Unbound

Post by danmo117 »

Hi guys,

I've noticed over the past few days that I can't connect to Plex directly via their dashboard website (https://app.plex.tv/desktop/) and it also shows I’m connected indirectly which i believe is via a relay server which is slow. After some digging it seems as though Unbound is the culprit.

Looking at this post on reddit https://www.reddit.com/r/PleX/comments/ ... t_connect/, the solution is to place the line below in the pi-hole.conf file however that file doesn't exist in /etc/unbound/unbound.conf.d/. There is a dietpi.conf however there isn't anywhere obvious in that to drop this line. Any ideas where this can go to fix the Plex issue?

private-domain: plex.direct

Thanks,
Dan
Attachments
Screenshot 2021-04-09 at 16.42.34.png
Screenshot 2021-04-09 at 16.42.34.png (9.74 KiB) Viewed 480 times
User avatar
Joulinar
Posts: 4536
Joined: Sat Nov 16, 2019 12:49 am

Re: Can't connect to Plex directly due to Unbound

Post by Joulinar »

Hi,

I guess you issue is similar to this one viewtopic.php?p=30572#p30572

just create a new .conf file and add the line.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
danmo117
Posts: 18
Joined: Wed Jun 03, 2020 4:01 pm

Re: Can't connect to Plex directly due to Unbound

Post by danmo117 »

That’s done the trick, thanks for pointing me in the right direction.

I can see from the other thread the OP never responded to your last question about confirming what was done.

For me I simply did the following...

Code: Select all

nano /etc/unbound/unbound.conf.d/plex.conf
Then added...

Code: Select all

private-domain: "plex.direct"
Then restarted all services using dietpi-services, no need to reboot.

Cheers.
User avatar
Joulinar
Posts: 4536
Joined: Sat Nov 16, 2019 12:49 am

Re: Can't connect to Plex directly due to Unbound

Post by Joulinar »

thx for sharing 8)
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
User avatar
MichaIng
Site Admin
Posts: 2924
Joined: Sat Nov 18, 2017 6:21 pm

Re: Can't connect to Plex directly due to Unbound

Post by MichaIng »

Here it is explained (bottom section): https://support.plex.tv/articles/206225 ... nnections/
But I didn't really understand how plex.direct can be affected by DNS rebinding, as it is a public domain but does not point your local Plex instance :?. However, as it is a common case, obviously, shall we add this by default via dietpi-software when Plex and Unbound are installed together?
User avatar
Joulinar
Posts: 4536
Joined: Sat Nov 16, 2019 12:49 am

Re: Can't connect to Plex directly due to Unbound

Post by Joulinar »

well or keep it simple and add private-domain: "plex.direct" to our defaul config file? Does it harm? Even if not used?
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
User avatar
MichaIng
Site Admin
Posts: 2924
Joined: Sat Nov 18, 2017 6:21 pm

Re: Can't connect to Plex directly due to Unbound

Post by MichaIng »

It is a public domain, having it in the default config file prevents it from being resolved. Not sure whether that domain is used for any other reason, but if I where a user I would ask why this is blocked by default.

Not a big deal to have an extra file added + removed on those installs/uninstalls.
User avatar
Joulinar
Posts: 4536
Joined: Sat Nov 16, 2019 12:49 am

Re: Can't connect to Plex directly due to Unbound

Post by Joulinar »

ok agreed, let's put the check to both software installations and pull/create the respective config file if not existing.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
User avatar
MichaIng
Site Admin
Posts: 2924
Joined: Sat Nov 18, 2017 6:21 pm

Re: Can't connect to Plex directly due to Unbound

Post by MichaIng »

Resolved with: https://github.com/MichaIng/DietPi/comm ... b53216b858
Changelog: https://github.com/MichaIng/DietPi/comm ... f7b77a69bb
On update, the file will be created as well if PMS and Unbound are both installed.
mail2rst
Posts: 103
Joined: Fri Apr 13, 2018 4:53 pm

Re: Can't connect to Plex directly due to Unbound

Post by mail2rst »

how to confirm that system accept unbound plex.direct file. in my other computer on lan with nslookup command this thing showup

####
"
> plex.direct
Server: nuc.local
Address: 192.168.1.90

DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: plex.direct
Address: 82.94.168.7
"

#####
"
> hello.plex.direct
Server: nuc.local
Address: 192.168.1.90

DNS request timed out.
timeout was 2 seconds.
Name: hello.plex.direct

"

is 82.94.168.7 is correct or my unbound machine ip address need to show (192.168.1.90)? what is the optimize result in nslookup command i expected if system works correct.
Post Reply