Opened 8 years ago

Closed 5 years ago

#5359 closed defect (duplicate)

Exit Nodes not working

Reported by: ubjective Owned by: erinn
Priority: Medium Milestone:
Component: Applications/Tor bundles/installation Version: Tor: 0.2.2.35
Severity: Keywords: ExitNodes, needs-triage
Cc: Actual Points:
Parent ID: #4347 Points:
Reviewer: Sponsor:

Description

After downloading Vidalia Bundle 0.2.2.35-0.2.17 and adding ExitNodes {US} to the torcc file, Tor fails to connect. Yet, if I use the older version 0.2.1.30-0.2.12 it works fine.

Mar 10 14:42:10.333 [Warning] No specified exit routers seem to be running:
can't choose an exit.
Mar 10 14:42:10.333 [Warning] failed to choose an exit server
Mar 10 14:42:11.333 [Notice] All routers are down or won't exit -- choosing
a doomed exit at random.
Mar 10 14:42:11.333 [Warning] No specified exit routers seem to be running:
can't choose an exit.

Child Tickets

Change History (6)

comment:1 Changed 8 years ago by rransom

Milestone: TorBrowserBundle 2.2.x-stable
Priority: criticalnormal

This appears to be a consequence of #4347 (Tor can't find its 'geoip' file, so it can't know what country any relay is in); see the workaround in that ticket's description.

The Tor Browser Bundle should not have this problem.

comment:2 Changed 8 years ago by nickm

Component: Tor ClientTor bundles/installation
Owner: set to erinn

I'm calling this a "bundles/installation" issue; please let me know if I'm wrong to do so.

comment:3 Changed 8 years ago by arma

In fact, should we just dup it to #4347?

comment:4 Changed 7 years ago by arma

Parent ID: #4347

comment:5 Changed 5 years ago by erinn

Keywords: needs-triage added

comment:6 Changed 5 years ago by cypherpunks

Resolution: duplicate
Status: newclosed

Vidalia is deprecated, either it's dup to #4347 or not.

Note: See TracTickets for help on using tickets.