.svg)
.svg)
The LifeinCloud firewall adds an extra layer of protection to your VPS by controlling which network traffic is allowed or denied before it reaches your server. It helps secure your services, prevent unauthorized access, and reduce attack risks.
What is the LifeinCloud Firewall?
The firewall is a security system built into your VPS management platform. It filters incoming and outgoing traffic at the virtualization level, meaning rules are applied before any packets reach your operating system.
This makes the LifeinCloud firewall stronger than relying only on internal tools such as iptables or ufw, since blocked traffic never reaches your server in the first place.
Default behavior
- By default, the firewall is disabled, which means all ports are open.
- When you enable it, the default policy is to block all traffic unless a rule allows it.
- You control which ports and protocols are permitted (e.g., SSH, HTTP, HTTPS).
This gives you maximum flexibility: your VPS is open for quick access at first, and you can later tighten security by enabling the firewall and adding rules.
Why should you use the firewall?
- Limit exposure: Only allow the ports you actually need (e.g., 22, 80, 443).
- Stop brute force attacks: Block all SSH except from your trusted IPs.
- Protect services: Keep databases or admin panels accessible only from private networks or specific addresses.
- Safer defaults: Dropping all unused ports reduces your attack surface automatically.
Use case examples
Secure web server
- Allow TCP 22 (SSH) only from your office IP
- Allow TCP 80 (HTTP) from anywhere
- Allow TCP 443 (HTTPS) from anywhere
- Drop all other traffic
Windows VPS
- Allow TCP 3389 (RDP) only from your IP
- Allow TCP 80 and 443 for web traffic (if hosting websites)
- Drop all other ports
Game server
- Allow TCP/UDP 25565 (Minecraft default port)
- Drop all other traffic except SSH/RDP for administration
Best practices
- Always add SSH (Linux) or RDP (Windows) rules before enabling the firewall.
- Test access with a second session before saving permanent rules.
- Start with open rules, then tighten gradually to avoid lockouts.
- Restrict sensitive ports (e.g., SSH, databases) to trusted IPs only.
