.svg)
.svg)
If enabling the LifeinCloud firewall causes connectivity problems, don’t worry. This guide lists the most common issues, recovery methods, and best practices to keep your VPS secure and accessible.
Locked out after enabling firewall
If you enabled the firewall without adding SSH (Linux) or RDP (Windows) rules first, you may lose access.
- Go back to your LifeinCloud client area → VPS → Firewall.
- Disable the firewall completely, or add an allow rule for SSH/RDP.
- Reconnect to your server and reapply a safer set of rules.
Always add admin port rules before switching the firewall on.
Websites or services not reachable
If your site or app stopped responding after enabling firewall:
- Check that the correct ports are open (e.g., 80/443 for web, 25/465/587 for SMTP).
- Confirm whether the service uses TCP, UDP, or both (e.g., some games need UDP).
- For IPv6-enabled VPS, make sure you’ve added matching IPv6 rules.
If unsure, temporarily allow from 0.0.0.0/0 (anywhere), test, then tighten rules again.
Firewall conflicts with internal rules
It’s fine to run iptables, firewalld, or ufw inside your VPS in addition to the LifeinCloud firewall, but conflicts can cause blocked traffic. Remember:
- LifeinCloud firewall runs before traffic reaches your server.
- If LifeinCloud drops a packet, your VPS never sees it.
- Keep both sets of rules consistent to avoid confusion.
Recommendation: Keep critical filtering at LifeinCloud firewall, and use VPS firewall for fine-grained controls.
How to test & diagnose firewall issues
- Check open ports:
nmap -Pn YOUR.SERVER.IP
- Check service reachability:
nc -vz YOUR.SERVER.IP 443
- Check from inside VPS: Verify the service is running and listening with
ss -tulpnornetstat -tulpn.
This helps you know whether the issue is firewall-related or service-related.
Best practices to avoid problems
- Always add SSH/RDP rules first.
- Keep a second terminal session open while testing changes.
- Document your firewall rules for clarity and audits.
- When in doubt, disable firewall, regain access, then reapply carefully.
