-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Daemon causes connection loss. #1761
Comments
Maybe this is generally an issue with the number of open connections? You could |
@doei what's your ISP? they may be throttling anything that looks like p2p. |
@doei I had weird issues with my ISP for month where daemon startup crashed and rebooted their supplied modem. BT and other P2P also worked fine, too. |
@cryptix so how did that stop? |
@doei hour(s) of calls and two holiday-days to get a support "techie" from them to run speedtest.net at my home.. I had to demonstrate them the crash twice until they changed something. I still think that it was the ISPs crappy carrier-grade NAT but... Just saying that you shouldn't factor out the ISP too soon. |
@cryptix so they didn't tell you what they changed exactly? I'm not factoring out anything, but filtering p2p traffic alone can't be the reason. Anyway thanks for the answers, i'll post here if anything ever changes. |
@doei that's painful, either way. After |
@doei you should come over to irc so we can discuss more - maybe it's worth a try to give you a patch that inserts sleep intervals between bootstrapping nodes. |
@cryptix i'm around :) just checked-in IRC |
Did anybody find a solution to this problem? I'm having the same exact issue with my connection for whatever reason. |
This has been resolved since 0.4.0 |
As discussed on #ipfs I can't run the ipfs daemon for more than a few minutes without getting kicked off. The issue looks similar to this one, however having had this problem for a few days already, my ISP did not contact me for any port scanning problem.
@whyrusleeping advised me to filter a few IPs (from this list), which seemed to delay the connection loss for a bit, but didn't fully solve the issue...
Hope it helps, tell me if you want some more logs and/or info for whatever...
The text was updated successfully, but these errors were encountered: