SSL certificate provisioning stuck after 48 hours

Support
1

Hello Netlify Team,

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

Site information

  • Site name: saleebenessere
  • Primary domain: saleebenessere.it
  • WWW domain: www.saleebenessere.it
  • Netlify subdomain: saleebenessere.netlify.app

Issue

My custom domain has been connected to Netlify DNS for approximately 48 hours.

The DNS configuration appears to be completely correct, but the HTTPS section of the dashboard is still stuck on “Waiting on DNS propagation”, and the Let’s Encrypt certificate has never been provisioned.

What I have already verified

  • Netlify DNS is enabled and being used.
  • DNS propagation is complete worldwide (verified with DNSChecker).
  • DNS verification in the Netlify dashboard is successful.
  • DNSSEC has been disabled at my registrar (Aruba).
  • There are no CAA records configured.
  • There are no TXT records configured that could interfere.
  • The custom domain correctly resolves to the Netlify IP addresses.
  • The site is accessible through the Netlify subdomain.
  • The site is also accessible through the unique deploy permalink.

Current behavior

HTTPS is still serving the default Netlify wildcard certificate instead of a certificate for my custom domain.

The certificate presented is:

  • Common Name (CN): *.netlify.app

Instead of containing:

Because of this, browsers report the error:

NET::ERR_CERT_COMMON_NAME_INVALID

When checking the certificate from the terminal, it still returns the default Netlify certificate instead of a Let’s Encrypt certificate for my domain.

Additional information

The website itself works correctly and DNS resolution appears to be functioning normally.

The only issue is that the SSL certificate has never been issued, despite the DNS verification succeeding and nearly two days having passed.

Request

Could someone please check whether the SSL provisioning process is stuck for my site and, if necessary, manually trigger a new Let’s Encrypt certificate issuance?

From my side, everything appears to be configured correctly, but the HTTPS provisioning process never completes.

Thank you very much for your time and assistance.