Firefox fails to find SOCKS proxy after tor is restarted through Vidalia
The Tor Browser Bundle version 2.2.34-4 on Linux uses the SocksPort auto setting in torrc. After restarting tor through the Vidalia interface, a new control port and a new SOCKS port are chosen while Firefox still uses the old SOCKS port. This causes "Connection refused" errors in Firefox.
Steps to reproduce:
- Start Tor browser bundle
- Random browsing
- Click "Stop Tor" button in Vidalia Control Panel
- Click "Start Tor" button in Vidalia Control Panel
- Open any URL
Expected result: URL can be opened normally Actual result: "Connection refused" error message
Suggestion for the fix on #tor-dev was:
!00:42 < armadev> vidalia could also fix it by memorizing the socks and control port (it does this anyway so it can tell firefox when it launches it), !00:42 < armadev> and restarting tor with the same ports it picked the first time
Trac:
Username: rpw