Ethereum: The change in Geth port causes disturbances
Recently, the Ethereum customer update has introduced a change at the Geth node’s discovery gate. Initially, the users used the 30303 default port, but after 1.13.14, an unexpected change occurred.
As several Ethereum Subredit users and other online forums have stated, the Geth node has now found connections in the gate instead of the 1024 30304 default port. At first glance, this change may seem low, but can cause significant problems. Users who trust this discovery function.
Problem: Discovery Port Change
Summary: When /Geth performs command line settings:
`Bash
“
`
The knot will initially find connections to the gate 30304. Shortly after starting the knot, he begins to find contact in the port 1024.
Causes and Consequences
There are some possible reasons for this unexpected change:
- The specified configuration files : It is possible that system configuration files (for example:
Get.conf,` Etherscan.io/Config.json) contain false settings that have led to a gate change.
- Node Update Problems : Recently, the update could have made changes to the Geth node behavior, which caused this unexpected discovery gate change.
Solution and Solutions
Solving the problem:
- Check the configuration files : Check the system configuration files for any wrong setting that causes the gate change.
- Update Geth : If you are using Geth’s latest version (such as 1.14.x), update to the latest version to be performed with the appropriate default setting port.
conclusion
A small but important change at the Geth Discovery port, raised by Ethereum users who trust this function. If you have problems with the node or have experience with determination files, it is necessary to study and solve differences that can cause this unexpected behavior.