--blockchain-ip[Python Gateway] or
--enodes[Go Gateway]) Let’s assume that this IP is
--blockchain-port[Python Gateway] or the
--enodes[Go Gateway] flags. Let’s assume that this port is 30303.
netcatto test connectivity to the blockchain node:
netcatcommand 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.
--enodethat doesn’t match the IP of your node, the Gateway will not be able to connect. To verify what IP is in use, please look at the Gateway_status.log file under analysis -> network -> blockchain_nodes -> ip_address. Alternatively, you can use the
bloxroute-cliwith the argument DETAILED to show the same information.
bloxroute-cliGateway_status DETAILED command and look for analysis -> network -> blockchain_nodes -> port.
--node-public-keyGateway startup argument will lead to the Ethereum node closing the Gateway connection. To verify that the Gateway is using the correct node public key, you can run the following command:
--blockchain-portargument. Default p2p port is 30303 for Ethereum client.