Changelog

This release resolved all 503 errors previously affecting Sites hosted through CloudCannon, recategorized some of these as legitimate 414 errors, and added several improvements, including an updated in-app font, a streamlined Getting Started with CloudCannon guide, and better detection of Lume, Gatsby, and Nuxt when using non-standard config filenames.

It also addressed several issues, including those affecting SAML login attempts, Snippet Cards in Text Editable Regions, Site Mounting, file uploads, and password reset for User Account Authentication.

Features & Improvements

• Resolved all 503 errors previously causing issues for Sites hosted through CloudCannon and recategorized some of these errors as legitimate 414 errors. Another postmortem for this issue is coming soon.
• Updated the in-app font to system-ui for better accessibility, performance, user experience, and maintenance.
• Streamlined the in-app Getting Started with CloudCannon guide after onboarding feedback, including reducing the number of steps, improving messaging, and updating the UI for better task clarity.
• Updated the UI for the Edit Collections modal for better clarity around folder structure and suggested Collections.
• Removed duplicate suggestions for your Build Configuration (e.g., public and ./public/ for an Output Path).
• Improved detection of Lume, Gatsby, and Nuxt during CloudCannon Configuration File creation when the Site uses a non-standard config filename.

Fixes

• Fixed an issue where CloudCannon did not clear the record of your failed login attempts after a successful SAML login.
• Fixed an issue where you could not drag Snippet Cards inside a Text Editable Region.
• Fixed an issue where CloudCannon did not list existing mounted Sites on the Site Settings and Org Settings pages.
• Fixed an issue where you could not upload a file with the same filename twice.
• Fixed an issue where CloudCannon would give a 500 error when you tried to reset your password for User Account Authentication.
• Fixed an issue where, in some cases, CloudCannon would treat login attempts on Sites with Password Authentication or User Account Authentication configured as a Form submission.
• Updated dependencies to patch security vulnerabilities.

The old version of the CloudCannon app is no longer available. Thank you to everyone who provided feedback during this process; we have addressed all issues brought to our attention. If you have any further feedback or questions, please don't hesitate to contact our friendly support team.

This release added several performance improvements to reduce issues for Sites hosted through CloudCannon. We are continuing to monitor this issue and are happy to report that the incidence has been reduced. It also added support for styles in Text Editable Regions.

This release addressed several issues, including those affecting the Recent Activity list, sorting in the Collection Browser, and Snippets in Editable Regions.

Features & Improvements

• Added more improvements to address performance on Sites hosted through CloudCannon.
• Text Editable Regions where data-type="text" now support Rich Text styles. You can define these using _editable.text.styles or _inputs.*.options.styles for Rich Text Inputs.

Fixes

• Fixed an issue where CloudCannon would incorrectly report that users "Performed an unknown action" in the Recent Activity list when they merged a Pull Request.
• Fixed an issue where, in some cases, sorting by date in the Collection Browser did not work correctly.
• Fixed an issue where Snippets in Editable Regions did not correctly load Input configuration.

Over the past week, we experienced a significant increase in bot and crawler traffic. This exposed a weakness in how our application managed database connections, leading to 503 errors for Sites hosted on CloudCannon. We take reliability seriously, and would like to apologize to all customers affected by this incident.

We have deployed a series of changes to address the root cause of this issue and are actively monitoring our hosting. We will confirm the effectiveness of these changes over the coming days. We are also working on broader architectural improvements to provide additional resilience under high traffic conditions. For the full incident postmortem, please see our Status page.

This release also addressed several issues, including those affecting new payment methods, resolving Syncing Errors, and custom Testing Domains for Client Organizations.

Fixes

• Fixed an issue where, in some cases, you could not retry a payment after a failed payment.
• Fixed an issue where, in some cases, the Reconnect or Clear and Reconnect buttons for resolving Syncing Errors did not work.
• Fixed an issue preventing Partner Organizations from creating custom Testing Domains for their Client Organizations.