Skip to main content

Firewall — Troubleshooting

This document provides guidance for resolving common issues when using the Firewall feature on FPT Cloud.

The Firewall menu does not appear in the interface​

Symptom: You navigate to a Specific VPC and go to the Network section in the navigation bar, but do not see the Firewall option.

Cause: The Firewall feature is only available to accounts that have been specially configured by FPT Cloud. Accounts that have not had this feature activated will not see the Firewall menu.

Resolution:

  • If you do not yet need network-level firewall capability, use Security Groups — this feature is available to all accounts on both General VPC and Specific VPC.
  • If you require the Firewall feature for specific enterprise needs, contact FPT Cloud support to request activation and account configuration.

Using a General VPC — Firewall is not supported​

Symptom: You cannot find the Firewall option even after searching the Network section of your VPC.

Cause: Firewall only works on Specific VPC. General VPC does not support this feature.

Resolution:

  • Confirm the type of VPC you are using by checking the VPC overview information (the Type or VPC type field).
  • If your VPC is a General VPC, use Security Groups to control traffic — Security Groups work on both VPC types.
  • If your business requirements call for a Specific VPC, contact FPT Cloud for advice on migration or creating a new VPC.

A rule was added but traffic is still blocked​

Symptom: You created a Firewall rule with an Allow action for a certain type of traffic, but the connection still fails.

Common causes and how to check:

CauseHow to check and resolve
Wrong rule directionConfirm you added the rule to the correct tab: traffic coming in from outside requires an Inbound rule; traffic going out from inside requires an Outbound rule.
Wrong protocolCheck the Protocol column of the rule. For example, if the application uses UDP but the rule only allows TCP, the connection will be blocked.
Wrong port or port rangeCheck the Port range column. Ensure the actual port used by the application falls within the range declared in the rule.
Source / destination address mismatchCheck the Source field (for Inbound rules) or the Destination field (for Outbound rules). To open traffic to all addresses, use 0.0.0.0/0.
Rule has a Pending or Error statusCheck the Status column of the rule. If it shows Pending, wait a few seconds and refresh the page. If it shows Error, try deleting and recreating the rule.
Rule overridden by a higher-priority Deny ruleReview the full rule list. If a Deny rule applies to the same traffic type with a higher priority, that rule takes precedence. Adjust the rule order or scope accordingly.

Cannot access Firewall even when using a Specific VPC​

Symptom: Your VPC is a Specific VPC, but the Firewall menu still does not appear, or you receive an access permission error when navigating to the Firewall page.

Possible causes:

  • Your account has not been configured by FPT Cloud to use the Firewall feature.
  • Your account does not have sufficient permissions to manage network resources in this VPC.

Resolution:

  1. Check with your internal administrator to confirm whether your account has been granted network management permissions in the corresponding VPC.
  2. If permissions are correctly assigned but Firewall still does not appear, contact FPT Cloud support and provide:
    • Your account name and organization ID.
    • The name and ID of the Specific VPC you are using.
    • A specific description of the issue you are experiencing.