Couldn't connect to the seed node error on Ubuntu AWS EC2

+2 votes

I have set up two Ubuntu instances on Amazon AWS EC2. I can ssh from one to the other. 

However following the getting started documentation, I cannot connect from one server to the other one. 

I have checked that `multichaind` is running and that the ports are open. Issuing `sudo netstat -ntlp | grep LISTEN` yields: 

tcp        0      0 127.0.0.1:7216          0.0.0.0:*               LISTEN      3241/multichaind
tcp        0      0 0.0.0.0:7217            0.0.0.0:*               LISTEN      3241/multichaind
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1166/sshd       
tcp6       0      0 ::1:7216                :::*                    LISTEN      3241/multichaind
tcp6       0      0 :::7217                 :::*                    LISTEN      3241/multichaind
tcp6       0      0 :::22                   :::*                    LISTEN      1166/sshd       

Still: When trying `multichaind chain1@<ipAddress>:7217` I get the typical error message: 

Error: Couldn't connect to the seed node <ipAddress> on port 7217 - please check multichaind is running at that address and that your firewall settings allow incoming connections.

Any thoughts?

 

asked Dec 16, 2016 by sascha

1 Answer

0 votes

Can you please run both multichaind nodes with the following extra flags:

-debug=mchn -debug=mchnminor -debug=net

Then let us know what you see in the debug.log files relating to the connection attempt.

You can also try connecting via telnet to the appropriate IP address and port, to see if it's open and receiving incoming connections.

answered Dec 16, 2016 by MultiChain
...