How to block or allow an IP address in the firewall
On this page
A firewall rule blocks or allows an address (or a whole range) for every service on the server: websites, email, FTP, SSH and the panels.
Steps
- In the administrator panel (
https://<server>:2087), open Firewall (section Security). - Under Allow or block an IP, choose the Action: Block or Always allow.
- IP or range — one address (
198.51.100.7) or a range in CIDR form (198.51.100.0/24). IPv6 works too (2001:db8::/48). - Note — why, for example
billing serverorspam bot. - Duration — Permanent, 1 hour, 1 day, 1 week or 30 days.
- Click Add rule.
- Click Keep these rules in the yellow box within 90 seconds, or the change is rolled back.
The rule appears in the Rules table with its Source (who added it) and Expires time.
Remove a rule
Click Remove next to it in Rules and confirm. Removing a block takes effect at once. Removing an allow rule must be confirmed with Keep these rules like any other change.
Good to know
- Allowed addresses pass everything in the firewall: port filtering, blocks and the public attacker lists, and the Protection Shield and brute-force protection never block them there. Use Always allow for your office, your monitoring and your billing server.
- The panel login block is separate. Brute Force Protection can still refuse logins from an allowed address after too many failures; add the address to its Whitelisted IPs too. See brute force protection.
- You cannot block your own address: "That would block your own IP (…)."
- Very large ranges are refused ("That range is too large to block."): IPv4 ranges must be
/8or smaller, IPv6/32or smaller. - Automatic blocks from brute-force protection and the Protection Shield also appear in Rules, with an expiry time.
- Customers can block visitors for their own websites only in Access Control in their control panel.
Common questions
How do I block a whole country?
There is no country list. Block the ranges you need, or use the public attacker lists.
Why should a billing server be allowed?
Wrong API tokens count as failed logins. A billing system that retries with a bad token could get its address blocked. Allow it here and add it to Whitelisted IPs in Brute Force Protection, so neither block can hit it.
The format is refused. What is accepted?
An IPv4 or IPv6 address, or a range like 203.0.113.0/24. The message is "Enter an IP address or a CIDR range (e.g. 203.0.113.0/24)."
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to configure the server firewall and open ports
Turn port filtering on, choose the open TCP and UDP ports, and confirm the change within 90 seconds so you can never lock yourself out of the server.
- How to unblock an IP address (customer can't connect)
A customer or you cannot reach the server or log in: find which protection blocked the IP address and unblock it in the right place in the admin panel.
- How to block known attackers with public IP blocklists
Turn on public lists of attackers, spammers and botnets (Spamhaus DROP, blocklist.de, CINS Army, abuse.ch Feodo) so they are blocked before any service.
- Firewall change was rolled back or locked you out
Why firewall changes come back after 90 seconds, how to confirm them with Keep these rules, and what to do if a firewall change cut off your access.