Firewall
Manage server firewall rules without locking out required services.
1Overview
Firewall controls network access to the server. Rules can allow or block addresses, ports, and services according to the panel’s protected configuration.
2Before you begin
Administrator actions can affect multiple customer accounts and server services. This is a security-sensitive task; use the narrowest change that solves the verified issue.
Keep a second administrator connection available so you can recover if a rule blocks the current session.
3Step-by-step workflow
Open Firewall, inspect existing rules, add the narrowest required source address and service, save, and confirm from an independent connection. Use the audit or status feedback after each change.
- Open Firewall and read the backend and Active or Inactive state first.
- Review the complete current rules, including allowed and blocked ports, protocols, and source addresses.
- Confirm the actual SSH, administrator-panel, and user-panel ports before changing access.
- Add one allow or deny rule with the required port, protocol, and source restriction.
- Check the saved rule and test it from a separate connection.
- If the firewall is inactive, remember that saved rules do not provide active filtering.
- Enable the firewall only after required access is allowed and you have a provider-console recovery route.
- Review and remove temporary rules after the task is complete, retaining permanent hosting rules.
4Practical example
Example: explicit encrypted FTP uses a control port and a passive-transfer range. Allowing only the control port can permit a login while directory listings and transfers still fail.
5Verify the result
Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.
- Confirm required services remain reachable from expected networks.
- Confirm the new rule appears exactly once and does not duplicate a broader rule.
6Common problems and what to check
The rule list is empty: check the reported backend, loading result, and active versus saved configuration.
A service stops connecting: check protocol, source restriction, rule order, and the provider firewall.
The panel reports Inactive: the package may be installed and its rules saved even though the firewall service is off.
7Security, impact, and rollback
Keep current administrator access and panel ports reachable before saving. Broad allow rules and accidental blocks can expose or lock down the server.