Support / SSL and Domains

Support
1

Bonjour l’équipe Netlify :waving_hand:

J’ai récemment supprimé puis réajouté mon domaine personnalisé nadia-ruello.com (géré via Netlify DNS) et j’ai reprovisionné le certificat Let’s Encrypt.

Tout fonctionne correctement pour le domaine et pour l’adresse IP 75.2.60.5, mais l’autre IP Netlify 99.83.190.102 échoue toujours lors de la connexion TLS.

Voici ce que j’obtiens sur SSL Labs :

  • 75.2.60.5 → Grade A+ (certificat valide et fonctionnel)

  • 99.83.190.102 → Failed to communicate with the secure server

Ce que j’ai déjà fait :

  • Vérifié la configuration DNS (A et CNAME corrects)

  • Cliqué plusieurs fois sur Verify DNS configuration puis Renew certificate

  • Vérifié que mes serveurs de noms sont bien :

    dns1.p05.nsone.net  
dns2.p05.nsone.net  
dns3.p05.nsone.net  
dns4.p05.nsone.net

Pourriez-vous forcer la synchronisation du certificat Let’s Encrypt sur tous les nœuds edge pour le domaine nadia-ruello.com ?

Merci beaucoup pour votre aide :folded_hands:

1 Like
2

Hi, @Nadia_RUELLO. We do not provide technical support in French. Would you please repost your question in English?

1 Like
3

Hello Netlify team,

I recently re-added my custom domain nadia-ruello.com (with Netlify DNS) and re-provisioned the Let’s Encrypt certificate.
Everything works fine for the domain and for the IP 75.2.60.5, but the other Netlify edge IP 99.83.190.102 still fails TLS handshake.

Here’s what I see on SSL Labs:

  • 75.2.60.5 → Grade A+ (certificate served correctly)

  • 99.83.190.102 → Failed to communicate with the secure server

I’ve already:

  • Verified DNS configuration (A + CNAME are correct)

  • Renewed the certificate multiple times

  • Confirmed nameservers → [dns1.p05.nsone.net](http://dns1.p05.nsone.net) … [dns4.p05.nsone.net](http://dns4.p05.nsone.net)

Could you please force a certificate sync on all edge nodes for nadia-ruello.com?

Thank you very much :folded_hands:

4

Hi, @Nadia_RUELLO. The IP address 99.83.190.102 is not one used by Netlify. My best guess is that you asked an bot what IP addresses to use and it gave you wrong information.

The solution for that would have been to delete that A record for 99.83.190.102.

However, I see you have moved this domain successfully to Netlify DNS so the issue appears to be resolved now.