Lock down your server's ports with the firewall
A firewall decides which network ports the world can reach. The goal is simple:
open only what you actually serve, block everything else. OrbixPanel manages
this for you on top of the standard Linux firewall (ufw).
The ports you normally want open
| Port | Service | Open to |
|---|---|---|
| 22 | SSH | you only (ideally your IP) |
| 80 | HTTP | everyone (redirects to HTTPS + SSL renewal) |
| 443 | HTTPS | everyone |
Mail, DNS, and other services open their own ports when you enable them. If you don’t run a service, its port should stay closed.
Manage it in the panel
In the Firewall tool you can allow or deny a port (TCP or UDP) and turn the firewall on or off. Each change applies immediately.
A safe starting policy:
- Allow 22, 80, 443.
- Enable the firewall.
- Leave everything else denied by default.
Don’t lock yourself out
Before enabling the firewall, make sure port 22 (SSH) is allowed — ideally restricted to your own IP. If you block SSH and you’re not in the panel, you can lose access to the server.
Rule of thumb
- Opening a port = inviting the internet to that service. Only open what’s hardened and needed.
- Database ports (MySQL 3306, PostgreSQL 5432, Redis 6379) should not be open
to the internet — apps reach them on
localhost. See Caching with Redis.
Next: Scan your sites for malware →
Running OrbixPanel? The firewall is managed from the panel. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.