TLS_ERROR when connecting back into Tor network through transparent proxy

Summary

After version 0.4.5.6 tor does not allow 100% bootstrapping when connecting back into network through transparent tor proxy.

Steps to reproduce:

  1. PC1 is transparent tor proxy TransPort
  2. PC2 is normal PC. Want connect through PC1 to reach internet.
  3. Start tor or torbrowser on PC2. tor and torbrowser on PC2 can not reach 100% bootstrap.

PC2 Tor Browser Log Copy to Clipboard

Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (TLS_ERROR; TLS_ERROR; count 10; recommendation warn; host xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
10 connections have failed:
10 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (TLS_ERROR; TLS_ERROR; count 11; recommendation warn; host yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
11 connections have failed:
11 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (TLS_ERROR; TLS_ERROR; count 12; recommendation warn; host zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

After restarting tor on PC1 many times, 100% bootstrapped on PC2 reached.

  1. tor service on PC2 also not reach 100% bootstrap.
[WARN] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (TLS_ERROR; TLS_ERROR; count 10; recommendation warn; host zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz at xxx.xxx.xxx.xxx:xxx)
[WARN] 10 connections have failed:
[WARN] 10 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
[NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
[NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
[NOTICE] Delaying directory fetches: DisableNetwork is set.

After restarting tor on PC1 many times, 100% bootstrapped on PC2 reached.

[notice] Bootstrapped 100% (done): Done

But fails again. many hours later.

[warn] Failed to find node for hop #1 of our path. Discarding this circuit.
[notice] Our circuit 0 (id: 116) died due to an invalid selected path, purpose Hidden service client: Establishing rendezvous point. This may be a torrc configuration issue, or a bug.
[warn] Failed to find node for hop #1 of our path. Discarding this circuit.
[warn] Failed to find node for hop #1 of our path. Discarding this circuit.

What is the current bug behavior?

Tor running on PC2 most times can not connect through transparent tor proxy running on PC1. Transparent tor proxy running on PC1 must restarted many times for Tor running on PC2 to connect 100% bootstrap.

What is the expected behavior?

Before 0.4.5.6 tor network allowed connections back into tor network every time. Now very few time allows connection.

Environment

  • Which version of Tor are you using? Run tor --version to get the version if you are unsure.

0.4.5.6, 0.4.5.7

  • Which operating system are you using? For example: Debian GNU/Linux 10.1, Windows 10, Ubuntu Xenial, FreeBSD 12.2, etc.

Operating system not matter. All problem.

  • Which installation method did you use? Distribution package (apt, pkg, homebrew), from source tarball, from Git, etc.

Relevant logs and/or screenshots

Possible fixes

Edited by David Goulet