Custom domain SSL intermittently fails on edge IP 99.83.190.102

Support
1

Hi Netlify team,

My custom domain siraytechnology.com is using Netlify DNS, and HTTPS is already enabled in the dashboard with a valid Let’s Encrypt certificate.

I already renewed the certificate, and it has been over 24 hours, but the SSL issue is still intermittent.

SSL Labs shows:

  • one edge/server is fine
  • another fails with “Failed to communicate with the secure server”

The failing IP is 99.83.190.102.

I can also reproduce this in real use:

  • with a Hong Kong VPN, Chrome shows ERR_SSL_PROTOCOL_ERROR
  • without the VPN, the site loads normally

I found a related forum thread mentioning the same broken edge IP (99.83.190.102), but my case is not the same as the external-DNS configuration issue, because my domain is already using Netlify DNS.

Could someone please check whether there is still an edge-specific TLS/certificate deployment problem affecting siraytechnology.com?

Thanks.

e5c6c5e7045d11e3d96cf2246471e88f
e5c6c5e7045d11e3d96cf2246471e88f1080×2374 96.5 KB

2
4

Hi @hrishikesh,

Thanks — this does look very similar to my case.

For siraytechnology.com, I also observed intermittent TLS/SSL failures, and the failing edge IP reported by SSL Labs was 99.83.190.102, while the other path appeared normal. I could also reproduce it from a Hong Kong VPN with ERR_SSL_PROTOCOL_ERROR.

At the moment, the site appears more stable after removing the problematic path on my side.

Could you please confirm whether siraytechnology.com was affected by the same edge / TLS termination issue on 99.83.190.102?

Also, please let me know:

  1. whether this issue has now been fully fixed for my domain,

  2. whether it is safe to restore the default Netlify DNS/record setup,

  3. or whether you recommend keeping the apex pointed only to the stable path for now.

Thanks

5

Did you read the solution posted in the thread? There’s no edge/TLS termination issue as the IP you’re using is not a Netlify IP.