Skip to content
This repository has been archived by the owner on Feb 10, 2024. It is now read-only.

Problem with SOCKS5 + Tor + Freenode #849

Closed
ghost opened this issue Nov 28, 2013 · 9 comments
Closed

Problem with SOCKS5 + Tor + Freenode #849

ghost opened this issue Nov 28, 2013 · 9 comments

Comments

@ghost
Copy link

ghost commented Nov 28, 2013

Freenode's tor hidden service is unstable, but it provides me 4 different nameservers, I need hexchat tries connection at all of them before reporting error but this doesn't happen.
Log:

  • Connecting to 127.0.0.1 (127.0.0.1) port 31786...
    SOCKS Proxy failed to connect to host (error 5).
    Proxy traversal failed.
  • Stopped previous connection attempt (pid=13279)

At the time of this connection I have 3 other nameservers to hexchat try, but he doesn't just hang up here.
Note: The proxy works, I'm 100% sure, maybe a little more.
Thanks for hexchat, it's really cool.

@Arnavion
Copy link
Contributor

As it was explained to you in #hexchat, HC does retry on server connection failure. It does not retry on proxy connection failure.

Your tor proxy rejects the connection when it is unable to connect to FreeNode's tor service. As far as HC is concerned, this means the proxy connection failed, not the server connection, so it does not retry.

Now, the fact that HC does not retry on proxy connection failure is a bug, but fixing that still won't solve your problem. HC doesn't know the proxy connection failure is because the hidden service is down, so even if it retried it would retry to the same server.

@ChipWolf
Copy link

I'm necro bumping this issue.
As @Arnavion says, the fact HC does not retry on proxy connection failure is a bug, which still hasn't been fixed.
Tor cycles it's routes each time a program attempts to transverse through it, so this would be a useful feature to have HC auto reconnect on proxy connection failures.
I have multiple hidden services set for each IRC server, even if one of those go down, it should still cycle. It should also reset the connection with the proxy (a relay/exit node could have gone down)

@Arnavion
Copy link
Contributor

Tor cycles it's routes each time a program attempts to transverse through it, so this would be a useful feature to have HC auto reconnect on proxy connection failures.

That is fine, but...

I have multiple hidden services set for each IRC server, even if one of those go down, it should still cycle.

As I said in my previous comment, even if HC were to retry here, it would retry to the same server (in this case, the same hidden service). It's true that tor may change the route to the hidden service and that's completely fine, since it's transparent to HC. The point is that if the connection fails, then HC only sees it as a proxy connection failure, not a server connection failure. HC cycles servers when it knows that it's a server connection failure, but it doesn't when it's a proxy connection failure, because that may be because the server is fine and the proxy is having issues.

@ChipWolf
Copy link

Either way, if it's a server or a proxy issue, a reconnect fixes it.
So if it were to auto-reconnect, it would fix it.

@bw4518
Copy link

bw4518 commented Mar 14, 2015

Hopefully this will get fixed eventually, although reported already more than a year ago.

Only possible workaround I can think of would be a script that would trigger on this 'Proxy traversal failed' error and re-start reconnect to the network.

@Mikaela
Copy link
Contributor

Mikaela commented Mar 14, 2015

It might also be worth noting that freenode's tor hidden service is temporarily disabled because of abuse and it has been that way for some time now.

2015-03-14 22:12:09+0200 -- Topic for #freenode is "Welcome to #freenode | Due to ongoing abuse the tor-sasl hidden service has been temporarily disabled | Staff are voiced; some may also be on /stats p -- you can /msg us at any time | FAQ: https://freenode.net/faq.shtml | Channel guidelines: https://freenode.net/poundfreenode.shtml | Blog: https://blog.freenode.net | Please don't comment on spam/trolls"
2015-03-14 22:12:09+0200 -- Topic set by mquin on 2015-02-09 20:04:38+0200

@lnostdal
Copy link

lnostdal commented Mar 15, 2018

This is still a problem in 2.12.4-5build2 (Xubuntu).

edit: Automatically reconnecting would fix this. I do a few calls to /reconnect manually now and it works.

@dry-75
Copy link

dry-75 commented Sep 30, 2019

Still an issue here , hexchat 2.14.2 ... Would be great if it's fixed ?

@olof486
Copy link

olof486 commented Oct 1, 2019

Still an issue here , hexchat 2.14.2 ... Would be great if it's fixed ?

here too. But strange issue: Yesterday it works (but no update at tor or hexchat) or changes at the system. Restarts and 10 tries, no connection to localhost

SOCKS Proxy failed to connect to host (error 5).
 Proxy traversal failed.
* Stopped previous connection attempt (11176)
* Looking up irc.xyz
* Looking up 127.0.0.1

And than, twenty minutes later it connect. What could here happend?

* Looking up irc.xyz.....
* Looking up 127.0.0.1
* Connecting to 127.0.0.1:9150 (127.0.0.1:9150)
* Connected. Now logging in.
* *** Looking up your hostname...
* *** Found your hostname (exit.tor.xyz)

Have someone an idea what here happend?

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

No branches or pull requests

7 participants