NewImprovedFixedSecurity

v2.9.16.1

PostgreSQL in Every Backup, Zero-Downtime Deploys for Docker Compose, and Private Databases by Default

Your site’s backups now include its PostgreSQL database, and you can restore it in place from the dashboard. Docker Compose sites can now use release mode, so visitors keep getting pages while you deploy. New One Click database installs are private unless you choose otherwise.

🔥 New Features

🆕 Your PostgreSQL Database Is Now in Every Site Backup

Before, a backup of a site that uses a PostgreSQL database finished without errors but held only the site’s files. The database, the part you most need back, was missing. Now every backup includes it, and you can restore it in place.

Who it’s for: everyone with a site that uses a PostgreSQL database.

  • The database is saved with every backup destination: local, S3-compatible storage, Google Drive, pCloud and SFTP. Incremental backups save only the files that changed, and the full database each time.
  • Existing sites get Database turned on in their backup destinations automatically. New PostgreSQL sites have it on from the start, like MySQL sites.
  • The Backups and Backup Settings pages say Backups include this site’s PostgreSQL database. when a destination saves it. If none does, they tell you to turn on Database in a backup destination.
  • A backup now fails, and you get the failure email, when the database can’t be saved (for example, when its container is stopped). It no longer shows as finished with the database missing.
  • Restore puts the database back in place in one step. xCloud keeps a copy of the current database first, so a failed import changes nothing.
  • A PostgreSQL backup restores only into its own site. Restoring it into another site or a new site shows A PostgreSQL site can only be restored in place, from its own backups.
  • Backups taken before this release stay listed as they were, with files only.

How to Back Up and Restore a PostgreSQL Database in xCloud

🆕 Zero-Downtime Deploys for Docker Compose Sites

Before, deploying a Docker Compose site stopped its web container, so visitors saw errors until the new one started. Now you can turn on release mode for a Compose site, and the current version keeps serving until the new one is ready.

Who it’s for: developers who deploy Docker Compose apps from Git.

  • Works for a Compose app with one web service built from your repository, plus a database or other supporting services, and background services built from the same code.
  • To turn it on, open the site and go to Git, then on the Release mode (zero-downtime deploys) card click the switch and confirm with Turn on. Every team can use it.
  • Deploy a new version with Deploy Now, and roll back to the previous one in one click.
  • Backup and restore work as before. They still stop the site for a few seconds while its data is saved. A supporting service that had already stopped stays stopped after a backup or restore.
  • If your Compose file has a setting release mode can’t use, you get one plain reason that names the service and tells you what to change.
  • If a deploy can’t clean up the old version, the next deploy finishes the cleanup by itself.

Zero-Downtime Deployments for Docker Container Sites in xCloud

🧑‍💻 For Developers: Public API and MCP

  • PostgreSQL backups: backup settings and backup status now return database_engine (mysql, postgresql, sqlite or null). Restores over the API and MCP follow the same in-place rule as the dashboard.
  • Git detection: git/detect returns detection_failed: true and retry_after_minutes when the repository couldn’t be read, so a guess is never mistaken for a detection.
  • Database check before deploy: git/auto refuses an app that needs PostgreSQL or MySQL when no database is chosen and no connection values are passed. The answer lists missing_env_keys (for example DATABASE_URL) and the actions choose_database_engine and supply_env_file_content.
  • 14 more dashboard actions on MCP:
    • WordPress: read the update and rollback history of a plugin or theme, and the history of bulk update runs, with date, status and search filters.
    • Hermes: start, stop and restart its services, and give the Hermes Workspace its own domain.
    • Laravel: start the background task runner of a Laravel site.
    • Cloudflare Enterprise: read analytics, blocked attacks, the Page Shield script report and settings for an external domain. Clear the cache of a site or an external domain, all or by URL. A cache clear previews its target and asks you to confirm first.

🔒 Security

  • New One Click database installs are private by default. A new MySQL, PostgreSQL, Redis or other database install is only reachable from the server itself, not by server IP and port. Tick Allow public access when you install if you want it reachable from outside; the card then shows its public address. Apps that need open ports, such as Minecraft, Mumble and RustDesk, stay reachable as before. Existing installs don’t change. Manage One Click App Domains and Public Endpoints in xCloud
  • The card of a private database install no longer says its ports are open to the internet or asks you to close them in your firewall.

⚡ Improvements

  • Deploy via Git tells you when an app needs a database: before, an app that needs PostgreSQL or MySQL was accepted, the site was created, and then the app failed to start. Now the form says which database the app needs and why, and holds Deploy until you choose that database or add the connection values in the environment editor. This also works on OpenLiteSpeed servers. Troubleshooting Git Deployments: Stuck, Failed or Not Triggering

🐞 Bug Fixes

  • Deploy via Git
    • When xCloud can’t read a repository to detect its type, the form no longer picks PHP App for you. It now says it couldn’t read the repository, tells you when to try again, and offers Detect again or lets you pick the app type yourself.
  • Release mode
    • Turning on release mode for a Node.js site no longer fails when its .env file has a value with a space in it.
    • In release mode, a Node.js app now always runs the version you just deployed, with its own files.
  • Cloudflare Enterprise
    • Buying Cloudflare Enterprise for several sites at once no longer ends on an error page for teams billed by invoice.