However, since tor was updated and pidgin wasn't, that suggested some incompatibility in tor, rather than a failure in pidgin. so tor seems to be working for the most part. I'm also using tor as the proxy for this browser session. what are you looking for?įWIW, I found out that configuring pidgin to contact the same port as SOCKS4 (with remote DNS checked) works. Netstat output? it's my desktop, surely you don't want all of it. (I had an empty one before, but in the process of investigating this, I switched to the default one, and it made no difference)

Tor config is just the default one from the rpm. pidgin doesn't log anything about connection attempts or so, does it? I don't see any. Normal connection, or perhaps timeouts and retries noted in the tor journalĪs I mentioned, after the reboot tor doesn't log anything about failed connections any more, although the connections eventually fail. If you haven't rebooted yet, you might see nearly immediate disconnects and errors issued by tor in journaldĪfter a reboot, the attempt to reconnect takes longer to fail, but it does, and there's no indication as to why in the tor journal Version-Release number of selected component (if applicable):Ģ.configure pidgin to use Tor/Privacy (SOCKS5) in tools -> preferences -> proxy, or in the proxy settings of a specific account (I've only tried XMPP and Matrix)ģ.disable and reenable the account, so that it attempts to reconnect After a reboot that restarted tor, I don't even get that any more, but connections still fail. After upgrading tor from tor-0.3.4.86_64 to tor-0.3.5.86_64, pidgin would fail to reconnect to XMPP and Matrix servers configured to use the global proxy settings: Tor/Privacy (SOCKS5) on localhost:9050.īefore rebooting, tor would report some user/password error every time I tried to reconnect.

Tor proxy server error