#770 Better error description on s2s error

Reporter pep
Owner Zash
Stars ★ (1)
  • Type-Defect
  • Milestone-0.12
  • Priority-Medium
  • Status-Fixed
  1. pep on

    I just got a "remote-server-not-found" because I have s2s_secure_auth to true and the remote server didn't support encryption. It would be nice to get a description with this kind of errors.

  2. Zash on

    Some info: remote-server-not-found pretty much only means that the host does not exist in DNS remote-server-timeout covers all other issues http://xmpp.org/rfcs/rfc6120.html#stanzas-error-conditions-remote-server-not-found http://xmpp.org/rfcs/rfc6120.html#stanzas-error-conditions-remote-server-timeout The tricky part here is that the code that sends the error bounces to clients is disconnected from the part that deals with s2s connection failure, and the actual cause is lost between them.

  3. MattJ on

    • tags Status-Accepted
  4. Zash on

    One small step https://hg.prosody.im/trunk/rev/c0bd5daa9c7f

    • tags Status-Started
    • owner Zash
  5. Zash on

    Related: https://hg.prosody.im/trunk/rev/1bb1e16f24b0

  6. Zash on

    Further improvements for cases of certificate errors in https://hg.prosody.im/trunk/rev/698ff3610e57

  7. Zash on

    And https://hg.prosody.im/trunk/rev/0c44090cb168 Maybe this can be considered mostly completed now?

    • tags Milestone-0.12
  8. Zash on

    No objections for almost 2 years, so considering it done.

    • tags Status-Fixed

New comment

Not published. Used for spam prevention and optional update notifications.