NewImprovedFixedSecurity

v2.9.6

Safer WordPress Logins, Simpler Cloudflare Setup, and a Weekly Backup Reminder

You can now protect WordPress logins with BetterShield, which replaces WP Fail2Ban. You can connect Cloudflare with just one API token. A weekly email tells you which servers have no backup, and you can finish setting up add-ons you already paid for. This release also brings more tools for the Public API and MCP, a large round of security work and many fixes. The v2.9.5.1 update from 25 October is included too.

🔥 New Features

🆕 Stop Login Attacks With BetterShield

Before, login protection used WP Fail2Ban. Now Login Protection on a WordPress site’s Security page installs BetterShield instead. It blocks repeated failed logins and also bans the attacker’s network at your server firewall for 15 minutes.

Who it’s for: WordPress site owners and agencies.

  • Blocks attackers, not Cloudflare. An attacker can’t keep trying from the same network block. BetterShield trusts Cloudflare’s visitor IP only when the request really comes from Cloudflare, so Cloudflare edges are never banned.
  • Opt-in per site. Nothing is installed until you turn it on.
  • Free switch from WP Fail2Ban. Sites that use WP Fail2Ban keep working and show a Switch to BetterShield notice. Turn on the switch on the WP Fail2Ban & Login Protection card. xCloud removes WP Fail2Ban, then installs BetterShield, free.
  • Strict by default. Every protection starts on. You can turn each one on or off from the site’s Security page:
    • the failed sign-in limit
    • the bot and proof-of-work checks
    • comment, password reset and registration protection
    • common usernames
    • public user listing
    • pingbacks
  • Extra hardening when you turn it on. BetterShield also:
    • turns off the dashboard file editor
    • adds security headers
    • hides the WordPress version
    • stops uploads folders from listing their files
    • tightens wp-config.php permissions where needed
    • moves an http:// site address to https:// when the site has a working certificate
  • Requirements. BetterShield needs WordPress 6.7 and PHP 8.0 or newer.
  • A cleaner Security page. All of a site’s security settings now live under one Security menu. Each card has an on/off switch in its header.

Set up BetterShield login protection

🆕 Connect Cloudflare With One API Token

Cloudflare retired Origin CA keys on 30 September 2026. Now xCloud doesn’t need a Global API Key either: a new Cloudflare integration takes one scoped API token and nothing else.

Who it’s for: everyone who uses Cloudflare with xCloud.

  • Every call to Cloudflare uses that token.
  • Existing integrations keep working. If your token lacks a permission, xCloud falls back to your saved Global API Key.
  • xCloud records which permission was missing. It shows it on the integration with an Update Token button.
  • Error messages now name the exact permission to add, such as Zone › SSL and Certificates › Edit.

🆕 Get a Weekly Email About Servers With No Backup

Before, a missing backup could go unnoticed until you needed a restore. Now a weekly check emails your team a list of servers whose production sites have no active remote backup and no provider backup.

Who it’s for: everyone.

  • You get this email at most once every 30 days.
  • Servers younger than 7 days are skipped.
  • The email is on for everyone. Turn it off under Settings → Notifications → Backup Reminders.

🆕 Finish Setting Up Add-ons You Already Bought

Before, an add-on bought in the cart but not set up yet was easy to lose track of. Now it appears on its own page with a Continue Setup option. This uses your credit instead of charging you again.

Who it’s for: anyone who bought an add-on, such as a Mailbox or Site Security Pro credit.

🧑‍💻 For Developers: Public API and MCP

  • New /api/v1/sites/{uuid}/bettershield endpoints turn BetterShield on or off, switch a site from WP Fail2Ban, and read or change its settings.
  • The Public API lists installed and available server PHP extensions for each PHP version.
  • The Public API installs or removes a PHP extension, and you can follow its progress.
  • The Public API reads and updates server-wide php.ini settings.
  • The same PHP extension and php.ini actions are available as MCP tools.
  • The xCloud AI Assistant can list and install PHP extensions and change php.ini settings. Removing an extension stays with you.
  • Rename a server or site and set its tags and notes with PATCH /api/v1/servers/{uuid} and PATCH /api/v1/sites/{uuid}.
  • Filter server and site lists by tag.
  • Deactivate WordPress plugins or themes with POST /api/v1/sites/{uuid}/wordpress/deactivate. You can follow its progress, the same way as activation.
  • Reinstall a server’s monitoring agent through the Public API or MCP without losing monitoring history.
  • Vulnerability scans in the API now need the site:vulnerability-scan permission.

