BEWARE: Qnap's new QTS 4.3.5 BETA problems with Plex

Plex Media Server NAS & Devices
1

I just upgraded to the new QTS version 4.3.5 and now Plex is no longer working. It starts up fine, but can’t be accessed. This is confirmed by other users on the QNAP forum.

One user reported that as a workaround, downgrade Plex server to 1.13.4.x. That workaround has been confirmed to work. Personally, I couldn’t try as I am unable to find older PMS versions (Plex website only offers current version).

I hope Plex can fix this soon.

1 Like
2

I have several older versions of Plex for Intel based Qnaps on my OneDrive available, can confirm that 1.13.2 is also working fine.

If I find the other versions of Plex I’ll them there also.

Modirator: removed link…Please do NOT redistribute Plex SW!

1 Like
3

Awesome @Gouldin, thanks a lot!

EDIT: OneDrive says the folder is empty :slight_smile:

4

Ah, sorry. Laptop went to sleep while uploading the files… Will be there in around 10 minutes :slight_smile:

1 Like
5

Ok guys, until Plex has fixed this, you can run 1.13.4, which you can download for 64bit QTS from this link:

MODERATOR: Link removed…please don’t post links

It actually works!

6

Thanks, fair bit newer than the versions I had. Still uploading the others and will put that version on too, just for an easy archive in the future :+1:

1 Like
7

Correct.

There was a change in how the HTTP server connects to the NIC in v1.13.5+ that is causing the issue.

8

I updated to qnap 4.3.5 and had no issues!
Plex version 1.13.6.5339
Except although i had 2 friends streaming the remote icon was red. (should mean no remote connection)

So to play it safe i downgrade to 1.13.4 .5271
The remote icon is now green and 2 friends still streaming!!

9

I"m going to jump here and ask everyone to remain calm.

  • QTS 4.3.5 is still BETA.
  • As is always best, beta is not final and cast in stone. It’s still being tested. It is not Final Release and subject to change should issues be discovered.
  • If you’ve discovered issues with 4.3.4 Beta, Did you report them to QNAP before backing down to QTS 4.3.4 Production? (this is how Beta software is tested)
  • I am here and can help coordinate between Plex and QNAP should it be needed to find the root problem.
10

Hey @ChuckPa

I don’t think anyone is not calm :slight_smile: We found a workaround, so all good. And of course, if you install a beta, you better expect stuff to break. So again, all good.

I’ve reported this on QNAP’s beta forum.

Thanks for chiming in.

11

I’m chiming in only because of some of the Plex-Qnap comments in the QNAP forum.

There were statements of “deal breaker” and “show stopper” because the sky was falling all because the word “Beta” had been overlooked (or ignored) .

I extended the offer to come look me up over here so I can coordinate with our Engineering team and QNAP as needed to find the root cause and correct it.

As always, I’m here and happy to help resolve whatever the problem is. We will get there, even if we have to beat it within an inch of its life in the process. :smiley: :smiling_imp:

12

What would you need to approach your QNAP contacts? Happy to help and dig deeper.

13

I see discussion of breaking Plex. First and foremost, I need to know what ‘breaks’ :smiley:

How can it be demonstrated / replicated ?

Any log files which capture this (DEBUG logging only)

14

See my opening post.

Basically, PMS 1.13.5 and 1.13.6 startup fine on QTS 4.3.5, but they are not accessible. Plex/Web can’t find the server and you can’t connect locally either (https://1.2.3.4:3200/web). As if the built in web server was down or not bound to a network interface (which wouldn’t surprise me, because networking is totally borked in the QTS 4.3.5 beta - tons of other issues there).

15

Is IPv6 enabled?

16

Well… I didn’t configure it. The QNAP uses stateless auto config for IPv6 by default. I have mine at the defaults.

17

it’s not stateless. :slight_smile:
Auto config means it’s just waiting for a DHCPv6 IP address with the DNS6 and gateway IP address to be pushed. Nothing more.

Best practice, with Plex or anything, is to disable V6 or V4 if not used on that LAN segment. The gateway device(s) will handle the translations.

PMS itself does not have appreciable IPv6 support because of the IPv6 global adoption rate. It is only now in its infancy in PMS.

I believe the best we can do to help QNAP and Engineering here is to be as finite as possible, controlling the network configuration to the best of our ability. The more controlled it is, the easier it is to replicate.

To this I would cite as example

IPv6: Disabled
IPv4: DHCP (assigned IP: 192.168.x.x, DNS: 192.168.x.x, gateway: 192.168.x.x – report the values assigned)

Next, from the shell:

netstat -rn
netstat -an | grep ':324'

This tells us if PMS has been able to bind(), listen() and accept(). (ready for client connections).

18

Ok, I will do that tomorrow (getting late here in Europe): Disable IPv6, install PMS 1.13.6 (right now I am rolled back to 1.13.4, which works just fine), and then report back with my findings.

19

Thanks. Enjoy the rest of your evening.

1 Like
20

And adding to all here…

Please DO NOT post download links !