Here is a summary of the ports that need to be open (for more information see Requirements):
- Port TCP 1801 for outbound and inbound traffic.
- Ports TCP 1809 and 1810 for outbound traffic.
- Port HTTPS 443 for outbound traffic.
- Optional – Ports TCP 28332 and 28333 for RPC and Websocket traffic
If the Gateway is reporting a connectivity issue (in the Gateway status log), here are some general troubleshooting steps:
1. Verify the IP address of the blockchain node (as defined in
--enode). One way to verify is to examine the gateway_status log and search for the section “blockchain_nodes”, then the field “ip_address” in it. Let’s assume that this IP is
2. Verify that the Gateway is using the correct port (see the field “port” under “blockchain_nodes” in the gateway_status log). This port is established by either the
--enode or the
--blockchain-port flags. Let’s assume that this port is 30303.
netcat to test connectivity to the blockchain node:
$nc 22.214.171.124 30303 Connection to 126.96.36.199 30303 port [tcp/ssh] succeeded!
A connectivity problem will result in a connection refused or connection timed out:
connect to 188.8.131.52 port 30303 (tcp) failed: Connection refused connect to 184.108.40.206 port 30303 (tcp) failed: Connection timed out
To verify that the node is indeed listening on the correct port you can run the
netcat command locally on the node server. If you get a “succeeded!” message, this means the port is correct, but might not be open for external connections. In this case, a firewall may be blocking the connection.