I am getting the same problem, my anyone-can-connect=false

+1 vote
On Master Node, I have the daemon running successfully (no errors).  Last message is "Node Started".

On Second Node, I run ./multichaind chainname@ and the message returned is:

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

I also disabled the firewall on both VMs, 2 VirtualBox VMs running ubuntu.

Any ideas or anything to try to troubleshoot?
related to an answer for: Didn't get wallet address
asked Jan 16, 2017 by MikeL

1 Answer

0 votes

Start by checking if you can connect via telnet from the VM running the second node to the VM running the first, using the same IP address and port (i.e. and 4255 in your examples). That should indicate whether it's a firewall or networking problem between the VMs, or something in the MultiChain handshaking stage. You can also examine the debug.log file in the appropriate blockchain directory on both VMs to see if there are any clues there. And finally, please ensure you are upgraded to the latest version, 1.0 alpha 27.

answered Jan 16, 2017 by MultiChain
Thank you - it was the networking - once that was resolved, I was able to connect the second node to the Master.  Thanks again.
Great - thanks for the update.