5 verified briefings on Web Hosting. Each story includes a plain-English summary, why it matters, and the concrete action engineering teams should take.
A developer reported being unable to connect their custom subdomain to a Netlify site. The platform indicated the domain was already managed by another team, preventing the new configuration. The user has requested a manual domain lock release from Netlify support after verifying ownership.
A Netlify user reported a "certificate parameter is required" error when trying to provision a Let's Encrypt SSL certificate for a custom domain. The issue occurred despite using Netlify DNS with fully propagated records, prompting a request for manual intervention from the support team.
A user on the Netlify Community forum reported an issue where their website's SSL certificate failed to activate, resulting in a "not secure" warning for visitors. This occurred despite confirmation that their DNS records had propagated correctly, a common prerequisite for SSL issuance.
A developer reported being unable to add a subdomain to a new Netlify project because it was linked to an old one. This common issue requires manual intervention from Netlify support, even after proving ownership via DNS records, highlighting a platform friction point for developers.
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.