Netlify news

A recent update to the Netlify CLI, from version 24 to 26, is causing deployment failures for some developers. The issue appears to affect Next.js projects, where a key server handler file exceeds the platform's 250 MB size limit, breaking previously working CI/CD pipelines.

A Netlify user has reported a billing discrepancy on the company's community forum. After purchasing extra credits and receiving payment confirmation invoices, the user found that the credits were not added to their account, highlighting a potential issue with Netlify's credit allocation system.

A nonsensical post with a garbled title and body was published on the Netlify Community forum. The entry, titled 'Ponzu. Hhgvvccccvv,' contained no meaningful information and appears to be an isolated instance of spam or an erroneous post on the developer platform.

A strange, off-topic post about a passion flower appeared on the Netlify Community forum. The post, unrelated to Netlify's services, raises minor questions about content moderation and spam filtering on the platform used by developers for support.

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 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 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 Netlify user is unable to add a custom subdomain to their site, receiving an error that the domain is already in use. Despite being the administrator and creating a verification TXT record, the user requires manual intervention from Netlify's support team to release the domain.

A Netlify user reported a persistent bug blocking production deployments with a "credit usage exceeded" error. The block remains active even after the user purchased more credits, suggesting a stale system state. This issue has prevented new deployments to their site for over 24 hours.

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.

A Netlify user reported being locked out of their domain after deleting their team account. The platform's DNS system retained control of the domain, preventing it from being added to a new project. This issue requires manual intervention from Netlify support to resolve the configuration conflict.

A developer's production site went offline after they deleted their Netlify account without first removing a custom domain. Despite changing nameservers, Netlify's network continued to intercept traffic, serving a 404 error. The issue required manual intervention from Netlify support to purge the DNS zone.

Developers using Netlify are reporting a DNS configuration issue where an 'already exists' error prevents them from setting up domains. The problem stems from orphaned DNS zones on Netlify's provider, NS1, left over from previous incomplete setups, requiring manual intervention from Netlify support to resolve.

A Netlify user reported their custom domain remains locked by the platform even after being removed from their project. This prevents them from connecting the domain to a new hosting provider, indicating a potential backend issue where domains are not being fully released from Netlify's system.

A developer on the Netlify Community forum reported a deployment failure due to a serverless function exceeding the platform's 250 MB size limit. This error prevents site updates and highlights a critical constraint for developers building complex applications on the platform, requiring code optimization.

A developer reported their Netlify site was automatically suspended while they were fixing a build error. The automated system flagged the site, preventing redeployment even after the code was fixed. The developer had to contact support to manually lift the suspension on their informational website.