The server ... does not allow secure connections

Server Version#: 1.13.9.5456
QNAP 673
i have not been able to get a green remote gtg for several weeks. today i followed the suggestions of

  1. turn on upnp in the router, (since the beginning it was port fwd setting) verify it is working by looking at the plex connection
  2. locally log out of the cloud (then it shows unclaimed)
    log out of the plex.tv
    log out of the local
    turn off local PMS
    restart local pms
    log into local pms
    reclaim server address
    log into plex.tv

the local pms shows green status
but remote clients, and the plex.tv pop up with the does not allow secure connections.

if i enable one time non secure, it works.
what am i missing?Plex Media Server.log (287.0 KB)

and in this log i see a
HTTP 401 response from GET https://plex.tv/media/providers?X-Plex-Token=

probably related to why i can not get a secure connections. thoughts?

BTW, this log is post restart of the PMS to allow a clean log…

Did you disable the security setting?

Edit - To be clear, you want that on preferred or required if you want to have a secured connection.

hello,
it is on preferred.

Ok, thanks. I’m seeing an error in your log. We need to investigate on our end. I’ll update when I hear anything.

A couple of us have exactly the same problem , losing lock sign, can’t use https with same error message as the title of this post.
It’s weird that we all suddenly have the same problem at the same timing which is from yesterday and today impactibg multiple OS.

Elan here kindly responded that no known issue…

We think we may have identified a problem on our back end. It wasn’t known at the time he wrote that.

Hah. I see he’s updated his statement.

here is some log from the plex.tv login session.

"type": "log:message",
"level": 1,
"message": "[Connections] Aborting connection test for NAS0DE9E0 at http://10.1.2.65:32400/media/providers due to mixed content prevention",
"time": "2018-11-07T20:50:39.957Z"

},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] Aborting connection test for NAS0DE9E0 at http://5xxx7:14497/media/providers due to mixed content prevention”,
“time”: “2018-11-07T20:50:39.958Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] All connections to NAS0DE9E0 failed”,
“time”: “2018-11-07T20:50:40.929Z”
},
{
“type”: “log:message”,
“level”: 4,
“message”: “[Servers] Found all servers = plex.tv”,
“time”: “2018-11-07T20:50:40.930Z”
},
{
“type”: “log:message”,
“level”: 1,
“message”: “[Connections] All connections to NAS0DE9E0 failed”,
“time”: “2018-11-07T20:50:40.936Z”

Yeah, we’re working on it, sorry for the trouble!

That’s expected when you can’t create a secured connection. We think we’ve found an issue and will get this fixed as soon as possible.

In the meantime, if you need to use Plex Web, try setting the connection type to allow unsecured connections.

yup, insecure works fine. trying to minimize clear text information on the net.

glad you have a direction.

will wait for your solution. thanks

Ok, a fix has been made on our back end. Restart PMS and try again. This may take some time to propagate so if you still don’t get a certificate, try again a little later.

yahaaaa!! it works. thank you.

i am good-to-go. :slight_smile:

Hi Since the new update I am having the same problem. Cannot access remotely. Any updates?

For me it turned out to be a plex back-end cloud problem which they fixed and that has resolved my remote access issues.

Pete

Thanks Peter, I ended up uninstalling the current version PlexMediaServer_1.14.0.5465-425e4ac90_x86_64 and reinstalling the previous version PlexMediaServer_1.13.9.5456-ecd600442_x86_64.
It immediately fixed the problem. Not the ideal solution for some I know…but at least it works

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.