Ever since Plex updated to the latest Plex Web version secure connections are no longer working for some of my remote users. They are unable to connect from Roku’s and Plex Web via secure connections. I thought maybe it was just the latest update so I downgraded back to 0.9.16.3 but same issue. I…

Yes both fail to resolve giving a non existing domain. While both resolve fine using the 8.8.8.8 dns server. In the forum of KPN I see someone also complaining about the same system not working for his 37-48-67-5.cloud.leaseweb.net domain. So it seems related to the dynamic IP part of the domains.

@sa2000 said: @K_Seymour said: So does that mean its dns rebinding on my router? Is there anything I can do about that? I have a linksys E4200. No - because the public IP also failed with your default DNS Did you enter the actual public IP Address string or the version i put here with xxx-xx…

If you both have the same ISP, before using your DNS settings blindly, give those same tests a quick run. Granted, you’ll probably get the same results but better safe than sorry. Once concluded you have the same issue, make the switch. To answer your question: Since your ISP’s DNS didn’t kno…

The problem is that the nslookup to plex.direct does give results just not to the dynamic part (when the ip is in the dns name) I also notice that your plex.direct domain is not being able to list the a records since they are dynamic. So I think that is the problem, they tried to solve some security…

The results we’re seeing are two-fold. the non-population of the .direct domain by the ISP (hence the no-records error) the rebinding / rebinding-protection with incorrect results being returned. You are correct, switching the server’s DNS only solves one part of the problem. The issue is being…

@ChuckPa said: @Froberg said: I am experiencing the issue as well… can’t access web-app securely, insecure works fine. My local devices have no issue, nor do remote users. What results do you get with the DNS queries as instructed by schuyler? Use Terminal in Linux, Start->Run->Cmd in Win…

And here’s the same from my server; froberg@master:$ nslookup 192-168-0-10.aaaaaaaabbbbbbbbccccccccdddddddd.plex.direct Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: 192-168-0-10.aaaaaaaabbbbbbbbccccccccdddddddd.plex.direct Address: 192.168.0.10 froberg@mast…

Ok, small update. KPN has contacted the other companie that had the same problem (leaseweb) with their dns not working. They are investigating together what is causing the problem. Since the Plex.direct dns is using the same system I can hope that any solution found there will also solve this proble…

First test confirm it seems fixed! Great job. I will resconfigur my router to us my providers DNS again and confirm that it indeed is fully fixed for my DNS.

Secure Connections broken since latest Plex Web update

General Discussions

sa2000 April 26, 2016, 4:16pm 63

A problem with the DNS setup for plex.direct has just been resolved and hopefully will fix some of the issues reported in this topic. See the technical explanation outlined by @wiiittttt here and confirmation of the fix here

Topic		Replies	Views
DNS issue has not been resolved, still cannot connect Remote Access server-windows	45	1598	July 26, 2021
I cannot access my server with a browser but i can with the Plex app Remote Access server-mac , plex-web	270	8815	February 5, 2022
Secure connection not working after last update Remote Access server-linux	148	3687	June 7, 2021
Server unreachable from Plex Web, but fine from "Plex for Mac" Plex Players plex-web	26	268	January 13, 2021
Plex showing indirect connection on local network and no manual access to PMS General Discussions	37	4173	April 19, 2020

Secure Connections broken since latest Plex Web update

Related topics