WP Fail2Ban in xCloud Is Retired: Switch to BetterShield

Updated October 26, 2026 · 3 min read

Summarize with:
Share:

WP Fail2Ban is retired in xCloud. xCloud now protects WordPress logins with BetterShield, a free plugin by WPDeveloper that covers every WP Fail2Ban option and adds two-factor sign-in, passkeys and Cloudflare-aware firewall bans. You can no longer turn WP Fail2Ban on or change its options from the dashboard, and BetterShield is the only login protection you can turn on. One exception is cloning a WP Fail2Ban site. The clone settings still show a WP Fail2Ban option, but the clone keeps WP Fail2Ban whether you tick it or not, because the plugin files are copied. Switch the clone to BetterShield the same way.

Sites that still run WP Fail2Ban

Sites that already run WP Fail2Ban keep working until you switch them. Saving other settings on the site’s Security → Overview & Firewall page does not install or remove it. These sites show a blue Switch from WP Fail2Ban to BetterShield. banner with a Switch Now button, and the Login protection tile on Overview & Firewall reads WP Fail2Ban, retired.

The blue Switch from WP Fail2Ban to BetterShield banner on the site overview, with the Switch Now button highlighted

WP Fail2Ban and BetterShield never run together on one site. Switch Now opens the WP Fail2Ban & Login Protection card, where the switch in the card header removes WP Fail2Ban and installs BetterShield in one step. Every WP Fail2Ban option has a BetterShield setting:

In WP Fail2Ban In BetterShield
Block failed login attempts Limit failed sign-ins, with bans at the server firewall
Block common usernames Block common usernames
Block user enumeration Block public user listing
Protect comments Comment protection (Comments)
Block spam Bot check and Proof-of-work check on comment forms
Guard password resets Password reset protection (Password resets)
Guard pingbacks Block pingbacks

The full steps, with screenshots, are in Migrate from WP Fail2Ban to BetterShield.

The WP Fail2Ban configuration file

While WP Fail2Ban is installed, its settings live in wp-fail2ban-config.php in the site’s wp-content directory, which you can open with the File Manager or over SFTP. Switching to BetterShield, or uninstalling WP Fail2Ban, deletes this file and removes its include line from wp-config.php.

Troubleshooting Common Issues and Managing IP Access

1. Unban IP Addresses

Sometimes, server owners may find themselves accidentally blocked or may want to grant special access to specific IPs. In such cases, there are two ways to manage this. First, you can go directly to the Server →  Security → Firewall Management section, where you can manually ban or unban IP addresses. 

2. Whitelist And Blacklist IP Addresses

Alternatively, you can go to Site → Security → IP Management, where you’ll have the ability to whitelist or blacklist any IP. Whitelisted IPs will be completely exempt from Fail2Ban restrictions, ensuring they are never blocked, while blacklisted IPs will be denied access to the site entirely, regardless of behavior.

Note:  Whitelisted IPs will never be banned by Fail2Ban. Blacklisted IPs will be completely blocked from accessing the site.

WP Fail2Ban with xCloud

3. New Log Types Added 

Additionally, xCloud has introduced two new log types within the Server Log Viewer: the Fail2Ban Log and the Auth Log. These provide insight into IP blocking activity and authentication attempts, making it easier than ever to monitor your site’s security in real time. Both logs are available for servers running on NGINX as well as OLS.

Still stuck? Contact our support team for any of your queries.