I just got a NAS for Christmas and decided to migrate my plex library to it.
It’s a synology DS218+.
After I got everything setup I decided to add Plex. To my horror it gave me the dreaded:
“Secure Connection Failed”
After some googling and tracking the instal locations down I could see Plex itself appeared to be functioning correctly, so I kept looking.
Eventually I thought it was a firewall issue, but I added all the ports and still nothing, the address I use is: https://192.168.1.161:32400/web/
Note: When I type the above but use http:// it redirects to https:// (even if I disable https redirection - this is essentially the crux of my problem).
I’ve tried multiple re-instalations. Wiping everything and starting from scratch, to no end.
The ONLY thing that got it working for me was to add a reverse proxy via:
Control Panel -> Application Portal -> Reverse Proxy.
From source https * 32402 to destination http localhost 32400.
This works when using https://192.168.1.161:32402/web/
But why!!!
I notice by using the above work around that if I access Plex using the following link, connect to the computer by selecting “Allow Always” I get stuck in a repeated http(s) redirection loop: https://app.plex.tv/desktop?secure=1
This changes the address to the following, which makes sense (and the only way to prevent the constant redirect is to change the secure parameter to 1): https://app.plex.tv/desktop?secure=0
Any help to get this working “out of the box” without the above hack would be appreciated.
P.s - I have also posted this to Synology as I do not believe this to be a Plex issue, unless someone can prove me otherwise.
Synology Software: DSM 6.2.1-23824 Update 2
Plex Media Server: 1.13.4.5271-200287a06
I agree with you this isn’t a Plex issue. Synology’s “redirect to https” option, although off by default, is the crux of the matter. It is far to easy to make DSM too ‘tight’ to run anything but DSM on it.
What are the obvious causes for this? Please do teach me to suck eggs to make sure I’ve not missed anything blatant.
As I mention I’ve disabled http https redirect and started from scratch multiple times.
I’ve even gone down the route of edditing the /etc/synoinfo.conf and added redirectHTTPS=“no” - all to no avail.
To anyone who falls into the solitary pit of dispair…
This eventually got resolved but wouldn’t have been possible without using the above hack to access the Plex UI, as the Synology was redirecting the http request to https regardless of my settings.
In whole I had to:
Using Synology Application Portal -> Reverse Proxy:
Create a rule to proxy Source https port 32402 to Destination http 32400 (as https 32400 clearly wasn’t working on its own by default). This allowed me to access plex on the local http port using https 32402.
I then disabled Plex “Secure connections” under Plex Settings -> Server -> Network.
Finally I had to then re-enable this to “Preferred”. I didn’t think to re-enable this after all of the different things I tried. After re-enabling it then allowed me access via the Synology on 32400.
Finally I could change this to required (and it didn’t prevent my reverse proxy rule should it break again in the future. I’ll disable it anyway with the warm fuzzy feeling I can bypass 32400 natively if it breaks again).
Thanks Chuck for your help - I think this is a grey area as it’s a combination of Synology and Plex security settings and it certainly didn’t work out of the box for me for what ever reason.
My ONLY caution: use of a proxy is, unless you are really careful, dangerous.
A proxy is a deliberate MITM (Man In The Middle) configruation. As such, Neither your PMS nor you know if truly end-to-end secure. Your server might be hanging out wide open and unsecure without PMS able to detect it.
We went to great lengths to remove “disableRemoteSecurity” when it last surfaced. All that code was removed for a reson. Now people use proxies and make themselves 10x more vulnerable.
If anyone gets compromised, “It’s not Plex’s fault, Sorry”. and I really don’t like to use that answer
