Secure Connections broken since latest Plex Web update

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@master:$ nslookup 192-168-0-10.aaaaaaaabbbbbbbbccccccccdddddddd.plex.direct 8.8.8.8
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@master:$ nslookup 1-2-3-4.aaaaaaaabbbbbbbbccccccccdddddddd.plex.direct
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   1-2-3-4.aaaaaaaabbbbbbbbccccccccdddddddd.plex.direct
Address: 1.2.3.4

froberg@master:$ nslookup 1-2-3-4.aaaaaaaabbbbbbbbccccccccdddddddd.plex.direct 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   1-2-3-4.aaaaaaaabbbbbbbbccccccccdddddddd.plex.direct
Address: 1.2.3.4

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 problem. They combined my ticket with the leasweb one. So fingers crossed.

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

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.

Hi, I also want to confirm that the fix solves the secure connection issue. Thank you very much for investigating and fixing the issue. I was following this topic, but my skills aren’t that good to contribute.

Excellent! Thank you all for reporting back.
Wiiitt and I had fun last night thrashing that one around until we got it down to a simple case I replicate anywhere (which I did) and then got in contact with the guys in charge of that stuff (who had it fixed in a couple hours). Thanks to wiiitt for sticking to it.

Seems to work again! Great job! Thanks!

Now working! Great job!

@ChuckPa said:
Excellent! Thank you all for reporting back.
Wiiitt and I had fun last night thrashing that one around until we got it down to a simple case I replicate anywhere (which I did) and then got in contact with the guys in charge of that stuff (who had it fixed in a couple hours). Thanks to wiiitt for sticking to it.

Ah the long nights troubleshooting… somehow I envy you… Great work and thanks to you both. Just in time for my kids holiday and now he can watch movies from home again remote, you made me dad of the week again thanks!

@Kaoh said:

@ChuckPa said:
Excellent! Thank you all for reporting back.
Wiiitt and I had fun last night thrashing that one around until we got it down to a simple case I replicate anywhere (which I did) and then got in contact with the guys in charge of that stuff (who had it fixed in a couple hours). Thanks to wiiitt for sticking to it.

Ah the long nights troubleshooting… somehow I envy you… Great work and thanks to you both. Just in time for my kids holiday and now he can watch movies from home again remote, you made me dad of the week again thanks!

I’ve got some other software you can help with if you like LOL. I spent 14+ hours over the weekend alone on it and another 12+ since.

Looks like I can access via https again, cheers guys :slight_smile:

This fix resolved my issue. Thank you!!

I can confirm this issue is fixed for my users as well. Thanks @ChuckPa and @wiiittttt for troubleshooting this!