-
Notifications
You must be signed in to change notification settings - Fork 119
Unrecoverable connection issues with socks5 proxy. #745
Comments
Not looking into this now, but: failures to connect/drops to CgAn are not uncommon, same for agora, this is one reason we have multiple IRC channels/servers configured by default, people could use more, people could set up new ones (IRC), people could easily implement new messaging layer implementations (see #650), but haven't done so yet. Anyway so my point is "Bitcoin handles socks OK" is not, I believe, the point, the point is your connection to CgAn keeps dropping. The bot should continue to operate on agora when that happens, if you have them both configured. |
I think the point is not that the connection keeps dropping, but that there is an endless loop of trying to recover and failing in different ways. I understand that the connection drops from time to time, but most of the time the script recovers. It's only some times that there is no recovery or exit, just an infinite loop. The only reason my copy/paste included a
I only have the CgAn in my config because I've never been successful with using both servers.
Didn't know you were looking for that, I may be interested and I have experience. |
Well something's wrong there; lots of people do, it's been like that for more than a year.
Constantly trying to reconnect in a loop is to be expected if the server is just not accepting connections from you. There have been periods like that in the past, but it's hard to keep track of, because it doesn't apply to everyone equally it seems, depends on (a) are you already connected (b) are you using clearnet/onion and other stuff no doubt.
That would be great. I see no downside to having other servers, the server operator has a potential to censor only, but then if people don't trust them they have no obligation to use it (edit: even more to the point: if you are up on all 3, and all users use all 3, then server 1 censoring you is pointless as you'll connect on the other 2). I think the code as-is should quite happily handle configuration of three servers, at least (there is no in-principle limit, don't know the practical actual limit). |
I think it had to do with the fact that I was using port 6697 instead of 6698 for CgAn. This seems to be resolved for me, so I will close the issue. |
@0xB44EFD8751077F97 Damn, dumb of me not to even think of that possibility :) Thanks for reporting on the resolution though, that'll help us to diagnose similar issues in future. |
This happens to me with
yg-pe.py
at least once per 24 hours. While this is happening, on the same host, I am able to make connections on the socks proxy without issue. Bitcoin 0.14.2 has no problem staying connected over the same proxy for instance. Here is a snip of some logs and then acurl
test to make sure the proxy is working.Apologies in advance if this is already being tracked. I couldn't find this exact bug with a search of open issues.
The text was updated successfully, but these errors were encountered: