0

SSL Error

Hello,

Since today, we encounter a lot of problems with your SSL certificate (end 29/11/2022).

Can you update this certificate asap please?

Thx

9 replies

null
    • NextDNs
    • 2 yrs ago
    • Reported - view

    Which certificate are you talking about?

      • NextDNs
      • 2 yrs ago
      • Official response
      • Reported - view

      infopy you where probably affected by this problem: https://help.nextdns.io/t/m1hs207/energized-ultimate-lists-blocking-nextdns

      What you were seeing is the blockpage certificate. You probably enabled the blockpage feature without trusting the associate CA root certificate. Our certs for blockpage are very short lived (as part of the security measures to protect this dangerous certificate). More info on https://help.nextdns.io/t/g9hmv0a/how-to-install-and-trust-nextdns-root-ca

      • infopy
      • 2 yrs ago
      • Reported - view

      NextDNS The https certificate of nextdns.io . For exemple, this morning, all my clients were unable to connect to internet. All websites were unaccessible. After some research, i've found that the SSL certificate of nextdns.io was near to end. All websites were alternatively available, then blocked, and accessible again. The website my.nextdns.io was also down during this time.

      • Emanuel
      • 2 yrs ago
      • Reported - view

      infopy For me it says: Let's Encrypt,

      Validity:

      Not Before Mon, 10 Oct 2022 20:16:03 GMT,

      Not After Sun, 08 Jan 2023 20:16:02 GMT,

      • infopy
      • 2 yrs ago
      • Reported - view

      Emanuel This morning, the ending date was Not After 29 November 2022

      • Emanuel
      • 2 yrs ago
      • Reported - view

      infopy You're saying they fixed it by the time I looked? It's possible, but kinda odd that the start date is on 10 Oct, wouldn't it be on 29 Nov ? unless maybe something else was going on, only for you? like, you were using a proxy or VPN and/or your connection was intercepted/MITM ? just guessing. Or I'm wrong and it's something else entirely. (like a localized nextdns https server and you're likely still seeing the issue unless they fixed it since then)

      • infopy
      • 2 yrs ago
      • Reported - view

      Emanuel All my impacted clients are using Eset Endpoint Security, including me, maybe it was a problem with the Eset proxy ... i don't know.

    • Craig
    • 2 yrs ago
    • Reported - view

    I had the same issue. Any https request came back with the NextDNS block page certificate. This effected getting to all secured websites including NextDNS.

    Have resorted to bypassing NextDNS.

      • infopy
      • 1 yr ago
      • Reported - view

      Craig Thank you for your comment. I thought i was the only one who had this problem ... I had to bypass Nextdns with another dns provider too. I'll wait a week before rolling back

Login to reply

Content aside

  • 1 yr agoLast active
  • 9Replies
  • 407Views
  • 4 Following