-
Notifications
You must be signed in to change notification settings - Fork 890
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
Two nodes in the same machine - can't connect from one to another #2337
Comments
Can you attempt to connect from You can also use the |
I have tried the connection both ways from clightning_bitcoin and from clightning_02_bitcoin. Neither works. The syntax didnt matter. Tried both of these and they have the same error.
Is there anything else you'd suggest I try to do to get to the root cause? Do you see any issues with the docker-compose ports and expose |
|
Another alternative would be to try and connect directly over the docker bridge. If you run If that doesn't work I'd suggest taking out |
This was helpful. But the problem now seems deeper and similar to #1798 The difference is that the ports are open on the DigitalOcean droplet, yet any telnet / netcat call to the IP and port is throwing an error:
When I check other applications running on the machine on ports 8080 and 8081, the netcat / telnet is successful:
lsof TCP outputThe firewall is good: |
Solved. The problem was with the --bind-addr flag not being present. The moment i added: Now I am able to connect between the nodes and from outside the VM as well and create inbound channels to my nodes. Does it make sense to add this to the README.md so that in future inbound connections aren't an issue? |
@rustyrussell does the |
I've run into this before. If you set |
I create a pull request for a README.md update so that this issue doesn't come up in the future |
Issue and Steps to Reproduce
I have two nodes running on ports 9735 and 9112 on the same DigitalOcean droplet.
When I try to connect from one to the other:
docker exec lightning lightning-cli connect 038de60a0cb43eea67e0bcb6e207daebad312a245cedd8b09deb2c5ba4bb19f601 138.68.231.196 9112
i get the error:
{ "code" : -1, "message" : "138.68.231.196:9112: Cryptographic handshake: peer closed connection (wrong key?). " }
Both my nodes are built out of image: elementsproject/lightningd and ports 9735 and 9112 are open through the DigitalOcean UFW firewall.
getinfo
outputNode 1:
Node 2:
Docker compose setup:
The text was updated successfully, but these errors were encountered: