-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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
Getting issues - while setting up Ethereum network in AWS instances using puppeth #16997
Comments
Hello after installing go ethereum and geth, I configured a bootode, and 3 nodes sealers I created a POA and started the nodes with json files; everything works, but when I try to install ethstat with puppeth, I receive the following error:
|
Are you able to login via ssh to your node ? ssh username@IP If not connect to the node via ssh first
if this not work disable temporary Do ssh-copy-id: Revert changes to ssh_config if you are security conscious and restart daemon. |
@Bitmaudit You need to explicitly type |
@bansatya You seem to be getting error returns |
Yes! Now i know...thanks
Grazie.
ing. Tommaso Coppola
Il gio 21 nov 2019, 11:00 Péter Szilágyi <notifications@github.com> ha
scritto:
… @Bitmaudit <https://github.com/Bitmaudit> You need to explicitly type yes,
not just y. Maybe we should accept both or make the error message more
meaningful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16997?email_source=notifications&email_token=AKU2T5JP5HFVWONCBULLPGDQUZL25A5CNFSM4FFGBJA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEZUXMY#issuecomment-557009843>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKU2T5LHIOSWZGC5GTJDGZDQUZL25ANCNFSM4FFGBJAQ>
.
|
HI,
I am facing issues while trying to setup private network using Puppeth between two AWS ubuntu instance . Initial issue was related to connection as below..
ERROR[06-15|10:27:01] Server not ready for puppeth err="ssh: handshake failed: ssh: unable to authenticate, attempted methods [none], no supported methods remain"
This is resolved once the private key of other m/c explicitly added to the other m/c in form of id_rsa file under .ssh folder.
However, while deployed nginex or other template , there is some generic issues. Details are in below log:
System information
Geth version: 1.7.2-stable
OS & Version: Linux ( Ubuntu16.04)
Commit hash : (if
develop
)The text was updated successfully, but these errors were encountered: