Went to PMS 1.18.2.2029-36236cc4c on my QTS 4.4.1.1117 system (a TS-651) and everything is working fine.
So I did the same upgrade I did on my TS-651 again, this time on my TS-251+. QTS 4.4.1.1117, installing the QPKG for PMS 1.18.2.2029. Can’t connect to the PMS there. ssh’ed into it and turns out there are still the 1.18.1.1973 binaries running. Stopping the QPKG for PMS in the App Center didn’t do anything to those processes. Had to kill -9 all of them and when I restarted the PMS QPKG I could connect to the Media Server again. Looks like the install of the QPKG wasn’t clean in stopping the old binaries.
HTH,
Alex
Alex,
Thanks. I will take that to QNAP in our next convo.
what command tell you this and how did you kill them?
Shows you the list
ps -ef | grep -i plex
Now kill the processes (left most column number)
kill -9 process_number1 process_number2 (can add them all here)
(example: kill -9 34511 34513 334555 )
If kill -9 doesn’t clear it, kill -11 is even more forceful.
thanks, @ChuckPa!
kill -9 was enough while a normal kill wasn’t.
OK, my TS-543Bmini is back on 4.3.6.1070.
I only have PMS v 1.18.2.2029 processes running.
Everything looks good so far, however I seem to remember Plex working initially when I last updated. The sequence was different though. The first time was upgrade QNAP then Plex. This time it was (essentially) upgrade Plex then QNAP (because I downgraded and then upgraded QNAP again) so maybe my initial problem was also having older Plex processes running (which got killed anyway during downgrade/upgrade)
J.
[edit] updated QNAP to 4.11.117 yesterday and Plex is still running fine today. Note that I have a TS-453Bmini which shows this rev as being released (not beta). I think my problem occurred when updating Plex, not updating QNAP.
Thanks cresjes, changing https off did the trick for me. Sooooo glad I don’t have to factory reset the unit now to solve the issue.
By the way I’m running QTS 4.4.1.1117 and PlexMediaServer-1.18.2.2015-5a99a9a46-x86_64.qpkg
Anyone have any idea why HTTPS access suddenly stops working like that on PMS GUI? For me it’s fine, now that I’ve factory reset and I’m having to go through all the work again… But for many people this will cause them to think their install is hosed and end up going down my path. For that matter, PMS GUI wouldn’t work on HTTPS until I forced it to only secure connection. If I used “preferred” secure connection option it didn’t work on HTTPS.
Well, my results are pretty devastating too.
After updating to .1117 i had to notice that:
random CRASHES of the qnap (qts) itself. Average count right now is something about 4-6 crashes - PER DAY!
4.4.1 did screw the default gateway up. i have MANUALLY set the automatic to nonworking VPN gateways, set it back to automatic. THEN the ■■■■■■ QTS does realize that my bridge interface has REALLY a default gateway which it could used in the first place. m)
QTS bugs like missing the final softreset at and of the shutdown process i usually dont mention anymore. Also i dont mention anymore the lack of technical proper documentation. QTS does not even provide detailed logs for bug or “event” hunting. 
currently i still dont know what is EXACTLY causing the crashes. But one thing is for sure: IT DID NOT HAPPEN PRIOR TO .1117.
IF it is some kind of combination XXXXXX (qts .1117 and PLEX) i dont know. But even if PLEX is pretty baaaaaaaaaaaaad coded, a stable operating system shall NEVER crash because of ONE not-system-critical-media-application. NEVER!
MODERATOR EDITED: Language
8 days ago, I warned of QTS 4.4.1.
I presented a stable version to stay with.
Why is everyone still upgrading to it?
Please don’t flame if upgrading to QTS, by choice, caused problems.
Please keep the language under control.
I think there is a portion of users who never had a problem with firmware upgrades and Plex before and are now being bitten. Absent forums like this, there is no indication of 4.4.1 being a problem on QNAP’s site. I had grown to feel pretty safe about applying firmware updates over the years. I’ve been doing it since QTS 4.1 and never had these things happen. I’m not defending the post, nor the language, only that it’s still happening because people are not proactively checking this forum before upgrading. They see the notice from the NAS and upgrade, as they are taught to do, generally to plug security holes.
My takeaway from this experience is to wait a couple of weeks and ensure no issues crop up in this forum before I update, but that’s hindsight. If QNAP considers 4.1 to be beta, it should be labeled as such on the website and all current 4.1 installs should not prompt for firmware update until the next stable GA patch (unless of course they have beta versions turned on). That would stem the bleeding.
Lastly, @ChuckPa, last week you spoke of some code in hand to assist with automatically copying Plex directly to a PlexData share but I still can’t find the actual .qpkg. I’m willing to back up my stuff manually and be a tester or to help resurrect the linked thread to get that done. Otherwise I can probably use a bash script and crontab to just periodically copy that directly myself. I’d love to test a solution that could see some distribution though. Please let me know if that qpkg can be made available. Appreciate all the hard work. Cheers!
I thought we concluded that it was beta for some QNAPs, but released for others.
It is true, I do have the new QNAP packaging in hand and ready for release.
What I cannot disclose is the list of other things in flight.
I can tell you, from the packaging perspective:
- QNAP - redesign
- Debian packaging - overhaul
- Redhat packaging - overhaul
- Other NAS vendors’ packaging. - updated
At this time, QNAP is the “odd man out” because the metadata is not stored separate form the executable code.
Synology is the first, and long standing, packaging architecture which deeps program and data separate.
When I can create the QNAP Forum Preview, and have the completely clear/free time to dedicate to it, I will. The big problem is managing my time.
I’m sure you’ve all seen TheTVDB issues of this week as but one example.
Let’s not digress from the topic of this thread any further please.
Or as free people call it: censorship.
MODERATOR COMMENT
Or as Plex calls it on our forum:
Exactly. 4.4.1 is “stable” e.g. for TVS-873.
So, 4.4.1 and its special attitude is not new, but 1117 is far from being stable. In fact its unstable and the QA of QNAP has to ask itself if they know what they are doing. That BS they do lately is far from being professional and would usually lead to personal consequences like being fired or demoted within the company.
We dont talk about “cosmetic” problems. We are talking about serious stability issues which actually can even lead to dataloss or expensive maintainance time.
However, im curious: Did PLEX or QNAP ever announce why QNAP has banned PLEX from all its devices?
1 Like
What do you mean?
Hello,
I am trying to run Plex Media Server 1.18.2 on a QNAP TVS-473e with firmware QTS 4.4.1.1117
I can reach the webserver at http://nas-ip:32400/ (with HTTPS it does not work) but I can’t access my server.
This is in the log:
Nov 23, 2019 01:10:37.719 [0x7fccbbfff700] DEBUG - EventSource: Stopping.
Nov 23, 2019 01:10:37.720 [0x7fccbbfff700] DEBUG - PubsubServerManager: Switching to next host in region: 172.104.145.70
Nov 23, 2019 01:10:37.721 [0x7fccbbfff700] DEBUG - EventSource: Stopping.
Nov 23, 2019 01:10:37.721 [0x7fccbbfff700] DEBUG - EventSource: Resolving 172.104.145.70 port 443
Nov 23, 2019 01:10:37.721 [0x7fccc042f700] DEBUG - EventSource: Resolved 172.104.145.70 to 172.104.145.70
Nov 23, 2019 01:10:37.794 [0x7fcbf7ea3700] DEBUG - HTTP 401 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=59afa7a9-11f7-4cbf-b291-516c0cb31e31
Nov 23, 2019 01:10:37.794 [0x7fcbf7ea3700] DEBUG - MyPlex: Published Mapping State response was 401
Nov 23, 2019 01:10:37.795 [0x7fcbf7ea3700] WARN - MyPlex: Invalid response when mapping state (code=401): <?xml version="1.0" encoding="UTF-8"?>
<errors>
<error>Invalid authentication token.</error>
</errors>
Nov 23, 2019 01:10:37.798 [0x7fcbfff8b700] DEBUG - MyPlex: Sending Server Info to myPlex (user=heiner@bunjes.net, ip=, port=0)
Nov 23, 2019 01:10:37.798 [0x7fcbfff8b700] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=ab171e8c-dd19-4477-8905-da18fbcf57d1
Nov 23, 2019 01:10:37.813 [0x7fccc042f700] DEBUG - EventSource: Connected in 63 ms.
Nov 23, 2019 01:10:37.813 [0x7fccc042f700] DEBUG - EventSource: Wrote data, reading reply.
Nov 23, 2019 01:10:37.958 [0x7fccbbfff700] DEBUG - EventSource: Read HTTP reply header.
Nov 23, 2019 01:10:37.958 [0x7fccbbfff700] DEBUG - EventSource: Failure in ParseHeader: HTTP/1.1 403 Forbidden
Server: nginx
Date: Sat, 23 Nov 2019 00:10:38 GMT
Content-Type: text/html
Content-Length: 162
Connection: close
<html>
<head><title>403 Forbidden</title></head>
<body bgcolor="white">
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>
(0 - Success).
Nov 23, 2019 01:10:37.958 [0x7fccbbfff700] ERROR - EventSource: Retrying in 15 seconds.
Nov 23, 2019 01:10:38.031 [0x7fcbfff8b700] DEBUG - HTTP 401 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=ab171e8c-dd19-4477-8905-da18fbcf57d1
Nov 23, 2019 01:10:38.032 [0x7fcbfff8b700] DEBUG - MyPlex: Published Mapping State response was 401
Nov 23, 2019 01:10:38.032 [0x7fcbfff8b700] WARN - MyPlex: Invalid response when mapping state (code=401): <?xml version="1.0" encoding="UTF-8"?>
<errors>
<error>Invalid authentication token.</error>
</errors>
Nov 23, 2019 01:10:38.036 [0x7fcc00855700] DEBUG - MyPlex: Sending Server Info to myPlex (user=heiner@bunjes.net, ip=, port=0)
Nov 23, 2019 01:10:38.036 [0x7fcc00855700] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=5f7f8668-122d-4f83-9f7e-71750a2d6709
Nov 23, 2019 01:10:38.272 [0x7fcc00855700] DEBUG - HTTP 401 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=5f7f8668-122d-4f83-9f7e-71750a2d6709
Nov 23, 2019 01:10:38.272 [0x7fcc00855700] DEBUG - MyPlex: Published Mapping State response was 401
Nov 23, 2019 01:10:38.272 [0x7fcc00855700] WARN - MyPlex: Invalid response when mapping state (code=401): <?xml version="1.0" encoding="UTF-8"?>
<errors>
<error>Invalid authentication token.</error>
</errors>
Nov 23, 2019 01:10:38.276 [0x7fcc1b159700] DEBUG - MyPlex: Sending Server Info to myPlex (user=heiner@bunjes.net, ip=, port=0)
Nov 23, 2019 01:10:38.276 [0x7fcc1b159700] DEBUG - HTTP requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=067dae76-834b-49ab-b733-1a86814ded6f
Nov 23, 2019 01:10:38.501 [0x7fcc1b159700] DEBUG - HTTP 401 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=067dae76-834b-49ab-b733-1a86814ded6f
Nov 23, 2019 01:10:38.502 [0x7fcc1b159700] DEBUG - MyPlex: Published Mapping State response was 401
Nov 23, 2019 01:10:38.502 [0x7fcc1b159700] WARN - MyPlex: Invalid response when mapping state (code=401): <?xml version="1.0" encoding="UTF-8"?>
Is this the same problem this topic is about or is there anything I can do?
Thanks in advance!
I had issues updating Plex to 1.18.2.2058 on firmware 4.4.1.1101. Thank you for the firmware warning to go to 1117. Think I’ll hold off. I’m currently at Plex PlexMediaServer-1.18.2.2058-e67a4e892-x86_64.qpkg and Plex seems to work occasionally.
