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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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

Closed (moved)
Open
Opened Aug 22, 2016 by bugzilla@bugzilla

Don't wait for Tor to start

If communication between firefox.exe and tor.exe was intercepted for some reason during start, then

The error message "Could not connect to Tor control port." is displayed after Tor Launcher (part of Tor Browser) fails to connect to the Tor control port for 30 seconds. But it usually happens when security suite asks users for permissions for these applications. And often 30 sec are not enough to create rules. So, Tor Launcher needs an option to manually continue the startup process instead of showing "Waiting for Tor to start...".

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