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.

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

Closed
bansatya opened this issue Jun 15, 2018 · 5 comments

Comments

@bansatya
Copy link

bansatya commented Jun 15, 2018

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:

root@ip-172-31-21-97:~# puppeth --loglevel 4
+-----------------------------------------------------------+
| Welcome to puppeth, your Ethereum private network manager |
|                                                           |
| This tool lets you create a new Ethereum network down to  |
| the genesis block, bootnodes, miners and ethstats servers |
| without the hassle that it would normally entail.         |
|                                                           |
| Puppeth uses SSH to dial in to remote servers, and builds |
| its network components out of Docker containers using the |
| docker-compose toolset.                                   |
+-----------------------------------------------------------+

Please specify a network name to administer (no spaces, please)
> test
Sweet, you can set this via --network=test next time!

INFO [06-15|11:16:59] Administering Ethereum network           name=test
WARN [06-15|11:16:59] No previous configurations found         path=/home/ubuntu/.puppeth/test

What would you like to do? (default = stats)
 1. Show network stats
 2. Configure new genesis
 3. Track new remote server
 4. Deploy network components
> 4

What would you like to deploy? (recommended order)
 1. Ethstats  - Network monitoring tool
 2. Bootnode  - Entry point of the network
 3. Sealer    - Full node minting new blocks
 4. Wallet    - Browser wallet for quick sends (todo)
 5. Faucet    - Crypto faucet to give away funds
 6. Dashboard - Website listing above web-services
> 1

Which server do you want to interact with?
 1. Connect another server
> 1

Please enter remote server's address:
> 35.176.198.237
DEBUG[06-15|11:17:15] Attempting to establish SSH connection   server=35.176.198.237
The authenticity of host '35.176.198.237:22 (35.176.198.237:22)' can't be established.
SSH key fingerprint is b1:f9:47:11:74:8e:d1:c0:b1:85:e9:6f:c3:62:f7:e8 [MD5]
Are you sure you want to continue connecting (yes/no)? yes
DEBUG[06-15|11:17:18] Verifying if docker is available         server=35.176.198.237
DEBUG[06-15|11:17:29] Verifying if docker-compose is available server=35.176.198.237

Which port should ethstats listen on? (default = 80)
>

Allow sharing the port with other services (y/n)? (default = yes)
>
INFO [06-15|11:28:24] Deploying nginx reverse-proxy            server=35.176.198.237 port=80
Please login as the user "ubuntu" rather than the user "root".


Proxy deployed, which domain to assign? (default = 35.176.198.237)
>

What should be the secret password for the API? (must not be empty)
> test

Keep existing IP [] blacklist (y/n)? (default = yes)
>
Please login as the user "ubuntu" rather than the user "root".

INFO [06-15|11:29:41] Starting remote server health-check      server=35.176.198.237
DEBUG[06-15|11:29:41] Checking for nginx availability          server=35.176.198.237
DEBUG[06-15|11:29:51] Checking for ethstats availability       server=35.176.198.237
DEBUG[06-15|11:30:01] Checking for bootnode availability       server=35.176.198.237
DEBUG[06-15|11:30:11] Checking for sealnode availability       server=35.176.198.237
DEBUG[06-15|11:30:22] Checking for faucet availability         server=35.176.198.237
DEBUG[06-15|11:30:32] Checking for dashboard availability      server=35.176.198.237
+----------------+----------------+--------+-----------+------------------------------------------------------+
|     SERVER     |       IP       | STATUS |  SERVICE  |                       DETAILS                        |
+----------------+----------------+--------+-----------+------------------------------------------------------+
| 35.176.198.237 | 35.176.198.237 | online | dashboard | invalid character 'P' looking for beginning of value |
|                |                | online | nginx     | invalid character 'P' looking for beginning of value |
|                |                | online | ethstats  | invalid character 'P' looking for beginning of value |
|                |                | online | bootnode  | invalid character 'P' looking for beginning of value |
|                |                | online | sealnode  | invalid character 'P' looking for beginning of value |
|                |                | online | faucet    | invalid character 'P' looking for beginning of value |
+----------------+----------------+--------+-----------+------------------------------------------------------+

What would you like to do? (default = stats)
 1. Show network stats
 2. Configure new genesis
 3. Manage tracked machines
 4. Manage network components
