On Spain servers, your service's Security tab lets you tell the AntiDDoS filter what runs on each port, so it recognises that traffic properly. Everything is in the Filters sub-tab.
1. One click: "Popular services"
The first block creates every filter a service needs in one go:
| Service | Filters it creates |
|---|---|
| FiveM | TCP 30120 and UDP 30120 |
| Minecraft (Java) | TCP 25565 |
| Minecraft Bedrock | UDP 19132 |
| Web (HTTP + HTTPS) | TCP 80 and TCP 443 |
| SSH | TCP 22 |
| Remote Desktop (RDP) | TCP 3389 and UDP 3389 |
| MySQL / MariaDB | TCP 3306 |
| Ping (ICMP) | Ping replies |
Click yours, check in the window which filters it will create and confirm with Apply. If your server uses another port (for example FiveM on 30121) or you changed the remote desktop port, these will not fit: create a custom one. And use the MySQL one only if you really must reach the database from outside: normally 3306 should not be exposed.
2. Custom: "Create custom filter"
- Traffic type: TCP, UDP or Ping. If your game uses both protocols, create one filter for each.
- Which port? A single one, or a range by also filling in the second field (up to 10,000 consecutive ports).
- Protection level: the filtering profile. The list shows the ones available for that traffic type; pick the one that fits your game or service.
- Add notes (optional): so you remember what it is.
- Click Create filter.
You can have up to 300 filters per IP. Existing ones appear under Active filters, each with a Delete button.
Each game's ports
| Game | Filters |
|---|---|
| Rust | UDP 28015 and UDP 28017 |
| ARK: Survival Ascended | UDP 7777 |
| Counter-Strike 2 / Garry's Mod | UDP 27015 |
| Valheim | UDP 2456 to 2457 |
| Palworld | UDP 8211 |
| Project Zomboid | UDP 16261 to 16262 |
| 7 Days to Die | TCP 26900 and UDP 26900 to 26903 |
| Terraria | TCP 7777 |
The other sub-tabs
- Overview: a summary of active filters and recent attacks.
- IP Settings: advanced protection settings for your IP (scan detection, temporary blacklist, blocking by country or network...). The defaults suit almost everything. Do not change them unless you know exactly what you are doing: it is easy to lock out your own players.
- Rules: the platform's rules, read-only.
- Attacks: the attack history for that IP.
If something stops working after creating a filter
- Check the traffic type (TCP or UDP) and the port are the ones your server really uses.
- Delete the filter you just created and check whether it works again.
- Remember the filter does not open ports: the Windows or Linux firewall must let it through too.
If it still fails, open a ticket and tell us which filter you created.