Server Version#:1.43.0.10467
Player Version#:
There is no new Beta Server 1.43.0.10467 for QNAP to download!
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Thanks for sharing.
Not sure if this might be linked to the updates to the built-system mentioned in the release notes.
Thanks for the quick response. I’ll wait and see.
I’ve learned that this particular beta release had been skipped for QNAP due to some dependency.
Hence, the answer to your OP is indeed… yes, no media server 1.43.0.10467 beta for QNAP-users.
I have updated the release post, however QNAP builds are unavailable at this time.
Any news about the work on progress for Qnap update?
Thanks to @ChuckPa
And pushed that beta to production without solving the bug in their new build and deploy system first. So first production release for PMS since July - but fumbled it for QNAP users outta the gate. Not a good look. Hopefully gets sorted soonish.
I can say that, at least personally, the beta version v.1.43.0.10389 (one version back) that is available for QNAP has been fine for me (outside of a few known bugs waiting for fixes).
Some additional details about the releases here: Where's the next PLEX version? - #32 by ChuckPa
Edit: and now it’s pulled entirely for additional issues with the build\deploy… hopefully it’ll get sorted soonish even with reduced manpower.
Is there any update for QNAP-Users? Is there going to be a release after the build-rehaul?
Yes 
Well, QNAP is indeed a different beast, and has a way of signing their QPKG’s that is completely different from all other vendors!
So it is expected, and will be resolved by Plex as soon as posible!
Granted, they could have released unsigned QPKG’s, but that would req. tech-notes and additional forum threads on how to procede then, not to mention their partnership with QNAP would be affected when releasing unsigned QPKG’s
So from a Plex perspective, they did the right thing IMHO by releasing to as many platforms as they currently can, and then will catch-up on the remaining ASAP
We don’t actually know it was a signing issue do we? Just that there was an issue with the new build platform that prevented a QNAP package being released and they had no idea when one would be forthcoming.
Considering they’ve pulled the release for issues with other platforms too, I think it’s hard to defend it as anything but fumbled.
Couple that with the layoffs that happened at the same time, it’s not great for instilling confidence in the PMS product.
The longer it takes to fix, the more I assume Claude flaked out and the remaining devs are scrambling to figure out how to reverse engineer it… 
It probably wouldn’t be as big a deal if it hadn’t been so long since a public release. Plex chose to put off fixes for known issues and regressions for several months now in favor of the new transcoder - which made a certain sense as a decision (arguably). But then they rushed the public release of the last beta using a new build\deploy tool - after promoting user patience to get a quality release. Very contradictory and conflicting in multiple ways.
I’m sure it’ll get sorted eventually but Plex is hurting their already flagging reputation.
couldn’t agree more 
Hey Plex support… any news/estimates on the Qnap release?
What’s the issue with the Qnap builds? Some real information would be awesome
Earlier it was mentioned there was a missing dependency.
I’m sure tom80H was trying to share what info they could when they mentioned it so nothing against them for sharing that info, but the reason itself kinda rings hollow after this much time and how other issues with the release (RHEL\DEB) got discussed with transparency and quick workaround fixes in an active pinned topic thread.
Additionally telling considering what should have included a testing period of the new build platform before switching to production that they somehow missed that it wouldn’t build a QNAP package; or they knew and seriously dropped the ball on communicating the situation effectively which isn’t good either.
Overall it’s not a huge deal to me really. The latest beta that is available is an option for Plex Pass users on QNAP and addresses most of the known bugs and features contained in the current production release and has felt stable for me for several weeks now.
Unfortunately, the overall handling of the situation indicates a drop in service\product\brand quality. Just disappointing from a long time user standpoint.
ChuckPa has mentioned more specifics about the QNAP release issue in a different topic: QTS and Plex Update Advice - #6 by ChuckPa
Still no estimate - even as a known issue from before they chose to do a public release without QNAP - but I’m guessing they counted how many QNAP users are around and decided it wasn’t a concern (and not like lots of folks are screaming about it). As mentioned previously, it’s not really a big deal functionally, particularly for Plex Pass users who can grab newer betas, but it still feels icky. Very “fight club recall”. 
As I started to mention here: No Media Server 1.43.0.10467 Beta for QNAP-User? - #10 by dane22 and now also mentioned here: https://forums.plex.tv/t/qts-and-plex-update-advice/936312/6 by @ChuckPa this is indeed caused by QNAP been so different than other vendors when it comes to signing!
When said, as long as there’s no security fixes in newer releases, then QNAP users are safe, but yes, might for some time miss previews, beta’s as well as fixes
Rest assure that Plex is doing everything they can to make sure that QNAP builds are produced as far as possible!
And before doubting me again @Insomnic_1 then note that I’m a former Plex employee, and knows QNAP in details!
I know you are former employee and that you wrote up most of the QNAP FAQs (which I pointed out in that other thread that you did a great job creating and keeping up to date)… so I don’t doubt you or your facts.
But the crux of my intent was that it didn’t really matter if it was true or not because it doesn’t change Plex’s decision and planning mishandling. It might be the reason but it’s not really an excuse. This isn’t a surprise situation with QNAP and if it was that’d be a mishandling too. You said it yourself though that this is a known thing about working with QNAP builds. So the fact that Plex dropped the ball and went with a release without a QNAP build is bad planning\coordination on their part. That was mostly what I was trying to get at there.
And when it didn’t get a release, the response was kinda poor too.
What ChuckPa said, and what you said, coulda been said from the start instead of the statements given being evasive and only saying Plex has no idea when a release will be ready so tough luck QNAP users who’ve been waiting for fixes for 6 months (not everyone has access to or wants to touch beta builds).
And nobody has owned up to it at all. It’s not that hard to say “we flubbed it ,but we’re working on getting it sorted out ASAP, sorry for leaving QNAP folks behind but we’ll catch it up, please be patient while we work on it”. It’s still mostly just saying nothing or that it’s QNAPs fault - somehow, because they’re doing what they’ve always been doing?
That’s what looks bad and lowers confidence. That’s what comes across as dismissive to customers\users.
Honestly it’s not a huge deal overall and not missing much by grabbing the last available beta build which has been solid. I think I’ve said it regularly that this is mostly just observational from me, not really upset or anything. Just, for me and likely others, another icky thing in what feels like a string of icky things. And we’d like to see Plex do better in this area. From my perspective it’s not hard or even more effort really… it’s just some extra words. BUT the lack of those words can be seen as an inherent lack of consideration. I’ve had this conversation so many times with IT service managers as part of my work it’s kinda automatic so… that’s what a lot of it is.
You and ChuckPa and tom80H are trying your best to help where you can and I, and others, appreciate it.
So, what now?^^
