The Firewall lets you block or allow IP addresses at the server firewall, and optionally restrict SSH access to a list of trusted IPs. This can be found by clicking ‘Firewall’ under the ‘Tools’ menu in the sidebar. By default, only the ports the server needs (e.g. 80 & 443) are open, with all the rest closed. If you need additional ports opened, please contact Support.
Firewall rules apply to the whole server, across all ports and all sites. To block visitors from a single site only, use IP Blocking in that site’s settings instead.

Blocking an IP

You’ll see a list of IP addresses currently blocked at the firewall. You can remove existing blocks at any time. Blocked IPs Click the ‘Block IP’ button and enter the address you want to block, along with an optional comment. You can enter a single IPv4 or IPv6 address, or a range in CIDR notation. Blocked IPs are dropped at the firewall entirely, so they cannot reach any service on the server.

Allowing an IP

Allowed IPs work the other way around: an allowed IP is whitelisted at the firewall and will never be blocked. This is useful for your office or home IP, monitoring services, or anything else that should always be able to reach the server. Click the ‘Add Allowed IP’ button and enter the address, along with an optional comment. As with blocks, single addresses and CIDR ranges are both accepted. Add Allowed IP

Restricting SSH by IP

You can lock down SSH so that only trusted IP addresses can connect. When enabled, port 22 (SSH) is closed at the firewall and only the IPs on the allowed list below the toggle can connect. Restrict SSH by IP Click ‘Add IP’ to build the list of allowed addresses- you’ll need at least one before the restriction can be enabled. Once you’re happy with the list, switch the toggle on.
Make sure your own IP is on the allowed list before enabling SSH restriction, or you’ll lock yourself out of SSH. Bear in mind that home and mobile connections often change IP address- if you do get locked out, you can disable the restriction from the Cito dashboard, or contact Support.
If your sites sit behind Cloudflare or a similar proxy, visitors connect to the server from the proxy’s IPs rather than their own. Firewall blocks won’t match those visitors- use per-site IP Blocking, which detects the real visitor IP.