HELPER VPS

Cloud firewall: free traffic rules for your VPS

A free cloud firewall that lets through only the traffic you allow, in front of your server

  • Free for every server
  • 50 rules, up to 10 servers
  • Add DDoS protection too

A cloud firewall allows or blocks incoming and outgoing traffic by your rules at the network level, before it reaches your server. HELPER VPS cloud firewall is free for every server, and you create 50 rules and apply them to 10 servers at once.

  • Cloud firewall

    Free for every server

    Free

    Billed monthly

    • Up to 50 rules
    • Up to 10 servers
    • Inbound and outbound traffic
    • Free
  • Firewall + DDoS protection

    Attack readiness

    168$/ mo

    Billed monthly

    • Up to 50 rules
    • 1 server
    • Inbound and outbound traffic
    • DDoS protection included

To prepare for large attacks too DDoS protected VPS

Which servers need a cloud firewall?

Every server exposed to the internet needs a firewall. Open only the ports you really need and unwanted connection attempts never reach your server. The firewall is free, so make attaching it when you create a server your default. Here are four common cases.

How is a cloud firewall different from a firewall inside the server?

The two firewalls are strongest together. The cloud firewall filters first in the network outside the server, and the firewall inside the server checks once more within the operating system. Keep rules in both places aligned on the same principles, and if one side has a gap, the other still protects you.

Cloud firewall

A firewall that filters first, outside the server

Best for

  • When applying the same rules to several servers
  • When keeping rules through OS reinstalls
  • When managing rules at a glance in the control panel
  • When blocking disallowed traffic before it reaches the server

Firewall inside the server (ufw, firewalld)

A firewall running inside the operating system

Best for

  • When you need detailed per-program rules
  • When configuring just one server separately
  • When keeping connection logs inside the server
  • When adding a second layer on top of the cloud firewall

How does a cloud firewall work?

A cloud firewall is a list of rules at your server's network entrance. Each rule sets a direction (inbound or outbound traffic), protocol, port and allowed IP address range, and only traffic matching the list gets through. Traffic not in the rules never reaches the server's operating system, so it uses none of the server's CPU or memory.

Create one firewall and you can add up to 50 rules and apply the same firewall to up to 10 servers. Split firewalls by role, such as a web server group and a database group, and when you create a new server you just choose the right firewall; changing rules applies them to all the grouped servers together. Rule management stays in one place.

Even if you reinstall a server's operating system, cloud firewall rules live outside the server, so they stay in place. Right after a reinstall, before settings inside the server are done, only the necessary ports are open, so you stay equally protected while preparing the new server. After a reinstall, just finish the settings inside the server and reopen your service right away.

How should I write cloud firewall rules?

The basic approach is to open only what you need and close the rest. For a web server, allow inbound traffic on ports 80 and 443 from all addresses, and SSH port 22 only from the IP addresses you connect from. Just these three lines tidy up most web servers. Keep other ports closed.

For servers used only internally, such as database or cache servers, open the relevant port only to the addresses of other servers in the same service. Using a private network as well, you can write rules with internal address ranges, so adding servers means fewer rule changes. Internal services need not be opened on public addresses, making the setup simpler.

Outbound rules set where your server may connect. Usually they are left as allow all, but for payment servers or servers handling important data, setting where they may connect makes them safer. Port 25 for sending mail is blocked on every server to prevent spam, so send email through a sending service that uses port 587 or 465.

How much does the cloud firewall cost?

The cloud firewall is free for every server. For servers that need protection against attacks, add DDoS protection for $1.68 per month to use alongside the firewall.

HELPER VPS in numbers

Choose from 40 regions, 12 operating systems and 10 one-click apps in one account, and pay right away. The numbers below are based on what is on sale now.

Operating systems and apps on servers the firewall protects

The cloud firewall works outside the server regardless of operating system. Apply the same rules to Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS Stream, FreeBSD and one-click app servers alike.

Why choose HELPER VPS cloud firewall

Cloud firewall FAQ

Answers on cloud firewall pricing, rules and setup

Is the cloud firewall free?

Yes, the cloud firewall is free for every server. You can add up to 50 rules to one firewall and apply it to up to 10 servers. To prepare for large traffic attacks too, add DDoS protection at $1.68 per month per server, which renews together with the server fee. Servers using only the firewall stay at the server price.

What is a cloud firewall?

A cloud firewall allows or blocks traffic by your rules at the network level outside the server. Rules are set by direction, protocol, port and IP address range, and only matching traffic is sent on to the server. It works regardless of operating system, so it is used the same way on both Linux and FreeBSD servers.

How many rules can I create?

Up to 50 rules per firewall. A web server usually needs just three rules, for ports 80, 443 and 22, leaving plenty of room even after adding admin tool or database ports. Create separate firewalls for server groups with different roles for easier management. Each rule sets a direction, protocol, port and IP range.

Can I apply one firewall to several servers?

Yes, apply the same firewall to up to 10 servers. Change one rule and it applies to all the grouped servers together, so there is no need to repeat the same settings per server. Create firewalls by role, such as a web server group and a database group, and just choose the right one for each new server. Rule management stays in one place, reducing mistakes.

Do I also need to set up a firewall inside the server?

The cloud firewall alone lets you open only the ports you need, and using a firewall inside the server such as ufw or firewalld as well adds a second layer. Keep rules in both places aligned on the same principles, and if you make a mistake on one side, the other still blocks it. Setup examples are in the firewall guide.

How should I open the SSH port?

We recommend allowing port 22 in your inbound rules only from the IP addresses you connect from. Combine this with SSH key login and password-guessing connection attempts never reach your server. If you connect from several places, add each of those addresses to the rules. The basic approach is web ports open to everyone and admin ports open only to your address.

How is DDoS protection different from a firewall?

A firewall lets through only traffic that matches your rules, while DDoS protection filters large traffic attacks flooding in on allowed ports. Using both, you open only the ports you need and are also ready for attacks arriving on those ports. DDoS protection is $1.68 per month per server.

Can I open mail server ports?

Port 25, used for sending mail, is blocked on every server to prevent spam. Send website notification emails through port 587 or 465 of an external sending service, and allow those ports in your firewall's outbound rules. Receiving mail and other ports work according to your rules.

Do rules disappear if I reinstall the operating system?

No, cloud firewall rules live outside the server, so they stay in place even when you reinstall the operating system. Right after a reinstall, before you finish the settings inside the server, only the necessary ports are open, so you are protected by the same rules while preparing the new server. Changing firewalls or editing rules needs no reinstall either, and takes effect right away on running services.

Do rules apply to IPv6 addresses too?

Every server comes with one IPv4 address and an IPv6 address. When creating firewall rules, include both IPv4 and IPv6 address ranges to manage traffic arriving at both addresses on the same principles. It is best to turn on IPv6 settings in the firewall inside the server too. Managing both addresses on the same principles leaves no gaps.

Cloud firewall guides

Guides worth following when creating firewall rules for the first time

The cloud firewall is free. DDoS protection is priced monthly in US dollars, included in the server price and renews with your server.

Port 25 for sending mail is blocked on every server | If payment fails: server suspended, then deleted 3 days later | Remaining time on deleted servers is not refunded. Refunds go to your account credit.