-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Connecting to some peers fails with 'dial attempt failed: context deadline exceeded' (MOSTLY) #5800
Comments
"context deadline exceeded" means the we reached a timeout. It sounds like you're behind a very restrictive network. Can you try running: > nc 104.131.131.82 4001 That should spit out the text (you'll need some netcat variant) |
@Stebalien thanks for answer! I`m able to see Also, i`ve discussed it with my network administrator - we have no any restricts. Moreover - i setted up port forwarding, so I don`t think that it is the problem. |
So, you're saying that Note: It is perfectly normal to not be able to connect to all peers. Many may either be offline or behind NATs. However, you should be able to connect to the bootstrap nodes. |
I`ll be able to try tomorrow. Will back with screenshot xD |
@Stebalien here is the link to screenshot where I made clean install of ipfs on clean Ubuntu 16.04.
And I can`t connect to 104.131.131.82... |
If you can use netcat ( However, to rule out other potential issues, mind running the example in the readme here: https://github.com/Stebalien/p2pcat ( |
@Stebalien does this output correct?
|
@Stebalien anyway, after that i still have no any peer in |
Yep, that's the expected output. That's really weird. |
@Stebalien to clarify all environment details - in both cases nodes interacting with the Internet through NAPT; but port forwarding did not help to resolve it. |
I have the same problem |
@amidmm The exact same problem? The issue here isn't the error message "dial attempt failed: context deadline exceeded". You'll get that whenever a dial fails. The issue here is that libp2p (our networking library) appears to be working while go-ipfs isn't. |
@Stebalien I'm using go-libp2p and for bootstrapping DHT I'm using |
@Stebalien |
Are both of your daemons running on the same machine? What ports? What's the output of |
similar error for me, but I am running 2 ipfs in separate docker-compose projects on the same machine (swarm ports exposed to host machine: 4001 and 4101)
I get dial attempt failed: EOF
|
For everybody experiencing this error, could you please build from master and try again? This should've been fixed in libp2p/go-libp2p-kad-dht#237. Please report your findings. |
I just tried to run 2 nodes on separate machines inside docker-compose, and it worked. in order to add the peer I had to run:
|
Version information:
Type:
Bug
Description:
Hi all!
I installed clean instance of
ipfs init
and startedipfs daemon
.After that
ipfs swarm peers
answers with nothing.When I tried to
ipfs swarm connect
to the multiaddrs fromipfs bootstrap
, it always saysAfter that i setted up port forwarding from my outer IP:4001 to my local PC`s IP:4001. Still same situation.
After that i tried to connect from remote node directly through outer IP:4001 and it was successful, and after that my
ipfs swarm peers
started to fills by some addresses. And restarts of daemon connects to peers (but if I wait for a while between stopping and starting, there are empty list inipfs swarm peers
, sometimes there appears some address and peerlist starts fills again - i think it is because peers that i was connected to, tries to reconnect to me afterperiod
seconds).But i still can`t connect to my remote node - same error:
Also, when i trying to execute
ipfs dht provide <hash>
- it hangs. With-v
flag it shows many connections to peers, some of them successful and some are not with same or similar errors:Can you provide me information about why these errors pops up (especially
context deadline exceeded
error)The text was updated successfully, but these errors were encountered: