Firewall
The Firewall page holds your account's own IP Blocks: visitors from an address on the list get 403 Forbidden on every website of your account, and only there — other accounts on the server and the server firewall are not affected. Block Address takes one IPv4 or IPv6 address, or a network up to /16 (IPv4) or /48 (IPv6), with an optional note (203.0.113.9/24 is stored as 203.0.113.0/24); an address already on the list stays as it is. The trash icon unblocks an entry after a confirmation. The address is the visitor's own (behind Cloudflare too); certificate renewal keeps working for a blocked address. The server firewall itself stays with your hosting provider: an address that should be blocked for the whole server (or unblocked there after a mistaken ban) is a request to support.
Automatic protection still applies to your sites: Fail2Ban acts on abusive addresses without any action on your side. Connection rate limits are server rules your hosting provider sets up; none apply unless they have added them.
Web Application Firewall (resellers)
If your account is a reseller, each sub-account's page carries the sub-account's web application firewall (ModSecurity with the OWASP rule set) in four cards:
- WAF mode — Server setting (the default: the mode your hosting provider runs the server in, named in brackets), Off, Detect only (requests that match a rule are logged, none is refused) or Block; the mode in force is shown next to the choice. Turning the WAF off asks for confirmation: requests to the sub-account's sites are then neither inspected nor logged.
- Application exclusions — the OWASP rule set's own exclusion rules for WordPress, Drupal, Nextcloud, DokuWiki and XenForo let the application's everyday admin requests (saving a post, settings forms) through when the WAF blocks. WordPress is on Automatic: the rules run on the sub-account's sites where WordPress is found (the card names them); On for every site or Off override that. The other applications are off until you switch them on. They apply only to the sub-account's own sites; a change takes effect at once (the card says so while it is being applied, at most five minutes).
- Rule exclusions — one rule left out for the sub-account's sites, on every path or only on
paths that begin with a prefix such as
/wp-admin/(the prefix covers every path below it; the query string is not part of the path, so/x.php?y=/wp-admin/is not under/wp-admin/). Use one when a rule keeps refusing a legitimate request, and remove it once the application is fixed. - WAF log — the newest requests to the sub-account's sites that matched a rule, with every rule they matched. Exempt this rule on this path opens the exclusion form with that entry's rule and path filled in; shorten the path to cover a whole folder. On a server running LiteSpeed Enterprise an entry reads Matched: LiteSpeed records which rules a request matched but not whether it was refused — with the mode Block it was, with Detect only it reached the site.
The cards appear only when your reseller plan allows firewall management. If it does not, a Web Application Firewall card says so rather than showing the firewall as off. The account owner's own panel has no WAF settings.
What your reseller plan withholds is not offered. When your plan does not include a capability — databases, e-mail, FTP, DNS, SSL, the file manager, cron jobs, logs — its entry is left out of the menu, and the Remote tab of Backups is shown only when the plan allows remote destinations. The same applies while you are signed in to one of your sub-accounts.
Our support team is here around the clock for anything you can't find above.