ejabberd - Comments for "Authentication failed: Peer provided no SASL mechanisms"

And mod_legacy_auth: {}

evadim — Sat, 09 Sep 2017 18:44:58 +0000

And mod_legacy_auth: {} enable bunch of old servers, on behalf with s2s_use_starttls: optional

I have the same problem.

Basildane — Mon, 24 Jul 2017 14:17:35 +0000

I have the same problem. Isn't using mod_s2s_dialback not solving the real problem?
Is it preferred to use SASL? I'm trying to understand the best-practice here.

badlop wrote:

Here is the solution: https://github.com/processone/ejabberd/issues/1700

Simply, enable mod_s2s_dialback: {} in the modules section of ejabberd configuration.

Here is the solution:

badlop — Mon, 22 May 2017 09:19:28 +0000

Here is the solution: https://github.com/processone/ejabberd/issues/1700

Simply, enable mod_s2s_dialback: {} in the modules section of ejabberd configuration.

Maybe that package includes a

badlop — Thu, 18 May 2017 20:44:51 +0000

Maybe that package includes a configuration file with some options enabled that are too restrictive, specifically s2s options, and more specific I mean s2s_use_starttls. Check what options you have enabled regarding s2s, and try to desactivate them. Once you find which one is relevant to your problem, you decide if it's a serious problem that requires a proper fix, or you don't both about reducing the strictness of that option.

Another thing to look is how many servers have you problem connecting. If it's several ones, check what software they run.

And last, it may happen that you found a bug in ejabberd or jabber.org's software.