Server management

Server firewall setup with CSF, ufw and fail2ban

We set up a firewall that keeps only the ports you need open, blocks repeated attacks with fail2ban and rate limits, and does not lock out your real users.

  • One-time job
  • Scope agreed before work
  • Written handover

Who is this for?

  • Your database or admin ports are reachable from the internet
  • Bots hammer wp-login.php or SSH all day
  • Your current firewall blocks real users at random
  • You run several servers and want the same rules on all of them

In short

Firewall setup for Linux servers: only needed ports open, database closed to the internet, fail2ban jails, rate limits on wp-login and xmlrpc, ModSecurity.

Packages: Basic · Standard · Complete. The price is quoted after we review your server or site.

Packages

Each package includes everything in the one before it.

Basic

10 tasks

CSF, ufw or iptables with only the needed ports open, internal ports closed and an SSH jail.

Request a quote
Recommended

Standard

18 tasks

Everything in Basic plus SSH and panel limited to your IPs, jails for web and mail, and rate limits for wp-login.php.

Request a quote

Complete

26 tasks

Everything in Standard plus xmlrpc and other sensitive paths, ModSecurity rules, log review after a few days and the same rules on several servers.

Request a quote

What is included in each package

TaskBasicStandardComplete
Initial review
List current services and portsIncludedIncludedIncluded
Agree which IPs must always be allowedIncludedIncludedIncluded
Pick CSF, ufw or iptables to suit the server and panelIncludedIncludedIncluded
Review existing rules and random blocksNot includedIncludedIncluded
Coordinate with the provider's firewall if one is activeNot includedIncludedIncluded
Inbound rules
Open only needed ports such as 22, 80 and 443IncludedIncludedIncluded
Close internal ports such as the database to the outsideIncludedIncludedIncluded
Apply rules with an open SSH session for quick rollbackIncludedIncludedIncluded
Limit SSH and the panel to specific IPsNot includedIncludedIncluded
Admin access through a VPN where possibleNot includedNot includedIncluded
fail2ban and rate limits
SSH jail with temporary bansIncludedIncludedIncluded
Jails for web server and mailNot includedIncludedIncluded
Rate limits for paths such as wp-login.phpNot includedIncludedIncluded
Rate limits for xmlrpc.php and other sensitive pathsNot includedNot includedIncluded
ModSecurity
Enable or review the base ModSecurity rule setNot includedNot includedIncluded
Fix false positives and problem rulesNot includedNot includedIncluded
Testing
Check sites and services after rules are appliedIncludedIncludedIncluded
Test fail2ban and rate limitsNot includedIncludedIncluded
Review firewall logs and bans after a few daysNot includedNot includedIncluded
Adjust rules based on the logsNot includedNot includedIncluded
Handover
List of applied rulesIncludedIncludedIncluded
How to disable the firewall temporarilyIncludedIncludedIncluded
Rules that may affect real usersNot includedIncludedIncluded
fail2ban and rate-limit settings as a listNot includedIncludedIncluded
Where the firewall and fail2ban logs areNot includedNot includedIncluded
Same rules applied on several serversNot includedNot includedIncluded

How it works

  1. Tell us what you needOpen a ticket and describe the job, the server or site, and any deadline.
  2. Scope and quoteWe review it and send the package, the exact scope and the price before starting.
  3. Secure access and backupYou share access through the ticket's private fields. We back up before changing anything.
  4. The workWe do the tasks in the package and test after each step.
  5. HandoverYou get the result, a written record of the changes and answers to your questions.

What we need from you

  • Root access
  • Your fixed IPs, if you have them
  • A list of the services that must stay reachable

What is not included

  • A server firewall does not stop large DDoS floods; those need filtering at the network or a CDN
  • Rate limits are tuned to your traffic; very aggressive limits can affect real users

Questions people ask

CSF or ufw?

On cPanel and DirectAdmin we use CSF. On plain Ubuntu or Debian servers ufw is simpler. Both work with fail2ban.

Does this protect against DDoS?

It stops small floods and brute force. Large DDoS attacks need upstream filtering or a CDN such as Cloudflare.

Can you apply it to several servers?

Yes, in the Complete package we roll the same rule set out to multiple servers.

Get a quote for firewall setup

Open a ticket with a short description of your server or site. We reply with the scope and price.

Request a quote