Ejabberd: Problem with s2s connections

[beherit]

What version of ejabberd are you using?

ejabberd 17.04

What operating system (version) are you using?

Debian 8.7

How did you install ejabberd (source, package, distribution)?

package

What did not work as expected? Are there error messages in the log? What
was the unexpected behavior? What was the expected result?

After update ejabberd from 16.09 to 17.04 my users have problem with s2s connections, In logs I see e.g.:

2017-04-25 19:49:53.972 [info] <0.23091.0>@ejabberd_s2s_out:init:292 Outbound s2s connection started: beherit.pl -> jabber.at
2017-04-25 19:49:54.138 [info] <0.23091.0>@ejabberd_s2s_out:handle_auth_failure:242 (tls|<0.23092.0>) Failed outbound s2s EXTERNAL authentication beherit.pl -> jabber.at (hidden_by_ejabberd): Authentication failed: Peer provided no SASL mechanisms
2017-04-25 19:49:54.138 [info] <0.23091.0>@ejabberd_s2s_out:process_auth_result:134 Failed to establish outbound s2s connection beherit.pl -> jabber.at: authentication failed; bouncing for 34 seconds

How to fix it?

[beherit]

I resolved it by adding new modules (added in 17.03) to config file :)

[mechmind]

For those who desperately lurking for fix: You need to add mod_s2s_dialback: {} into modules section of config.

[evadim]

And mod_legacy_auth: {} allow more of them

[zinid]

@evadim mod_legacy_auth is only for c2s (very ancient clients), see XEP-0078

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.