Wouldnt have to post a link if Plex actually had a download previous version likes most every other company does… Clearly the files still exist so makes no sense not to offer a way to access them without knowing the complete version of the file… Just saying… =] …
1 Like
I did what you noted and plex still becomes unavailable after 1-2 minutes… I have sent you my logs and the output of the commands you put for shell…
Note: I had to downgrade to 1.13.4 in order to be able to have plex run long enough to export the logs.
I was one of the people that said Plex not working was a deal breaker on the QNAP forums. I am well aware it is a beta firmware and it was not “overlooked” or “ignored”. I knew the risk and accepted it when I installed and was well aware I might have to downgrade back to 4.3.4. Without trying to install it and see what works or doesnt I would have never known. Since Plex is my primary DVR I cant just not have it working. If you want to buy me another NAS to test on I would be happy to take it and help out… =] lol
I also have seen a lot of posts from Plex team members that say “We do not support plex on beta firmwares so sorry about your luck”. Knowing you would be happy to help and figure things out I am happy to test by updating plex back to the newest version or even a beta versions when Plex is not recording and downgrade after we done testing. So if there is any else you want me to test or do please let me know…
This is seriously bothering me. Extremely so. I mean WTH? Just so you know, I am going to post the download link everywhere for as long as it pleases me. And you know why, I don’t think I have to explain that.
So here it is once more for everyone who has to downgrade to get their Plex working again:
There is ZERO reason for you (Plex) to remove this. Don’t be that guy.
EDIT:
Of course the link was deleted again and I have received a warning for posting it. Way to go, Plex. You just lost a lot of respect from me.
3 Likes
Just wanted to share with everyone some of the findings me and @ChuckPa have found via testing… We continue to try and test different things to determine what in 1.13.6.X might be causing the issue and will share back more if there is a fix/change that can be done.
-
QTS 4.3.4 and Plex 1.13.6.X (and previous versions): Work without issues
-
QTS 4.3.5 (beta) and Plex 1.13.6.X: Does not work
-
QTS 4.3.5 (beta) and Plex 1.13.5.532: Works without issues (Can access this version by going to Plex Download page and switching off the Plex download button as it is the current public release)
-
QTS 4.3.5 (beta) and Plex 1.13.4.X: Works without issues
1 Like
Thanks @Pyrotech1620 and @ChuckPa, really appreciate it!
Alright… so summary…
If you want to run QTS 4.3.5 you will need to stay on 1.13.5 (or earlier) of PMS. Seems to be the most stable.
As QTS 4.3.5 was just released it is hard to determine if it is a bug in QTS or a bug in PMS. Since PMS 1.13.6 is also beta makes it even harder to find which software is causing the problem. If others can share their experience and details might help narrow the search to monitor the issue better.
1 Like
Adding to what @Pyrotech1620 and I have discussed privately,
It’s not possible to be definitive about what to change, if anything, when QTS is a moving target which just had its network stack overhauled.
For those who have the time and are able to help be targeted in their testing, testing QTS will probably help the most.
1 Like
I’ve installed QTS 4.3.5 beta on my TS-253A and PMS 1.13.6.5339 is working fine. I did not detect any problem. Tested several clients locally (iOS, Android, PlexConnect, Plex/Web), remote connection is up and running, tomorrow will test remote access.
1 Like
It is weird that some people don’t have the issues, while others do. Could this be related to the new Plex feature that allows you to bind PMS to a specific network interface? Just a thought.
Each different QNAP family has a different firmware binary because the hardware is different.
The likelihood of small bugs in how different models are configured exposes different bugs.
It seems those with 1-2 network adapters are largely ok. Those with 4 are less ok.
Let’s continue to see what pattern emerges
Just to help with the trouble shooting with some info.
I have a TS-451 (Dual NIC) and the combination of QNAP 4.3.5 with Plex 1.13.6.5339.
After the upgrade Plex started fine on QNAP with no errors reported, however symptoms are as same as above.
I tried configuring the two nics in various configurations under trunking, active-backup, balance-alb and balance-tlb. with no difference.
- Using static 192.168.xxx.xxx addressing
- IP6 turned on or off also did not have an impact. (both on Qnap and Plex)
- Using internal DNS or external DNS also didn’t have an impact.
Broke the trunking to have to standalone NIC configurations with no difference, meaning server showed as unavailable on each of the addresses.
Downgrading back to Plex 1.13.5.5332 worked with QNAP 4.3.5
1 Like
Just to track a little easier… I will try and keep updated.
Working on 1.13.6.X:
- TS-253A
- TS-651
- TS-653A
Not Working on 1.13.6.x:
- TS-451
- TVS-882
Thanks @Pyrotech1620 interesting that the TS-651 works and the TS-451 does not. I was under the belief that were the same except for the drive bay number. Maybe there is a config difference somewhere that could point to the cause.
To refine the research a blt, can you also list the number of ethernet adapters present, how many are in use, if port trunking is active, and if a Vswitch is in use. This will help identify how many IPs are being presented to the LAN on how many subnets.
e,g. 4x LAN + 802.11ad + v-switch
1 Like
TVS-882
2 IPs
- 3X LAN used in 802.3ad
- 1 LAN used for dedicated v-switch
TS-451 (1.13.5.5332 works / 1.13.6.5339 does not work)
2 x Nic
Port trunking (can change if helps for testing) is active
Single static IP
Balance - alb
No V-switch
Jumbo Frame 9000 (tried standard with no difference)
LAN is flat with only one subnet
So sorry on my part. WOuld you please go back and edit your replies to include which version(s) of Plex work in that config and which don’t ?
It will make it easy to cherry-pick info without having to reassemble by hand
Hi @ChuckPa
Done see above.
I have tried just about every config I can with QNAP network to see if I get a different result. The best I get is when I break the trunking and set the default gateway nic manually to fixed then failure over from Nic 1 to Nic 2. The server appears on the network for approx 3 -5 seconds then becomes unavailable.
Edit - Sorry just a bit more info I cannot connect with Orca’s, the android or web client. I needed to install the working version of Plex and then stop and restart to get working so did this between each test in troubleshooting with no luck.
Looking at the changelog between the two versions, doesn’t seem to be much changed on the PLEX side (Plex Media Server). Understanding that QNAP has had a lot of changes in this release. My experience is per @Pyrotech1620 above in post 25. Seems only the latest QNAP beta and PLEX version do not play well together but other combinations seem to work fine.
I was running 1.13.6.5339 (on TVS-1282 running 4.3.5) and it was working. But as I didn’t want to risk it I went back to a different one most are mentioning.
FYI - I am running 1.13.5.5291 - and no issues!
