SSL inconsistency: 99.83.190.102 fails TLS while 75.2.60.5 passes (ERR_SSL_PROTOCOL_ERROR)

Support
1

Hello Netlify team,

I’m experiencing an SSL issue with my custom domain.

Site name: valleyexports.netlify.app
Custom domain: valleyexports.com

My DNS is configured as recommended:

  • A → 75.2.60.5
  • A → 99.83.190.102
  • CNAME www → valleyexports.netlify.app

Netlify shows a valid Let’s Encrypt certificate for both valleyexports.com and www.valleyexports.com.

However, HTTPS is inconsistent:

  • The site loads securely in Chrome Guest Profile and desktop browsers.
  • Some Android browsers, especially the Instagram in-app browser, return ERR_SSL_PROTOCOL_ERROR.
  • HTTPS works for some users but fails for others.

I’ve already tried:

  • Waiting more than 24 hours for DNS propagation.
  • Verifying the DNS records.
  • Renewing the certificate from Netlify (it reports DNS verification failed even though the domain is resolving to Netlify).
  • Testing from different browsers and devices.

SSL Labs consistently reports:

  • 75.2.60.5 → A+

  • 99.83.190.102 → Failed to communicate with the secure server
    I ran an SSL Labs test and consistently get:

    • 75.2.60.5 → A+ (HTTPS works)
    • 99.83.190.102 (aacb0a264e514dd48.awsglobalaccelerator.com) → Failed to communicate with the secure server

    Because DNS points to both IPs, I suspect some users are reaching the working endpoint while others are reaching the failing endpoint.

Could someone please verify whether the SSL certificate has been correctly deployed across all Netlify edge servers for my custom domain or whether there is an issue with one of the endpoints?

Thank you!

2

Additional information from testing:

I tested both the Netlify subdomain and my custom domain.

  • https://valleyexports.netlify.app loads correctly in Microsoft Edge and Chrome.
  • https://valleyexports.com returns ERR_SSL_PROTOCOL_ERROR in Microsoft Edge and Instagram’s in-app browser.
  • Chrome Guest Profile can load https://valleyexports.com, so the issue appears to be client-dependent and specific to the custom domain rather than the deployment itself.

This seems to indicate the deployment is healthy and the issue is isolated to the custom domain’s SSL/TLS handling.