Bitcoin 0.8 client not working with tor.

[kerogre256]

I set bitcoin and tor according to this but is not working
https://en.bitcoin.it/wiki/Tor
I have port 8333 on my network blocked.
0 active connection to network....

[doobadoo]

Me too.  I have the port set to 9050, socks ver 5.  No mapping of UPnP.  Running Tor 2.3.25-4 (latest release).  Checked in tor browser, it too is using port 9050 socks 5.  (configure control port automatically not checked in Vidalia)

OS X 10.6

Any ideas guys?  Got 0 peers.  0 active connections.

EDIT:  Either my eyes are getting old or its just late.  But I "saw" 9050 in my browser, but no i really didin't!  Its really 9150...The satoshi client was misconfigured to use the old default of 9050...see next 2 posts.

[doobadoo]

Hmm, for some reason, maybe its the new TOR version but the socks port is 9150...not the default 9050.  Don't know why it picked that.

Anyhow...if you are having problems with the Satoshi client using TOR, double check what port TOR is using by starting TOR then selecting Settings button-->Advanced Tab-->Edit current torcc Button.  Then look to the last line "SocksPort"  The number next to it is the port you must use in your Bitcoin socks proxy settings.

[doobadoo]

Note to the Devs...  Tor is now defaulting to port 9150, no longer 9050.  According to the Tor changelog this has something to do with the move to FF ESR 17 and HTTPS Everywhere.  Not sure if the change is permanent but it probably is.   The default proxy port should be changed from 9050 to 9150 in the Satoshi client.  Not a priority, but confused me for a bit.  This change appears to have just been released in the stable version 0.2.3.25-4.  Those Onion routing jokers!

[wiggi]

Tor is now defaulting to port 9150, no longer 9050.

thanx for figuring that out. Tor jokers should make a changelog in a place where their
regular users can find it when they dl new browser bundle. Now many people think
secret service has new super powers