Ethereum: Geto port change causes disruption
The latest Ethereum client update has changed the port used for discovery of Geto nodes. Initially, users were using the default port of 30303, but an unexpected change occurred after installing version 1.13.14.
As reported by several users on the Ethereum subreddit and other online forums, Geto nodes were now listening for connections on port 1024 instead of the usual default port of 30304. This change may seem minor at first glance, but it can cause major problems for users who rely on this discovery feature.
Problem: Discovery Port Change
To summarize, when you run « ./geth » with the command line options:
»bash
./geth –port 30303 –discovery.port 30304 –http –http.api eth,net,engine,admin –authrpc.jwtsecret ~/myhex.hex –datadir=’~/ethereum/execution/data’
« `
Initially, node looks for connections on port 30304. However, shortly after node starts, it starts looking for connections on port 1024.
Causes and Effects
There are several reasons for this unexpected change:
- Malconfigured configuration files: One or more of your system configuration files (e.g., « geth.conf », « etherscan.io/config.json ») may have incorrect settings that caused the port to change.
- Node update issues
: A recent update changed the behavior of the Geth node, causing the discovery port to change unexpectedly.
Workarounds and Solutions
To resolve this issue:
- Check configuration files: Review your system configuration files for incorrect settings that may have caused the port to change.
- Update Geth: If you are using a recent version of Geth (e.g., 1.14.x), update to the latest version to ensure that you are using the correct default discovery port.
Conclusion
A small but important change to the Geto discovery port has caused confusion among Ethereum users who rely on this feature. If you have encountered a node or have experience with configuration files, it is imperative to investigate and eliminate any anomalies that may be causing this unexpected behavior.