Tor (with bridges) keeps giving “connections have failed” in command line (while working ok through Tor Browser)?
When I try to connect to Tor through command line (Windows 10):
"C:\Tor Browser\Browser\TorBrowser\Tor\tor.exe" -f "C:\Tor Browser\Browser\TorBrowser\Data\Tor\torrc" | more
I get the following error:
Mar 11 14:10:01.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Mar 11 14:10:02.000 [warn] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 1; recommendation warn; host A1A1234A123AB12345A1234A1A1234A123456789 at 0.0.2.0:2)
Mar 11 14:10:03.000 [warn] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable [WSAENETUNREACH ]; NOROUTE; count 2; recommendation warn; host A1A1234A123AB12345A1234A1A1234A123456789 at 0.0.2.0:2)
Mar 11 14:10:03.000 [warn] 1 connections have failed:
Mar 11 14:10:03.000 [warn] 1 connections died in state connect()ing with SSL state (No SSL object)
Tor works normally when I use the Tor Browser (not the command line) with no problem using the same Bridge provided within the torcc configuration file.
I'm sure that bridges are working (not blocked) because when I run Tor Browser, connection is established with no problems. I believe something is missing in order to make the command line work successfully.
Notes:
Further Notes: There is a question seems to be the same, asking about the similar error message: • Can't connect Tor Network, failed to establish network
My question is different as it's about not being able to use Tor through command-line with bridges I'm sure they are not blocked (because they are working on Tor Browser within the same computer).
I am looking for using Tor (with Bridge) over the command line (without the need to start Tor Browser) and make connection established successfully through command line.
Trac:
Username: omareg94