How to troubleshoot when the node is up but couldn't begin to sync block
Last updated
Last updated
In general, as long as the node is operational, it will begin to sync new blocks. However, there were a few unknown behaviors that prevented the block from synchronizing. As a result, this instruction will be helpful in resolving the issue of blocks not synchronizing once the node has been powered up.
The reason can come from the P2P port (default 30303) from the node had been blocked by the Firewall.
Solution: Rectify & Unblocked the port.
If the case that the firewall had been opened for the port. Then please try to run the node with the add-on command --nat extip:111.111.111.111 with 111.111.111.111 is the IP address to connect with internet (external network) of that node.
In case you are running the node via Docker, then you need to:
Open the port 30303 to internet for TCP/UDP
Docker should use the network mode host instead of bridge
Incorrect mapping port
Correct mapping port
The explanation for the network mode host is that Docker may use the port as long as it starts the container; it does not need to map to another port. This will result in improved performance as docker will no longer need to proxy traffic.
Example of the docker start command
Tips: If you are unsure whether your the port 30303 is opened or not, hence you can check it via port-checker online tools. For example:
If you are looking for other bootnodes, please refer to this
More detail for using the docker to run a node in mainnet can be found at the readme file
