Illustration of a broken lock next to a green checkmark, representing an SSL certificate failure.

Infrastructure

Netlify SSL Fails Despite Correct DNS

TL;DR: A Netlify user is reporting an SSL certificate provisioning failure for a custom domain. The issue persists despite all DNS checks, including Netlify's own verification, showing a correct configuration. The user has requested manual intervention after repeated automated failures, highlighting a potential platform-level issue.

By Ashish KaleNetlify Communityjust now1 min readupdated 4h ago

Source

Key facts

Category: Infrastructure
Impact: Low
Published: just now
Source: Netlify Community

Full summary

A Netlify user reports an SSL certificate failure despite a correct and verified DNS configuration, pointing to a hiccup in platform automation.

A user on Netlify's community forum has reported a persistent issue with SSL certificate provisioning for their custom domain. The user's site is configured to use Netlify's own DNS, and all standard diagnostic tools indicate that the domain's setup is correct. There are no conflicting CAA records, DNSSEC is not enabled, and no other DNS issues have been identified. Netlify's own dashboard confirms that the DNS verification for the custom domain was successful. Despite these positive checks, the automated process to issue an SSL certificate fails immediately every time it is attempted, preventing the site from being served securely over HTTPS. The user has requested a manual intervention from Netlify's support team to resolve the problem.

This situation is a concern for developers, IT teams, and businesses that rely on Netlify's automated infrastructure for deploying and managing websites. An SSL certificate is essential for modern web standards, ensuring data encryption, building user trust, and maintaining search engine rankings. When automated systems like SSL provisioning fail without a clear reason, it can lead to deployment delays and unexpected downtime for secure sites. This case highlights a potential vulnerability in the platform's automation, where a correctly configured user account can still encounter critical errors. It underscores the importance for technical teams to be aware of such platform-specific anomalies and to factor in potential support delays when planning project timelines.