Opened 7 years ago

Closed 2 years ago

#9307 closed defect (wontfix)

Can't connect to remote tor

Reported by: seppel Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version: Vidalia: 0.2.21
Severity: Normal Keywords: remote, tor, connect, archived-closed-2018-07-04
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Vidalia is unable to connect remote tor server.

For example I have a Tor on a Linux server and trying to control it with Vidalia from my desktop.
I provide valid IP, TCP port and password in Vidalia settings (these credentials are suitable to control remote Tor with telnet), nevertheless Vidalia says that Tor is not running.

Also it's very strange for such "remote" use scenario, that Vidalia requires tor executable name. If I leave tor executable name empty, the message box "Error saving settings", "You must specify the name of your Tor executable" appears. I wouldn't have tor installed on my desktop. I've got a server for such purposes.

Google says that same error was reported and solved 6 years ago in old Trac:

Maybe this bug is trivial and developers are able to fix it in 5 minutes. If not I can try to fix it myself and provide patch.

Child Tickets

Change History (2)

comment:1 Changed 3 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:2 Changed 2 years ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: newclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.