Hi there. I’ve been using Plex for some time now and even got a Plex Pass Lifetime. Last year (2020) I rehomed and from then I have not used my QNAP Server, (therefor not used Plex) up until now. I had no issues before (except for occasional buffering in my home network).
Last week I started the QNAP (model TS-470) up, updated all the apps and QTS version, etc.
I downloaded ver.1.22.0.4163 (QPKG file) and installed it manually to the QNAP.
I noticed that the QNAP version (1.16.6) also shows as installed, even after I removed it completely. But if I click to open ver.1.22.0.4163 I get the following information message: “Secure connections (https://) are not supported for this application. Are you sure you want to open it?”
If I select No, nothing happens. If I select Yes a new tab opens to this address: “http://192.168.101.197:32400/web” with the following message: " Not Found - The requested URL was not found on this server.", including a “Not Secure” site information indicator in Chrome browser.
I checked that the Web Server is enabled, Secure Connection is enabled, and ever enabled Force secure connection only. After enabling force I try open (https://192.168.101.197/cgi-bin/) but still nada/nothing.
I searched again online (Google, QNAP and Plex Forum) but for the last couple days I have been unable to fix this issue, with every possible solution I found.
I’m now at a point where I do not know what to do anymore.
here’s the System-Log file for you to check. system-log.txt (5.7 KB)
You know what really grinds my gears is that non of the PLEX gurus attends to this issue. Many other issues similar to this was attended to promptly.
I initially sent my issue to plex directly whereby the guy replied by saying he will not answer me directly, I must post it here on the forum. Nice hey…
Then I wonder WHY I PAY FOR PLEX PASS if I get no Customer Service…!!?
Nothing yet. It seems that PLEX has no customer support or they’re just not interested in helping. I really don’t know why I bought a PLEX PASS when plex is now useless to me. I can’t use it and I get absolutely NO SUPPORT!
Coming here to add a ‘me too’ - although here there are two problems.
The URL for PMS should have /web/index.html in order to work
If you have configured Plex to work with SSL, the error message from QNAP is misleading. However it still sends you to a http:// URL instead of https:// which means that it would not work properly anyway.
I can’t figure out how to change the URL that PMS will redirect you to - I assume it’s part of the QPKG metadata…
For me, I just reinstalled my NAS to different drives (figured it needed a refresh) and now Plex is having these problems. Not a killer for me since I use the apps, but if you’re just getting started, try adding /index.html on the end of the URL and you should be able to move forward.
I think the OP has a TS-470 which has a Celeron G550 - a 64-bit CPU.
Maybe the other two guys can chime in with their specs.
For me (Lifetime Plex Pass holder), I have a TS-253Be, freshly factory reset (replacing a dead TS-251 originally installed in 2015). Some point a few years ago, I enabled SSL on the PMS (using the Let’s Encrypt certificate on the NAS), and the link to Plex Web had always worked fine through various upgrades (and no warnings about https).
After factory reset (with 4.5.4.1741), a freshly installed PMS (after restoring the Let’s Encrypt certificate to the NAS) suddenly has this issue. It makes no difference if I install the version of PMS that is available in App Center or if I install the latest one downloaded from plex.tv.
Plex Web works fine, but in order to access it I must add https at the start, and /index.html on the end of the link (http://<nas_name>:32400/web) that QTS provides.
Perhaps I should have installed PMS before I enabled SSL on the NAS? Is there any way I can update the link that QTS shows on the PMS icon?
And another thing. Now that I have fully restored my Plex server (after copying back the Library metadata and configuration, I had to access the server via the IP address and claim the server otherwise Plex Web was empty), it appears I don’t need the / nor /index.html, only to add https at the start.
All I have left is this SSL issue. I have found a file /mnt/HDA_ROOT/.config/qpkg.conf that appears to be the place to change the setting (from Web_Port = 32400 to Web_SSL_Port = 32400 - I guess I just have to restart the NAS to pick up the changes.
OK all fixed. I actually had to add an additional line under the PlexMediaServer section: Web_SSL_Port = 32400
and keep the existing Web_Port = 32400
intact
I wanted to add QPKG_WEB_SSL_PORT and keep it in there by default
I ran into trouble because QTS, in spite of the glued-on certificate, isn’t actually part of the cert’s domain.
As confirmation, would you also please try:
a. With your cert active,
b. ssh command line , type: hostname. It should return the FQDN. In all I’ve done, it will not.
c. Unless I can figure out how to make it always return the FQDN in hostname(), PMS will always fail to accept the cert you give it. PMS checks hostname() and the URL you give it for validity. If the two names don’t match (a simple string comparison) PMS refuses to pin the cert into PMS.
I’ve been spending time with the QTS testing team to get their testing environment such that they actually test our app the way it’s written. The biggest challenge is that their app testing environment puts the NAS-under-Test into a different subnet. They expect the app to be able to startup, be configurable, and operate in such a split environment. PMS doesn’t work that way until after you’ve Claimed it.
To add to that, I’ve been asking / negotiating for some changes to QDK. If they are able to incorporate them, I will be able to add a simplistic GUI through which I can add a “Plex Claim Token” method like I’ve added to Synology. It’s much like Dane22’s “ClaimIt” functionality except my tool would be permanently resident in each QPKG file
I think you’re asking if the URLs can change? Not really. QDK gives me:
# Relative path to web interface.
QPKG_WEBUI="/web"
# Port number for the web interface.
QPKG_WEB_PORT="32400"
PS: My TVS-1282 will be back here on Monday and setup by Tuesday/Wednesday (It will take several days to create the array and load it up fresh – 45TB )
Thanks for the reply. Appreciate my stream of consciousness messages might have been confusing.
In response to your questions:
hostname outputs the hostname of my NAS (which doesn’t match the SSL hostname at all). My setup looks like this:
a) Let’s Encrypt SSL cert with <my_name>.myqnapcloud.com as CN and SAN-DNS
b) DNS entry in my router (OpenWRT) pointing that name to the NAS IP
c) Port forward with NAT reflection enabled (I enabled this as Plex was logging a failure to curl my public IP on startup before I figured out I needed to claim it by logging in via the IP address).
The last one wasn’t there before I factory reset the NAS - uPnP forwarding was sufficient. Not sure if the error was benign because I subsequently figured out that claiming the new server was required. I haven’t bothered to remove the port forward since it’s all working now.
It sounds like from what you are saying that if I tried to setup PMS today with a xxx.myqnapcloud.com SSL cert, it would refuse to accept it. I guess that check in PMS was added after I originally set things up. Just to mention, I had grafted my previous Library and configuration into the new install and things are back as they were - i.e. I can use PMS with all the apps and devices (including web) with SSL and without any cert warnings.
That sounds like quite a challenge. I guess you’d need a pretty beefy test harness set up for it to work in an isolated way as you’ve described.
Is that to perform the claim through the QTS UI when installing PMS? I’ve never used a Synology but friends have them and I am starting to get the occasional bout of envy
Sorry this was the confusing part of my stream of messages. I came to this thread as I had the exact same symptoms as the OP with the 404/Not Found error. I believe this condition only occurs prior to claiming the server, while using a hostname that doesn’t match that of the NAS device (but am not 100% sure), since now that I have got the PMS claimed, it works fine without the trailing slash. Although this doesn’t appear to align with the OP’s issue. Unfortunately now my NAS is set up I don’t want to reset it (and I don’t have a spare). Maybe you can test that if you have one to hand.
YES. Plex will not claim when referenced with a FQDN (Security mechanism for those users who rent VPS/remote host space). When hostname and cert (host+domain) don’t match – It refuses.
it’s quite the challenge. The testing lab exists on multiple subnets and the engineering team is on the office subnets. The fun never stops
Synology has a pretty swoopy UI but, as a fellow QNAP owner, there isn’t a Syno box in existence which can touch what I have in my TVS-1282-i7-64GB
(2x 10GbE, 2x, 1TB SATA-3 (qts) 2TB NVME SSD PCIe (vm storage), 4x 2.5" SATA-3 SSD (development), 8x 12TB WD Enterprise (main array),
the 404 is very likely because it can’t find what is being provided by Plex/web UI. (remember, the Plex/web UI loads from the NAS but gets all its data from Plex.tv so there is that initial disconnect before you claim the server… which is why you and it must be on the same subnet )
I still cannot get connect to my Plex server. I do not understand some of the things that you have done above. First: I have done with Ghost Media Plex did I am using a bit newer 453D by qnap and running firmware 4.5.4.1741. Just like him I get the “secure connections Https:// are not supported…” I have done like dannygoulder has suggested changed the http to "https://myNasIPaddres:32400/web " and I get in safari and chrome “cannot connect to server”
When I launch the Plex app from the App Store it says my server is currently unavailable.
I just don’t know where to go from here. I do have a valid secure certificate I believe. I just purchased one from qnap a bit ago and I log in with https:// when I want to get onto the NAS. I’m really just at a loss of where to go here.
by Tuesday/Wednesday (It will take several days to create the array and load it up fresh – 45TB )
