How to Use the TudCloud VPS Control Panel Firewall

Create narrowly scoped firewall rules while preserving a tested route back into your server.

Know which firewall you are editing

The control-panel firewall and the firewall inside your operating system are separate layers. A connection must pass both. Plan rules around the actual services and addresses you use, rather than treating a panel rule as proof that the application is reachable.

Create a rule deliberately

1. Select the correct VPS and open the available Firewall section. Preserve a copy or screenshot of the current policy.
2. Identify the rule direction, address family, action, protocol, port, and source or destination address. The tutorial interface exposes Direction, IP Type, Decision, Protocol, Port, IP, and Note fields.
3. Start with the allow rules needed for administration. Where supported, restrict administration to your trusted address or VPN range. A single IPv4 address uses /32; an IPv6 address uses /128.
4. Add public application ports only when the workload needs them. A website typically needs TCP 80 and 443; its database usually does not need public access.
5. Add the rule, save the policy, and complete any separate apply or attach step presented by your panel. Review rule ordering and the default policy before blocking anything.

Test allowed and blocked traffic

Open a second SSH or RDP session from an allowed source. Test the public website from another network. Check IPv6 separately if the server has an IPv6 address. A rule for IPv4 alone does not describe the IPv6 policy.

Recover from a lockout

Use the provider console or the panel policy editor to restore the last working rule. If you do not know how that platform orders rules, check its help or contact support before adding conflicting allow and deny entries. Do not disable every protection just to make one port work.

Keep learning

Browse the complete TudCloud video tutorial library or explore server security guides.