🔒 Security

  • Backups. Backups accept only plain file names and folders. A restore refuses records that don’t look like a real backup. Every stored name is handled safely when you restore or delete a backup.
  • Server scripts. Server scripts that run as admin, for logs, SSH keys and the OpenLiteSpeed firewall, now refuse symbolic links. They write site files as the site user.
  • Payments. Stripe payment updates are applied only when they come from the account that bills your team. Split payments are checked before anything happens.
  • Passwords and keys stay hidden. These no longer appear in page data, logs or server scripts:
    • TLS private keys
    • Stripe tokens
    • Elastic Email keys
    • Slack and Telegram secrets
    • DigitalOcean and GCP credentials
    • the support access code
  • Support tickets show only the sites and servers you may open.
  • Addresses checked. Storage provider endpoints, cPanel hosts, migration sources and enterprise server addresses must be public addresses.
  • Mailbox aliases can only be created on a domain your team owns.
  • Invitations can only be accepted by a verified email address.
  • White label. Wholesale and product deletion now check that you are allowed to do them.

⚡ Improvements

  • Faster Cloudflare checks. xCloud now looks up a zone by name instead of listing every zone in every connected account. Teams with large Cloudflare accounts no longer hit timeouts or rate limits.
  • PageSpeed scan limits. You can run one scan per site every 10 minutes, and 30 per team per hour. This keeps the shared Google quota available for everyone. The message tells you how long to wait.
  • Faster site lists. The All Sites list and the command palette load less data.
  • Reinstall monitoring. Reinstall a server’s monitoring agent from the Monitoring page without losing monitoring history.
  • Hetzner sizes per location. The server create page shows which Hetzner sizes are available in the location you chose. The rest are greyed out.
  • Reseller panel.
    • The Last 1 Year invoice filter works.
    • Page links keep your filter, search and sort.
    • Settings links follow permissions.
    • The onboarding product modal lists your providers.
    • Each reseller’s custom SMTP is used for its own emails.
    • A client’s team email follows the client email.
  • PHP 7.4 minimum for fresh WordPress installs and PHP switches.
  • Server Settings page. A new server page groups the services you can install.

🐞 Bug Fixes

Backups

  • Scheduled backups no longer overlap or hang a server.
  • A failed SFTP backup is now recorded as failed.
  • A Docker restore now uses the exact image its backup recorded.
  • Two sites with the same domain now keep separate remote folders.
  • Remote backups are now only forgotten after the provider confirms deletion.

Cloudflare

  • The script-tag WAF rule no longer blocks logged-in admin-ajax.php saves.
  • Deleting a site or server now keeps a DNS record that points at another server.
  • WAF and edge cache rules now follow a domain change.
  • A new Origin CA certificate is now installed before the old one is revoked.
  • Cloudflare Enterprise domains are now cancelled on every permanent server delete.

PHP

  • A PHP install or site PHP switch no longer stays stuck on “installing” while another install is running.
  • PHP 8.3 can now be uninstalled on Nginx servers.
  • On OpenLiteSpeed, xCloud now refuses to remove the PHP version OpenLiteSpeed depends on. Before, it removed OpenLiteSpeed with it.

Firewalls

  • The built-in OpenLiteSpeed firewall is updated to v1.5. It no longer blocks WP Export, /login/ pages and SAML SSO.
  • The built-in Nginx firewall no longer blocks the xSpeed Database panel or OAuth logins.
  • The firewall log now holds real blocks only and shows the rule that blocked the request.
  • AI Bot Blocker no longer blocks AI assistants acting for a user, such as Claude-User and ChatGPT-User.

Mail

  • A mailbox that failed to delete is no longer reported as deleted.
  • Renaming an alias now moves it at your email provider too.
  • Adding Mail Delivery or Mailbox records now keeps your existing SPF.
  • A declined Mailbox purchase can no longer be activated by reopening the payment page.
  • Custom SMTP providers are no longer billed.
  • Add-on bills are back on the monthly invoice.

Apps

  • Supabase now keeps accepting connections after a permission reset.
  • A WireGuard site now keeps its version when you change its domain.
  • Two one-click installs at once no longer get stuck waiting on each other.
  • Open WebUI sign-ups no longer become admins.
  • LibreChat registration is now closed on new installs.

Notifications

  • Telegram alerts now arrive when a server, site or plugin name contains < or &.

Other

  • A disabled site on OpenLiteSpeed now shows its saved disabled-site page.
  • The SSH Key page now loads for very large teams.
  • A password-mode migration can now switch to a public key.
  • The Plain stack now shows its own icon.
  • An unverified invitee is now sent to verify their email instead of seeing an error.

Please note