port not enabled despite setting the firewall rules for it

[shafman17]

i have enabled port forwarding of 3333 TCP in the firewall rules but when i check using yougetsignal the port is closed. same with port 30303-30315 Please help 

[VannGuce · Accepted solution]

Hi,

To make sure that the firewall rule is routing to the proper instance you can check the network tag. You can use this link[1][2] as a guidance on how you can double check the network tag in your VM instance and in your firewall rule.

Let me also share the documentation on how to configure firewall rules[3] for other checking on the configuration. Make sure also that the port is listening from your server, checking and commands may differ depending on what type of server you are using.

This link[4] will give you an idea on how they check their ports if it is listening or not. Even the port is already configured in your firewall but the port is not listening in your server, still the port will not be accessible.

[1]https://cloud.google.com/vpc/docs/add-remove-network-tags#using_tags_with_firewall_rules_and_routes
[2]https://cloud.google.com/vpc/docs/add-remove-network-tags#targets_for_firewall_rules
[3]https://cloud.google.com/firewall/docs/using-firewalls#console
[4]https://www.pico.net/kb/what-is-listening-on-a-tcp-port/

[shafman17]

here's a screenshot of me adding the network tag both for the VM and the firewall rule. still, port 3333 isn't listening. I'm using Ubuntu 22.04 for my instance and I checked using Nmap a