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

Closed (moved)
Open
Opened Sep 13, 2017 by Taylor Yu@catalyst

large clock skews cause numerous bootstrap UX issues

Setting the system clock several hours ahead or behind real time can cause many different bootstrapping problems. Often bootstrapping will get stuck with no obvious way to make progress, and no visible indication of what might actually be wrong. These seem to be lead to a disproportionate number of support requests.

Some examples are:

clock in past:

  • stuck at 40% (Loading authority key certs) clock in future:
  • stuck at 80% (Connecting to the Tor network)
  • stuck at 85% (Finishing handshake with first hop)

More details and child tickets as I investigate further.

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