Skip to content
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.

Sign up for GitHub

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

Jump to bottom

(Sokol) Update bootnodes #143

Merged
merged 2 commits into from
Apr 7, 2020
Merged

(Sokol) Update bootnodes #143

merged 2 commits into from
Apr 7, 2020

Conversation

varasev
Copy link
Contributor

@varasev varasev commented Apr 6, 2020

The connection was checked with nc -vz [host] [port].

Please check

enode://77fe2f11606874677697f1e861264b0566458381a04f8cd280e6ba300bb56bb0cd884cdc44f6f58ac086d83d8c05ca0aea245808a2c3c32c8be897ae1370bbbb@104.248.49.16:30303

enode://e08adce358fc26dfbe1f24ee578dceaa29575ca44a39d9041203131db5135aceba6241840a9b57b1540eeaf7b4eff1aead28a74641be43342c35af454abb31b3@199.247.18.10:30313

Couldn't connect to them.

@varasev varasev requested a review from igorbarinov April 6, 2020 14:02
@igorbarinov
Copy link
Member

let's remove the first one 104.248.49.16:30303 (nethermind enodes are not sustainable after container restart)
the second one is fixed (opened firewall to a non-standard port)

@varasev
Copy link
Contributor Author

varasev commented Apr 7, 2020

let's remove the first one 104.248.49.16:30303 (nethermind enodes are not sustainable after container restart)

Ok, done: 4af2f7d

@varasev varasev merged commit 254ac17 into sokol Apr 7, 2020
@varasev varasev deleted the sokol-update-bootnodes-20200406 branch April 7, 2020 06:29
@varasev varasev mentioned this pull request Apr 7, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@igorbarinov igorbarinov igorbarinov approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@varasev @igorbarinov