> 4

 1. Tear down Faucet on 35.176.198.237
 2. Tear down Dashboard on 35.176.198.237
 3. Tear down Nginx on 35.176.198.237
 4. Tear down Ethstats on 35.176.198.237
 5. Tear down Bootnode on 35.176.198.237
 6. Tear down Sealnode on 35.176.198.237
 7. Deploy new network component
> ^C
root@ip-172-31-21-97:~# puppeth --loglevel 4
+-----------------------------------------------------------+
| Welcome to puppeth, your Ethereum private network manager |
|                                                           |
| This tool lets you create a new Ethereum network down to  |
| the genesis block, bootnodes, miners and ethstats servers |
| without the hassle that it would normally entail.         |
|                                                           |
| Puppeth uses SSH to dial in to remote servers, and builds |
| its network components out of Docker containers using the |
| docker-compose toolset.                                   |
+-----------------------------------------------------------+

Please specify a network name to administer (no spaces, please)
> 1
Sweet, you can set this via --network=1 next time!

INFO [06-15|11:34:50] Administering Ethereum network           name=1
WARN [06-15|11:34:50] No previous configurations found         path=/home/ubuntu/.puppeth/1

What would you like to do? (default = stats)
 1. Show network stats
 2. Configure new genesis
 3. Track new remote server
 4. Deploy network components
> 4

What would you like to deploy? (recommended order)
 1. Ethstats  - Network monitoring tool
 2. Bootnode  - Entry point of the network
 3. Sealer    - Full node minting new blocks
 4. Wallet    - Browser wallet for quick sends (todo)
 5. Faucet    - Crypto faucet to give away funds
 6. Dashboard - Website listing above web-services
> 1

Which server do you want to interact with?
 1. Connect another server
> 1

Please enter remote server's address:
> 35.176.198.237
DEBUG[06-15|11:35:03] Attempting to establish SSH connection   server=35.176.198.237
The authenticity of host '35.176.198.237:22 (35.176.198.237:22)' can't be established.
SSH key fingerprint is b1:f9:47:11:74:8e:d1:c0:b1:85:e9:6f:c3:62:f7:e8 [MD5]
Are you sure you want to continue connecting (yes/no)? yes
DEBUG[06-15|11:35:07] Verifying if docker is available         server=35.176.198.237
DEBUG[06-15|11:35:17] Verifying if docker-compose is available server=35.176.198.237

Which port should ethstats listen on? (default = 80)
> 1
^C
root@ip-172-31-21-97:~# puppeth --loglevel 4
+-----------------------------------------------------------+
| Welcome to puppeth, your Ethereum private network manager |
|                                                           |
| This tool lets you create a new Ethereum network down to  |
| the genesis block, bootnodes, miners and ethstats servers |
| without the hassle that it would normally entail.         |
|                                                           |
| Puppeth uses SSH to dial in to remote servers, and builds |
| its network components out of Docker containers using the |
| docker-compose toolset.                                   |
+-----------------------------------------------------------+

Please specify a network name to administer (no spaces, please)
> test
Sweet, you can set this via --network=test next time!

INFO [06-15|11:38:13] Administering Ethereum network           name=test
INFO [06-15|11:38:13] Dialing previously configured server     server=35.176.198.237
DEBUG[06-15|11:38:13] Attempting to establish SSH connection   server=35.176.198.237

DEBUG[06-15|11:38:14] Verifying if docker is available         server=35.176.198.237
DEBUG[06-15|11:38:24] Verifying if docker-compose is available server=35.176.198.237
INFO [06-15|11:38:34] Starting remote server health-check      server=35.176.198.237
DEBUG[06-15|11:38:34] Checking for nginx availability          server=35.176.198.237
DEBUG[06-15|11:38:44] Checking for ethstats availability       server=35.176.198.237
DEBUG[06-15|11:38:55] Checking for bootnode availability       server=35.176.198.237
DEBUG[06-15|11:39:05] Checking for sealnode availability       server=35.176.198.237
DEBUG[06-15|11:39:15] Checking for faucet availability         server=35.176.198.237
DEBUG[06-15|11:39:25] Checking for dashboard availability      server=35.176.198.237
+----------------+----------------+--------+-----------+------------------------------------------------------+
|     SERVER     |       IP       | STATUS |  SERVICE  |                       DETAILS                        |
+----------------+----------------+--------+-----------+------------------------------------------------------+
| 35.176.198.237 | 35.176.198.237 | online | nginx     | invalid character 'P' looking for beginning of value |
|                |                | online | ethstats  | invalid character 'P' looking for beginning of value |
|                |                | online | bootnode  | invalid character 'P' looking for beginning of value |
|                |                | online | sealnode  | invalid character 'P' looking for beginning of value |
|                |                | online | faucet    | invalid character 'P' looking for beginning of value |
|                |                | online | dashboard | invalid character 'P' looking for beginning of value |
+----------------+----------------+--------+-----------+------------------------------------------------------+

