Couldn't connect to the seed node

Question

Hi, hopefully someone can help me: I am trying to set up a sample chain on ubuntu 14.04. The Multichain is running on a aws ubuntu, have done the "Getting started stuff" and like now to connect from another node to it with multichaind. I always get this answer:

Retrieving network parameters from the seed node 52.89.90.67:7195 ...
Error: Couldn't connect to the seed node 52.89.90.67 on port 7195 - please check your firewall settings or contact your network administrator.

When I telnet to this port on the node, I have a connect, so there is no FW setting wrong. Anyone an idea?

Running MultiChain Core Daemon build 1.0 alpha 7 protocol 10002

thanks! jp

Answer 1

Generally this is a firewall problem but I'm not sure in your case. Did you try telnetting from the same source as the node you're trying to connect from?

If this problem persists you may want to try setting the default-network-port in the params.dat file to a port which you know is open on your network (e.g. 80), before starting the chain running.

Comments

Hi Gideon,
I do:
azureuser@swissminer:~$ telnet 52.89.90.67 7195
Trying 52.89.90.67...
and get following answer:
MultiChain Core Daemon build 1.0 alpha 7 protocol 10002

So, there is no FW Problem and the daemon is running.

So the full error Message when trying to connect from Swissminer to Blockchain via multichaind:
azureuser@swissminer:~$ multichaind  swisscoin@52.89.90.67:7195

MultiChain Core Daemon build 1.0 alpha 7 protocol 10002

Retrieving network parameters from the seed node 52.89.90.67:7195 ...
Error: Couldn't connect to the seed node 52.89.90.67 on port 7195 - please check your firewall settings or contact your network administrator.

So, the multichaind CAN connect to the node, because the node answers with "MultiChain Core Daemon...."

or I am wrong??

---

It sounds like you are right and we will need to look into why it is not working in your specific case. Perhaps look in the various log files inside the ~/.multichain/swisscoin directory to see if there's any info in there? Apart from that, can I suggest that you still trying using a different port to see if that resolves the problem?

---

hmm, restarted with -debug, tail -f debug.log and then try to connect from swissminer to the swisscoin chain but found nothing in the debug.log.

---

Try debug.log on the other node? Apart from that the best I can suggest as a short term fix is using a different port, or else setting up a couple of nodes at Digital Ocean where we have done extensive testing.

---

Hi Gideon,
so, today I have moved from Azure to AWS and it works. Dunna know what's up in Azure...

---

Odd. Thanks for letting me know. It may be an issue with the Azure infrastructure interfering with communication between unusual port numbers. Even though you did see that initial message successfully via telnet. If we get more reports of this we will look into it further.

---

Having the same issue here. Got the identical message when trying to connect the 2nd node to the first one. Both are VMs on Azure. :(