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

Closed (moved)
Open
Opened Feb 12, 2012 by Robert Ransom@rransom

Tor should give managed proxies its ORListenAddress

koolfy tried to set up a managed obfsproxy on an instance of one of our EC2 bridge images. It didn't work:

14:52 < koolfy> obfsproxy says
14:52 < koolfy> 2012-02-12 22:50:13 [debug] error_cb for 127.0.0.1:443: what=0x0020 errno=111
14:52 < koolfy> 2012-02-12 22:50:13 [warn] Error talking to 127.0.0.1:443: Connection refused
14:55 < koolfy> # What port to advertise for Tor connections.
14:56 < koolfy> ORPort 443
14:56 < koolfy> # advertise 443 but bind to 9001).
14:56 < koolfy> ORListenAddress 0.0.0.0:9001
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#5104