After Tor restart, TorBrowser thinks it is not running and Vidalia also can't reconnect to it.
Sometimes Tor needs to be restarted, in `/etc/init.d/tor restart` way. This fixes problems, but causes Vidalia to stop showing the happy green bulb permanently and Tor browser also warns that Tor is not running.
If I press “Yes, start anyway” it works without problems.
Related to Tails -
#3 Updated by anonymous2 2015-02-05 10:32:45
> > Sometimes Tor needs to be restarted, in `/etc/init.d/tor restart` way.
> Sorry, we don’t support that. What problem does it solve for you exactly?
Stuck Tor after clock jump. TAILS runs in a VM, and when the host goes to suspend-to-ram (and to other network), TAILS in VM feels bad and sites become unreachable from Tor browser. Sometimes the problem got fixed by waiting for long enough, or after pressing “Use new identity” button; but `/etc/init.d/tor restart` is the reliable way.
I think there should be button “Restart Tor” in Vidalia or in “Applications->System tools” or “Applications->Networking” menu.
#4 Updated by intrigeri 2015-02-05 10:39:25
> I think there should be button “Restart Tor” in Vidalia or in “Applications->System tools” or “Applications->Networking” menu.
This can be triggered by disconnecting and reconnecting from the network, using the NetworkManager applet.
Does it work for you?
#6 Updated by intrigeri 2015-02-05 14:45:52
> If it is the “official” workaround against Tor problems, then there can be a phrase in Vidalia’s window like “To restart Tor, reconnect to the network using Network Manager applet’s to restart”.
Yep, except we’re going to remove Vidalia. So this should go somewhere in the documentation instead, I think.
#12 Updated by anonymous2 2015-02-13 11:24:40
I have just verified that Tor unstucks itself when I disconnect and reconnect from NetworkManager’s applet.
$ curl --head http://google.com/ HTTP/1.1 504 Connect to google.com:80 failed: SOCKS error: TTL expired
$ curl --head http://google.com/ HTTP/1.1 301 Moved Permanently