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

Swarm Connect failure when trying to connect two nodes I control #5588

Closed
obo20 opened this issue Oct 11, 2018 · 5 comments
Closed

Swarm Connect failure when trying to connect two nodes I control #5588

obo20 opened this issue Oct 11, 2018 · 5 comments

Comments

@obo20
Copy link

obo20 commented Oct 11, 2018

Version information:

go-ipfs version: 0.4.17-
Repo version: 7
System version: amd64/darwin
Golang version: go1.10.3

Type:

Bug

Description:

I'm trying to manually connect two ipfs nodes together via IPFS swarm.

On the first node, I get:
Error: connect (my node ID) failure: dial attempt failed: <peer.ID XXXXXX> --> <peer.ID YYYYYY> dial attempt failed: context deadline exceeded

On the second node, I get:
Error: connect (my second node ID) failure: dial attempt failed: failed to dial <peer.ID XXXXXX> (default failure)

This is happening 100% of the time without fail, and is turning into a pretty big issue for me, as attempting to pin via "ipfs pin (hash) -r" when I'm not directly connected between the two nodes seems to be bugged as well.

@leerspace
Copy link
Contributor

leerspace commented Oct 12, 2018

For anyone else who comes across this, I think this is the same issue as what's being discussed in this discourse thread.

@vyzo
Copy link
Contributor

vyzo commented Oct 12, 2018

Are your peers in different networks and behind NAT/firewalls?

@obo20
Copy link
Author

obo20 commented Oct 15, 2018

@vyzo the peers are both on digital ocean, and they're behind no NAT.

They are behind firewalls, but these two peers have all TCP ports open right now for testing purposes.

@Stebalien
Copy link
Member

Stebalien commented Oct 16, 2018

If you run ipfs dht findpeer YYYYYY on peer XXXXXX, what do you get?

@obo20
Copy link
Author

obo20 commented Oct 16, 2018

It turns out while there was no firewall issues on Digital Ocean's networking side, there was an unintentional firewall that was set up on ubuntu. By running "sudo ufw allow 4001" on each of the nodes, the issue was fixed.

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

No branches or pull requests

4 participants