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
  • #13920

Closed (moved)
(moved)
Open
Created Dec 08, 2014 by Tom Lowenthal@flamsmark

If the ports tor wants to use are already in use, try different ports before freaking out.

A user story: Imagine that you want to run two instances of Torbrowser at the same time. Perhaps you want to use one site in one instance and another site with the other, but who knows? You download the Torbrowser tarball and extract it twice — into two different directories. Now you launch one of the Torbrowsers. So far so good. You go to launch the other one, and… oh no, “Tor unexpectedly exited.”. Now you're sad.

Tor didn't launch properly because the ports it wants to use are already in use by the other Torbrowser's tor. You could fiddle with the config files to manually fix this. But it'd be nicer if Tor Launcher figured this out on its own. If tor didn't start properly, was it because the ports it wanted were already in use? If we just increment them all by one and try again, does it work? If so, let's just do that.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking