Registered · Cross-platform

9229 Node.js debugger

TCP Unofficial
UDP
SCTP
DCCP

What it is

Node.js inspector/debug port.

When / why

Local Node debugging. Never expose — allows code execution.

Protocol status detail

TransportStatusMeaning
TCP Unofficial Not assigned by IANA, but standardized, specified, or widely used on this port.
UDP Not applicable for this transport.
SCTP Not applicable for this transport.
DCCP Not applicable for this transport.

Port range

Registered (1024–49151). Assigned by IANA on request; usable without elevated privileges on most systems.

Browse all ports →

Firewall rules for port 9229

Copy-ready inbound rules for the active transports. Replace every <source> placeholder with the specific host, subnet, or CIDR that should reach this port.

⚠ High exposure risk — this service should never be reachable from untrusted networks. Scope the rule to a management subnet or VPN.

ufw

sudo ufw allow proto tcp from <source> to any port 9229

Allow TCP 9229 (Node.js debugger). Replace <source> with the network/host that should reach it.

firewalld

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<source>" port port="9229" protocol="tcp" accept'

Allow TCP 9229 (Node.js debugger) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

nft add rule inet filter input ip saddr <source> tcp dport 9229 accept

Allow TCP 9229 (Node.js debugger). Assumes table 'inet filter' with an 'input' chain.

iptables

sudo iptables -A INPUT -p tcp -s <source> --dport 9229 -j ACCEPT

Allow TCP 9229 (Node.js debugger). Persist with iptables-save/netfilter-persistent.

Azure NSG

az network nsg rule create -g <resource-group> --nsg-name <nsg> -n Allow-nodejsdebugger-9229 --priority 1000 --access Allow --direction Inbound --protocol TCP --source-address-prefixes <source> --destination-port-ranges 9229

Inbound rule for 9229 (Node.js debugger). Set <source> to a CIDR; lower priority number = higher precedence.

AWS Security Group

aws ec2 authorize-security-group-ingress --group-id <sg-id> --ip-permissions IpProtocol=tcp,FromPort=9229,ToPort=9229,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 9229 (Node.js debugger). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

gcloud compute firewall-rules create allow-nodejsdebugger-9229 --direction=INGRESS --action=ALLOW --rules=tcp:9229 --source-ranges=<source-cidr> --network=<network>

Ingress rule for 9229 (Node.js debugger). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow Node.js debugger 9229/TCP" dir=in action=allow protocol=TCP localport=9229 remoteip=<source>

Inbound TCP 9229 (Node.js debugger). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow Node.js debugger 9229/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 9229 -RemoteAddress <source>

Inbound TCP 9229 (Node.js debugger). Replace <source> with a host or subnet.

Rules are generated only for transports marked active for this port. They default to an inbound allow with an explicit source placeholder — never any. Review direction, scope, and rule precedence before applying in production.