[tor-talk] Vidalia is closing tor's SOCKSPort listener (workaround found)

Nusenu BM-2D8wMEVgGvY76je1WXNPfo8SrpZt5yGHES at bitmessage.ch
Sun Jan 4 16:04:45 UTC 2015


> Is anyone aware of a way to prevent this behaviour?

To get a working setup I simply replaced the system tor daemon with a
tor instance that is started by vidalia (instead of connecting vidalia
to an already running tor instance).

torrc for vidalia located in ~/.vidalia/torrc

I had to explicitly set SocksListenAddress to 0.0.0.0 instead of using
SOCKSPort 0.0.0.0:9050



More information about the tor-talk mailing list