Manage your VPS firewall from the client area
- Updated 15 November 2026
- 4 min read
Every AtmosNode VPS comes with a network firewall that you manage from your client area. It filters traffic before it even reaches your server: you choose which ports are open and which addresses can reach your VPS, without typing a single command.
It works alongside your operating system's firewall and does not replace it: see Set up the UFW firewall on Linux or Open a port in Windows Firewall.
1. Open the firewall
- Log in to your client area and go to My services.
- Open your VPS.
- In the Firewall box, click Manage firewall.
At the top of the page, a summary shows the current state: firewall disabled (all traffic gets through), all inbound traffic allowed, or inbound traffic blocked except for the listed ports.
2. Enable the firewall
If the firewall is disabled, click Enable firewall. While it is disabled, your rules are saved but not applied.
Enabling the firewall does not close anything on its own: as long as there is no "Block" rule, inbound traffic is still allowed.
3. Open common ports with templates
The Templates section allows the most common ports in one click, inbound, over IPv4 and IPv6:
| Template | Ports opened |
|---|---|
| SSH (Linux VPS) | 22 TCP |
| Remote Desktop (Windows VPS) | 3389 TCP |
| Website | 80 and 443 TCP |
| Minecraft | 25565 TCP and UDP |
| Pterodactyl | 80, 443, 8080 and 2022 TCP |
| FiveM | 30120 TCP and UDP |
A template that is already in place shows the Added badge.
4. Add a rule
In Add a rule, fill in the fields, then click Add rule. It is applied immediately.
- Action: Allow or Block.
- Direction: Inbound (connections to your VPS), Outbound (connections from your VPS) or Both.
- Protocol: TCP, UDP, ICMP (ping) or All. If in doubt, check your software's documentation: many games use UDP.
- Port: a single port (
25565) or a range (27015-27030). Leave empty for all ports. - Source address (optional): an IP address (
203.0.113.10) or a network (203.0.113.0/24). The My IP button fills in your current address. Leave empty for any address. - IP version: IPv4 + IPv6, IPv4 or IPv6.
5. Close everything except your services
This is the safest setup: only the ports you need stay open.
- Allow your own access first: the SSH template (Linux) or Remote Desktop template (Windows).
- Allow the ports of your services (templates or Allow rules).
- Add a Block rule, direction Inbound, protocol All, with port and address left empty.
The summary then shows "Inbound traffic blocked, except" followed by your open ports.
WarningIf you block all inbound traffic without allowing SSH or Remote Desktop, the client area warns you and offers Allow SSH first (or Allow Remote Desktop first). Without that access, you could no longer connect to your VPS.
6. Restrict a port to your IP address
To make a sensitive service (SSH, database, admin tool) reachable only from your own connection:
- Add an Allow rule, direction Inbound, with the port (for example
22) and your address in Source address (My IP button). - Add a Block rule, direction Inbound, on the same port, with no source address.
If your IP address changes (home router, mobile connection), update the rule, or you will lose access to that port. If you get locked out, disable the firewall from the client area: access comes back straight away, and you can then fix your rules.
7. Block an unwanted address
To block an address that is attacking or spamming your server, add a Block rule, direction Inbound, protocol All, port empty, with that address in Source address. This block takes priority over your allow rules.
8. Manage your rules
In the Rules list, each rule can be paused (and resumed) or deleted.
Rules marked AtmosNode are security rules and cannot be changed. This includes blocking outgoing email on port 25, which protects our network against spam. If you need to send email directly from your VPS, open a ticket.
In what order rules apply
Rules are evaluated by priority, not in the order you created them:
- AtmosNode rules;
- blocks of a specific address;
- allow rules;
- general blocks.
This is what lets you allow a port for a single address, then block it for everyone else.
Good to know
- An open port only responds if an application is listening on it: if a test fails, first check that your service is running and that the operating system's firewall allows it too.
- Disabling the firewall does not delete your rules: they apply again as soon as you re-enable it.
- The number of rules per VPS is limited. If you make many changes in a short time, wait a few minutes before trying again.
