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

Project 'web/support' was moved to 'tpo/web/support'. Please update any links and bookmarks that may still have the old path.
Closed (moved)
(moved)
Open
Created Mar 24, 2016 by David Goulet@dgoulet🆘

DirPort reachability test fails preventing the relay to work properly

(On git master: ea9472d)

Few seconds after the bootstrap is completed, this warning appears:

[warn] We just marked ourself as down. Are your external addresses reachable?

followed by this in the info log:

[info] TLS error while handshaking with "XXX.XXX.XXX.XXX": http request (in SSL routines:SSL23_GET_CLIENT_HELLO:unknown state)
[info] connection_tls_continue_handshake(): tls error [misc error]. breaking connection.
...
[info] connection_dir_client_reached_eof(): 'fetch' response not all here, but we're at eof. Closing.

and then the relay fails to join the network thus not usable. I track down the commit that introduces this regression (git bisect):

commit 2d33d192fc4dd0da2a2e038dd87b277f8e9b90de

This is a blocker because anyone using an IPv4 (haven't tested on v6) DirPort address will suffer from this. Only having an ORPort open is fine.

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