Ethereum: Change of port of Geth causes disruption
A recent Ethereum client update has introduced a change in the Discovery port for the Geth Node. Users initially used the default port 30303, but after installing the version 1.13.14 there was an unexpected change.
As reported by several users on Ethereum Subreddit and other online forums, the Geth knot has now discovered connections to Porto 1024 instead of its usual default port 30304. Discovery.
Problem: Changing the Discovery port
To summarize it when you run ./Geth with the command line options:
`Bash
./geth -Port 30303 -dishes. ‘
`
The node initially appears connections to the port 30304. Shortly after the node starts, it will start to discover the connection on the port 1024 instead.
Causes and consequences
There are several possible reasons for this unexpected change:
1
- Nod update problems : The last update could introduce changes in the behavior of the Geth node, causing this unexpected change of the Discovery port.
Solution and solutions
Solving this problem:
- Check the configuration files : Check your system configuration files for incorrect settings that could cause port change.
- GETH
update: If you are using the latest version of Geth (eg 1.14.x), update to the latest version to make sure you start the correct default Discovery port.
Conclusion
A small but important change in the Discovery port for Geth caused a stir among Ethereum users who rely on this feature. If you have encountered problems with your node or have experience with configuration files, it is necessary to investigate and solve any irregularities that could cause this unexpected behavior.
Leave a Reply