I have an Ethereum node on a Amazon AWS instance. When I clone my node, it will generate with the same enode-ID
. When both machine try to connect to peers, they get race each other, so one of them able to connect to peers but other cannot.
[Q] How could I change my enodeID
on using geth
?
Solution for Parity
node:
Changing or removing the network key changes the enode address:
~/.local/share/io.parity.ethereum/network/key
You could increment the value by one or generate a new one or remove it and parity will take care of that.
I don't know how to do this approach on geth
.
enodeID
. @TC8enode://6f8a80d14311c39f35f516fa664deaaaa13e85b2f7493f37f6144d86991ec012937307647bd3b9a82abe2974e140724[email protected]:30303?discport=30301
i.e. a hexadecimal ID followed by an IP address and port number. If you run two nodes you'll need them on distinct IP/port combinations or they won't work properly. By changing the port number of one of them you won't change the hexadecimal part of the enode string but you will change the port numbers at the end, which should be all you need to avoid conflict