Bug #8381

Time synchronization displays error with proxy plus bridge

Added by sajolida 2014-12-03 17:09:22 . Updated 2015-04-14 15:39:56 .

Tor configuration
Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:


In Tails 1.2 and 1.2.1, when I do:

- Start Tails without network.
- Set the date to “Sat, Jan 1 2000 00:00:00”.
- Configure Tor to go through an HTTP proxy and a bridge.

Then I get an error message as soon as Tor tries to connect: “Tor failed to establish a Tor network connection. Establishing an encrypted directory connection failed (done).”

Still, Tor continues to connect in the background and end up connecting fine and I get the “Tor is ready” notification.


Related issues

Related to Tails - Bug #6985: Allows configuring unworkable combination of outbound port filtering + obfsproxy Resolved 2014-03-28


#1 Updated by anonym 2014-12-03 17:20:33

Just dumping what I had on our Tails 1.2.1 testing session pad:

We may have to live with this. Tor Launcher isn’t designed to have Tor stall during bootstrap due to certificate lifetime issues. The best we may be able to do is to kill Tor Launcher (to hide the error) in 20-tordate, right after “if clock_is_way(); then”.

#2 Updated by intrigeri 2014-12-14 17:46:05

  • related to Bug #6985: Allows configuring unworkable combination of outbound port filtering + obfsproxy added

#3 Updated by BitingBird 2015-04-10 17:46:38

Should this be rejected, then?

#4 Updated by intrigeri 2015-04-14 13:00:03

> Should this be rejected, then?

The problem is real, anonym suggested a workaround, and there’s always the option to adapt Tor Launcher to our needs => no, IMO this should be left open. If we decide we are unlikely to fix it ourselves any time soon, then Low priority would be more appropriate.

#5 Updated by BitingBird 2015-04-14 15:39:56

  • Priority changed from Normal to Low