Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #7490

Closed
Open
Opened Nov 15, 2012 by Trac@tracbot

Unable to run Tor as a relay: "Control socket is not connected"

My home server runs Linux Mint 13 Cinnamon. I'd like to set it up as a non-exit relay on the Tor network.

If I set Vidalia to run Tor as a client only, everything works fine. If I set it to run as a non-exit relay, however, I get an error when I try to connect:

"Vidalia was unable to apply your Server settings to Tor. Control socket is not connected."

And a corresponding log entry:

Nov 10 23:18:54.797 [Error] set_options(): Bug: Acting on config options left us in a broken state. Dying.

I receive this same error whether I run the version of Vidalia from the Tor browser bundle, the Ubuntu repo, or the torproject repo.

Trac:
Username: Centinel

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#7490