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

Closed (moved)
Open
Opened Aug 31, 2013 by bastik@bastik

Reachability test fails sometimes

Since version 0.2.4.x-alpha (I guess the whole branch up to 0.2.4.16-rc) I saw the reachability test fail on my bridge which, as far as I know, didn't show this message with 0.2.3.x.

I can't reproduce it, but it happened yesterday and the day before that, without me noticing. It runs on Windows, like always and is up part-time. Today it took extremely long (compared to previous times) to validate that it is up.

It happened before and all I did back then was to exit Vidalia (and Tor) and start it again.

Strange enough is that Tor retries the test, but keeps failing if it failed the first one. To what I have experienced it appears that this does not happen in you restart it, though I can't say that for sure.

Another bridge that was set-up during the 0.2.4.x-alpha phase on a Linux server failed this reachability test at least once and all I did was restart the Tor daemon to make the test succeed.

Both bridges are obfsproxy bridges, which are configured like normal bridges with lines for the transport. No NoAdvertise or no NoListen. There's nothing special about them.

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