Server Version#: 1.29.1.1974
Player Version#: 4.54.4
Hey there,
Since a few days the plex webapp has been refusing to connect to my server (runnning on a Synology NAS) with the message ‘app.plex.tv is unable to connect to XXXXX securely’. The secure connection setting is set on ‘Preferred’ (as it was since the beginning). It just stopped working.
It prompts me to try the windows version, which I did, and indeed the windows version connects flawlessly to my server. Any idea what is happening there on the web version?
Thanks!
Thanks, I’ll try to create the bond then. Is there any potential impact on the data/other NAS configuration that I should be aware of? I would not think so as it is network related but better safe than sorry.
Thank you very much again for all your help.
Same problem with secure connections with using plex.tv/desktop seems like a known issue after upgrading to DSM7. Not sure if Plex Developers are actively working on a fix or not.
I experienced the issue today on my NAS. I stopped the Plex service and restarted the service. That fixed the problem. I’m sure it’s temporary and assume an updated Plex package will solve it.
I’ve read through the posts here, and realized the topic is regarding Synology servers - I have a WD PR4100. Before I try these fixes, does the steps hold true to Western Digital servers?
Facing the same issue after update to DSM 7, I am using a bond, tried all the steps as mentioned. Attached are the logs for your reference. Kindly help Logs.zip (5.1 MB)
Same issue here, albeit my server is on windows. I tried resetting to no avail.
Interestingly, i can still access my library via Roku or Android app, just not via browser.
I’m having the same issue. I’m running PMS on an ubuntu server. I can access content through apps; but I get secure connection issues when trying through browser.
I have the same with my Nvidia shield tv, just did an update and the server is unreachable from outside with the error app.plex.tv is unable to connect to “******” securely, hope plex soon coming with a bug fix???