Project

General

Profile

Bug #8856

After Tor restart, TorBrowser thinks it is not running and Vidalia also can't reconnect to it.

Added by anonymous2 about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
02/04/2015
Due date:
% Done:

0%

Feature Branch:
Type of work:
Test
Blueprint:
Starter:
Affected tool:
Tor Launcher

Description

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 issues

Related to Tails - Feature #6841: Replace Vidalia Resolved 03/03/2015

History

#1 Updated by intrigeri about 5 years ago

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?

#2 Updated by BitingBird about 5 years ago

  • Assignee set to anonymous2
  • QA Check set to Info Needed

#3 Updated by anonymous2 about 5 years ago

intrigeri wrote:

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 about 5 years ago

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?

#5 Updated by anonymous2 about 5 years ago

I'll try when I see the stuck Tor next time.

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".

#6 Updated by intrigeri about 5 years ago

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.

#7 Updated by anonymous2 about 5 years ago

Removed? Then what should show Tor's status and have "Use new IP, but don't close all my tabs" button? The text can be there as well.

#8 Updated by BitingBird about 5 years ago

#9 Updated by BitingBird about 5 years ago

See #6841

#10 Updated by intrigeri about 5 years ago

Removed? Then what should show Tor's status and have "Use new IP, but don't close all my tabs" button? The text can be there as well.

Please, let's move this discussion to the ticket about removing Vidalia.

#11 Updated by anonymous2 about 5 years ago

Posted a message to https://labs.riseup.net/code/issues/6841

I'll write here again when I check if reconnecting to the network does fix Tor.

#12 Updated by anonymous2 about 5 years ago

I have just verified that Tor unstucks itself when I disconnect and reconnect from NetworkManager's applet.

Before:

$ curl --head http://google.com/
HTTP/1.1 504 Connect to google.com:80 failed: SOCKS error: TTL expired


After:
$ curl --head http://google.com/
HTTP/1.1 301 Moved Permanently

#13 Updated by BitingBird about 5 years ago

  • Status changed from New to Resolved

So it's resolved then.

Also available in: Atom PDF