Hi all, I wanted to respond to the existing thread(s) with this reply but they had closed due to inactivity.
I came across the issue this morning where the latest Plex app for Roku, would not connect to my Plex server. Setting the setting in the app settings to always allow insecure connections worked, as well as setting security to disabled in the network settings of Plex Server directly. However, I think the the solution I came up with this morning is better suited for security minded people.
DISCLAIMER!
This solution is ONLY tested on routers running DD-WRT, and may NOT apply to others, use at your own risk.
OK, with that said, connect to the routerās setup page, usually http://192.168.1.1
Select the Services tab
Scroll down to DNSMasq, if enabled, click disable for No DNS Rebind.
Click Save, Click Apply Settings, reboot is optional here.
Restart Plex App on Roku, your server āshould be functionalā. I have also gone as far as setting my Roku Plex App to require secure connections and the server has worked fine. Granted, this is limited testing, but Iām going to assume here, that people here are above average user experience so will have at least heard of DD-WRT, if not run it, or another open firmware.
Below, I included a screenshot of correct section:
If security minded please do not disable DNS Rebind protection. Enter the following in the Additional Dnsmasq Options field box: rebind-domain-ok=/plex.direct/
Iāve been getting used to DD-WRT over an AirPort Extreme. Once Apple dropped the product, I got aNetgear R7000 and took off their stock firmware, and put DD-WRT on. My impression is since No DNS Rebind is disabled by default means Remind is ON by default. Since disabling it in my case caused problems, and re-enabling it brought full functionality back, does this mean Plex, or Roku has solved the rebind issues? I did noticed the extra options mentioned in the closed thread, however, I didnāt enter them, and things still work, so is there a reason to at this point ? I think my challenges has been, not to understand what Iām doing, but what DDWRT calls things, and if they actually do what the setting is called.
When I initially installed DDWRT, things just worked, things apparently broke after I started tweaking settings learning what things did, and what people recommended to have setup.
Many more options than Appleās Airport, so itās been a bit of a learning curve, but the router has been rock solid.
When I first saw the problem this morning, I just had the mindset Roku broke something again, as Apple TV, or iPad didnāt have issues. I mainly use InFuse when I want to stream blu-ray content to avoid Plexās transcoding, but I still use Plex as well.
Thatās what threw me initially, the No DNS Rebind setting in DDWRT is Disabled by default, when I enabled it, things stopped working. Itās almost like DD WRT has the habit of doing the opposite of what the setting name is.
Iāll add the command you supplied.
Iām understanding they called the setting āNo DNSRebindā because it means you donāt want DNS Rebinding. So, selecting disable means youāre actually turning it on, and selecting Enable means youāre actually disabling Rebinding. I was mainly looking for clarification that Iām understanding the setting correctly.
So, I donāt think in my initial post I suggested disabling rebind. I apologize if the wrong message came across.
Done, thanks so much. I tested, and things work with a secure connection. I apologize for the mix up. I had gotten one impression of the setting from the DDWRT forums and then a different one here. The enabled no dns rebind + command you gave me works now. When I came posting the solution I found, I came under the impression, there was no official fix yet. Thanks for providing this. Are there any other things I should add when it comes to other devices such as Apple TV, or a Sony BDP, or is the settings given here mainly only needed for Roku ? Thanks again.
It is a setting which affects the server.
It is important for every Plex client (no matter the client type) which is in the same local network as your server, to access said server over an encrypted connection.
Ok, that I understand, it was mainly the DNS rebind that I was a bit confused about.
Here on Plex, the preferred setting is to Enable āNo DNS Rebindā, and enter the rebind command in extra options. On the DDWRT forums they have a mix of opinions varying from similar to here to saying the latest beta versions of DDWRT (which I am running) handlingās rebind internally so the setting isnāt as big a deal now as it was in older software. So, thatās why I was a bit confused over the setting. Since enabling it broke my server, and disabling it fixed it, I thought maybe when I was messing with settings and enabled the no dns rebind option, that I had made a mistake. Either way, the client seems to work now with the suggested settings here.
Was the setting does is to create an exemption rule.
While āDNS rebinding protectionā is still activated globally (āNo DNS rebindingā)
it is allowed for the domain plex.direct.
The whole reason for this is, that the DNS server in dd-wrt cannot distinguish Plexās completely legit activity from a āDNS rebinding attackā.
Thus the āDNS rebinding protectionā needs to be disabled for Plexās domain name.
DNS Rebind Protection is a preference. It works by not allowing a FQDN that resolves to a RFC918 space to connect. However this is exactly what Plex is doing and its not malicious thus the exception using the options field. It does not hurt to have it enabled as its there to generally protect you from DNS hijacking.
Right, follow completely. Because DDWRT cals the Setting āNO DNS Rebindā setting to enable disables global rebind, but the command gives Plex an exception. Setting No Rebind to Disabled, enables global rebind, so the exception isnāt needed, but also puts the network at risk.
Iām straight now with how the setting is labeled and which way to toggle the setting. Thanks for helping clear this up.
OK, with the routing issues taken care of, one more question. How do I access my continue watching list on the newest Plex channel for Roku? by default itās not visible. Other then that, everything else is working now as expected.
