Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #7490

Closed
Open
Created 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
Time tracking