New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add your client as a bootnode #1
Comments
enode://be62cf8128c575215ef2dd510eebb09e308a6a76e8cfc19e21d4b6b9180476d8aebbae8a48291847b36b8b0c1688951ad920c6221ea821b0f646a4a6a4469ca6@127.0.0.1:30303 |
enode://cde0932df8adb3ac234ff0b9614539a95639701e5bb94bcb5cb180bc1633cad20b4aa48c9e04826f9e811be59e2ce39ad65534ea659fef483abdd90ab3d12ad3@127.0.0.1:30303 |
enode://fd124720dcf3a1cf783e8aac3a88a3699fc5665554eda8f179b7fee8b1566062b326576c741401b305a95fb063b2361e54b432bd2854ed5d6ca39ecd12c31290@127.0.0.1:30303 |
@gavrilo77 Those address seems not to have a public IP address -- it has the loopback address 127.0.0.1. So unfortunately, other clients will not be able to connect to it and it cannot act as a bootnode. 😢 If you are sure that you have a public IP address, please check your router's NAT settings. Make sure the enode address you get is anything other than 127.0.0.1 or in the private IPv4 address space. |
@DragonFyZex As said above, please make sure the enode address you get is anything other than 127.0.0.1 or in the private IPv4 address space. Otherwise, clients won't be able to connect to your node. |
enode://9215ad77bd081e35013cb42a8ceadff9d8e94a78fcc680dff1752a54e7484badff0904e331c4b40a68be593782e55acfd800f076d22f9d2832e8483733ade149@213.14.82.125:30303 |
Thanks @sstercan! Added. |
Singapore Node by digitalocean |
Thanks @ultramenid! Added. |
We've had enough bootnode as of now. Thanks for everyone's help! If you still want your client added as a bootnode, please feel free to continue to comment on this issue. |
If you have a long-running Parity client, please share the enode URI to add it as a bootnode.
Your enode URI will be displayed when you start your Parity client, and it is in the format of
enode://816bff950121884a5de03332d6a1dd67d89c9a99fa85338148b47f33378b1093e532ab5e63bafe156c568d270fe43c30d62c690481799c62414ac996d5908755@108.61.198.224:30303
.The text was updated successfully, but these errors were encountered: