Registered · Cross-platform

8332 Bitcoin JSON-RPC

TCP Unofficial
UDP
SCTP
DCCP

What it is

Bitcoin node RPC API.

When / why

Wallet/node control. Keep loopback-only.

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 8332

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

ufw

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

Allow TCP 8332 (Bitcoin JSON-RPC). 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="8332" protocol="tcp" accept'

Allow TCP 8332 (Bitcoin JSON-RPC) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

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

Allow TCP 8332 (Bitcoin JSON-RPC). Assumes table 'inet filter' with an 'input' chain.

iptables

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

Allow TCP 8332 (Bitcoin JSON-RPC). Persist with iptables-save/netfilter-persistent.

Azure NSG

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

Inbound rule for 8332 (Bitcoin JSON-RPC). 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=8332,ToPort=8332,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 8332 (Bitcoin JSON-RPC). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

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

Ingress rule for 8332 (Bitcoin JSON-RPC). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow Bitcoin JSON-RPC 8332/TCP" dir=in action=allow protocol=TCP localport=8332 remoteip=<source>

Inbound TCP 8332 (Bitcoin JSON-RPC). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow Bitcoin JSON-RPC 8332/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 8332 -RemoteAddress <source>

Inbound TCP 8332 (Bitcoin JSON-RPC). 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.