What would you like to do? (default = stats)
 1. Show network stats
 2. Configure new genesis
 3. Manage tracked machines
 4. Manage network components
> INFO [06-15|11:39:36] Starting remote server health-check      server=35.176.198.237
DEBUG[06-15|11:39:36] Checking for nginx availability          server=35.176.198.237
DEBUG[06-15|11:39:46] Checking for ethstats availability       server=35.176.198.237
DEBUG[06-15|11:39:56] Checking for bootnode availability       server=35.176.198.237
DEBUG[06-15|11:40:06] Checking for sealnode availability       server=35.176.198.237
DEBUG[06-15|11:40:17] Checking for faucet availability         server=35.176.198.237
DEBUG[06-15|11:40:27] Checking for dashboard availability      server=35.176.198.237
+----------------+----------------+--------+-----------+------------------------------------------------------+
|     SERVER     |       IP       | STATUS |  SERVICE  |                       DETAILS                        |
+----------------+----------------+--------+-----------+------------------------------------------------------+
| 35.176.198.237 | 35.176.198.237 | online | ethstats  | invalid character 'P' looking for beginning of value |
|                |                | online | bootnode  | invalid character 'P' looking for beginning of value |
|                |                | online | sealnode  | invalid character 'P' looking for beginning of value |
|                |                | online | faucet    | invalid character 'P' looking for beginning of value |
|                |                | online | dashboard | invalid character 'P' looking for beginning of value |
|                |                | online | nginx     | invalid character 'P' looking for beginning of value |
+----------------+----------------+--------+-----------+------------------------------------------------------+

What would you like to do? (default = stats)
 1. Show network stats
 2. Configure new genesis
 3. Manage tracked machines
 4. Manage network components

System information

Geth version: 1.7.2-stable
OS & Version: Linux ( Ubuntu16.04)
Commit hash : (if develop)

@Bitmaudit
Copy link

Bitmaudit commented Jan 5, 2019

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:

Which server do you want to interact with?
 1. Connect another server
> 1

What is the remote server's address ([username[:identity]@]hostname[:port])?
> root@5.189.165.23
What's the decryption password for /root/.ssh/id_rsa? (won't be echoed)
>

The authenticity of host '5.189.165.23:22 (5.189.165.23:22)' can't be established.
SSH key fingerprint is 5c:1e:73:e6:38:91:82:54:63:03:c2:f6:c5:47:c4:60 [MD5]
Are you sure you want to continue connecting (yes/no)? y


-------------------------------------------------------
ERROR[01-05|14:34:51.771] Server not ready for puppeth err="ssh: handshake failed: unknown auth choice: n\y"
------------------------------------------------------------------------

@softstack
Copy link

softstack commented Sep 13, 2019

Are you able to login via ssh to your node ?

ssh username@IP
ex. ssh ubuntu@10.122.0.5

If not connect to the node via ssh first

  1. ssh-copy-id 0.0.0.0

if this not work disable temporary
Log in as root
Edit ssh config:
sudo nano /etc/ssh/sshd_config
Change this line:
PasswordAuthentication no
to
PasswordAuthentication yes
Restart daemon:
sudo systemctl restart sshd

Do ssh-copy-id:
ssh-copy-id someuser@

Revert changes to ssh_config if you are security conscious and restart daemon.

@karalabe
Copy link
Member

@Bitmaudit You need to explicitly type yes, not just y. Maybe we should accept both or make the error message more meaningful.

@karalabe
Copy link
Member

@bansatya You seem to be getting error returns Please login as the user "ubuntu" rather than the user "root".. When connecting to your server do ubuntu@IP

@Bitmaudit
Copy link

Bitmaudit commented Nov 21, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants