NewImprovedFixedSecurity

v2.9.7

PostgreSQL on Your Servers, Alerts in Discord, and Bulk PHP for the API

You can now run PostgreSQL on your server and manage it with pgAdmin. Your alerts can go to Discord or to your own web address, signed so you can trust them. You can also update WireGuard from the dashboard, and many backup, delete, Mail Delivery and billing problems are fixed.

🔥 New Features

🆕 Run PostgreSQL Sites and Manage Them With pgAdmin

Until now, xCloud sites could only use MySQL-type databases. Now a server can run one managed PostgreSQL service that every PostgreSQL site on it shares.

Who it’s for: developers running Node.js, PHP or Laravel sites from Git.

  • Add it when you need it. Choose PostgreSQL when you create a server. Or install it later from Server Management → Install a Service on an existing Nginx server.
  • See where it stands. The card shows queued, installing, ready and failed states. You can retry a failed install.
  • pgAdmin, managed for you. Enable pgAdmin next to the PostgreSQL card. Open it over HTTPS with its own web login, and manage databases and roles there.
  • Your data stays when pgAdmin goes. Disabling pgAdmin keeps your data. Databases you created in pgAdmin move to the owner role instead of being deleted.
  • Pick MySQL or PostgreSQL per site. Native Git sites (Node.js, PHP and Laravel) can choose either one when you create them. This works in the dashboard and in the white-label site form.
  • Ready to use. xCloud creates a database and role for the site and adds them to the site’s environment settings.
  • Deleting a site keeps its database. The database and role stay, and xCloud tells you so.
  • What you need. An Nginx server with Docker Engine 28 or newer.
  • Not supported yet. PostgreSQL sites cannot be cloned, migrated, staged or snapshotted yet. Their databases are not part of site backups yet, so export them from pgAdmin before you rely on a backup.

How to Install Managed PostgreSQL and pgAdmin in xCloud

🆕 Get Alerts in Discord or at Your Own Web Address

Before, your xCloud alerts could only go to Slack, Telegram or WhatsApp. Now you can also send them to Discord, or to any HTTPS address you run. Find both under Settings → Integrations → Notification.

Who it’s for: teams that work in Discord, and developers who want alerts in their own tools. Paid plans only.

  • Discord. Paste a Discord channel webhook URL. Alerts arrive in that channel with a bold title and an Open link to the server or site.
  • Webhook. Enter any HTTPS address you run. xCloud sends each alert as JSON and signs it with HMAC-SHA256, so you can check it really came from xCloud.
  • Your signing secret. It is shown once. The guide shows how to check the signature in PHP and Node.js.
  • Choose your alerts. Discord and Webhook each have their own switches for server, site and other alerts under Settings → Notifications. These are separate from Telegram.
  • Test it. Send test notification on each integration sends a test alert right away and shows the result.
  • Safe by default. Only HTTPS addresses are allowed. Private and internal addresses are refused when you add the integration, and again before every alert. Redirects are not followed.
  • Cleans up after itself. If you delete the Discord webhook, the integration removes itself. The URLs and secret are stored encrypted.

Send xCloud notifications to Discord or a webhook

🆕 Update WireGuard From the Dashboard

Your WireGuard site now shows its current version and the latest stable version. You can start an update from the dashboard and follow its progress.

Who it’s for: anyone running a WireGuard VPN site on xCloud.

  • Only safe updates. Only stable updates within the same major version are accepted.
  • Your data is protected. The update saves a copy of your client data first. If the new version does not start up healthy, xCloud puts that data back.

🧑‍💻 For Developers: Public API and MCP

  • Bulk PHP switching. You can switch PHP for up to 100 sites in one call. Preview the change first, then run it.
  • Bulk PHP results. xCloud runs the switches one after another on each server, and reports each site’s result as a task you can poll.
  • Bulk PHP with AI agents. An AI agent can now do “PHP 8.3 on all my sites” with one confirmation.
  • Site redirects. Create, update and delete a site’s redirects with POST, PUT and DELETE /api/v1/sites/{uuid}/redirections, with the same access rules as the dashboard.
  • Older WordPress redirects. Legacy WordPress redirects stay on Site Rules.
  • Vulnerability scan settings. Turn a site’s vulnerability scan on or off with PUT /api/v1/sites/{uuid}/vulnerability-scan/settings.
  • Turning a scan off. It now also removes the site from scheduled scans and scan lists, without deleting past findings.
  • WordPress versions you can install. GET /api/v1/catalog/wordpress-versions lists the versions site creation accepts, and the API checks against that same list.
  • Stricter filters. An unknown status or type filter on the site and server lists now returns 422, instead of a list that was silently not filtered.
  • WireGuard updates. You can also start a WireGuard update from the Public API or MCP.
  • Default PHP failures. When a default PHP switch fails, the Public API reports the failure and keeps the old default.

🔒 Security

  • Safer database management. Database and user names are now checked and safely handled in every database action.
  • No reach into other databases. A name with _ or % can never give access to another database, such as mysql.
  • Cloudflare “Block Sensitive File Access”. The rule now also blocks leftover wp-config copies.
  • No more false blocks. The rule’s backup check now matches only archive files, so normal site addresses are no longer caught.
  • Telegram. Linking a chat now uses a single-use code, and links only the chat you confirm.
  • Safer MariaDB on new servers. New servers install MariaDB 11.8. MariaDB 10 can no longer be chosen for a new server or a rebuild. Existing MariaDB 10 servers keep working.
  • No half-finished installs. A MariaDB install now stops if a download fails or the version is below the security fix, instead of finishing.
  • Know your version. Server pages show the exact MariaDB or MySQL version installed.
  • Checked custom Nginx rules. Custom Nginx rules saved by members with site-level access are checked before they are applied. This includes bulk apply, activation and site clones.
  • Unsafe rules are refused. Rules with unsupported directives, includes or unsafe paths are refused with a clear message. (Already live since 27 October.)
  • Passwords stay private. When you update a password, the new password no longer stays behind in server scripts.

⚡ Improvements

  • A failed default PHP switch now says so. The dashboard and the AI Assistant report the failure and keep the old default. Before, they showed a success that did not happen.
  • n8n needs Node.js 24. Site creation refuses n8n below Node.js 24. An n8n update is refused when the chosen version does not support your server’s Node.js.
  • Node.js update checks. They now clear out dead package sources first, so they no longer fail on retired PPAs.
  • Lighter PHP settings sync. Saving PHP settings now restarts only the parts of PHP that need it.
  • Faster SSH Key page for teams with many sites.

🐞 Bug Fixes

  • Backups. The Previous Backups page now shows a Backup in progress row the moment you click Backup Now, even for a site’s first backup. The page now refreshes itself when the backup finishes.
  • Backups. A failed backup, or one whose report xCloud refused, no longer leaves the destination stuck on “running”.
  • WordPress updates. A core update row no longer stays stuck on “Updating” after the update has finished. It is settled on the next scan.
  • Server deletes. Deleting a Vultr or Hetzner server that the provider already removed now finishes instead of failing.
  • Server deletes. Leaseweb servers outside the pool are now deleted at Leaseweb, instead of failing with “Invalid cloud provider”.
  • Server deletes. A server whose VPS is still in use is never terminated.
  • Mail Delivery. Removing your last Mail Delivery plan now closes the account at your email provider, and warns you about sites that will stop sending.
  • Mail Delivery. Each domain now publishes and checks its own DKIM key.
  • Billing. Enterprise API Site Security Pro purchases now work and bill the client team.
  • Billing. A saved server resize now runs after its invoice is paid, and the resize success email is sent again.
  • Billing. A white-label product SKU is now checked only within its own white label.
  • Firewalls and apps. The built-in OpenLiteSpeed firewall no longer blocks the xSpeed Database panel.
  • Firewalls and apps. LibreChat now keeps saving its MongoDB data after install, domain change and Site Rescue.
  • Firewalls and apps. A WordPress multisite network now survives a domain change, and old Cloudflare DNS records of a multisite are cleaned up.
  • Site SSH. A failed SSH change on the server is now rolled back in xCloud, and key syncs are checked.

Please note

  • PostgreSQL works on Nginx servers only and needs Docker Engine 28 or newer. PostgreSQL sites cannot be cloned, migrated, staged or snapshotted yet. Their databases are not in site backups yet.
  • Discord and webhook notifications need a paid plan. They are not yet available in the Public API, MCP or white-label dashboards.
  • n8n on a server with Node.js below 24 keeps running, but you cannot update it until you update Node.js.
  • Hide My WP custom Nginx preset can no longer be applied by members with site-level access only. A member who can manage the server’s settings can still apply it.