QNAP NAS "Unavailable" after today's Roku channel update

Plex Media Server NAS & Devices
,
1

Server Version#: 1.14.0.5470

One of my Rokus got the new Plex channel update today, and ever since then it cannot connect to my QNAP NAS, which is running the latest Plex server. I’ve power-cycled everything: Roku, routers, NAS; signed out and back in both the server and Roku. The new Plex channel does have connectivity otherwise; it is able to stream from internet-based sources. Two other Rokus in the house which have not yet received today’s update still work with the NAS just fine.

Any suggestions on what else to try?

UPDATE: My second Roku got the Plex update, and immediately stopped working with the NAS as well. Upon inspecting the main router’s logs, I noticed quite a number of these errors:

possible DNS-rebind attack detected: 192-168-1-63.7c843aaf44624bd7ab877907979dee22.plex.direct

I disabled the “Prevent DNS-rebind attacks” option in the router (for the time being), and what do you know, both Rokus started working again.

I do agree with the general consensus here, I much prefer the old Plex UI. I guess “If it ain’t broke, fix it until it is.”

2

My Plex Servers (ubuntu) both became “unavailable” after the roku3 Plex 6.1.1 update. Did yours show up as unavail? or not at all?

3

In your modem/ router,

see if DNS rebinding protection is enabled.
If it is, temporarily turn off as the test & confirmation.

If this is the case, You will need to create a private domain exception
which allows *.plex.direct

4

Unavailable.

5

Thanks for the suggestions. I had already determined that disabling rebinding protection “fixed” the problem. I have no idea how/where to create the private domain exception, however (Tomato-based router). Will probably just leave the protection disabled for now.

6

Chatting with the dev now.

You can turn DNS protection back to where you had it.

In the Roku app, you previously had a value set for Secure Networks (Allow Insecure Connections).

In this update, it wasn’t copied forward.
If you set the value again now to where you want it, it will copy forward

Roku should return to normal

7

Still didn’t work. What did work was changing Allow Insecure Connections from Never to On Same Network. Are you saying that originally this setting was set for Always (I don’t remember what it was set for previously), and it got changed to Never during the update?

1 Like
8

confirmed – allow insecure connections Always.

Just need Plugins back and I’ll quit using Emby.

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.