What do you see instead? Jul 21 16:23:57 connUZECvuvwqtHL debug New connection FD 27 (x.88, 41446, y.19, 5222) on server FD 16 (*, 5222) Jul 21 16:23:57 connUZECvuvwqtHL debug Connected (FD 27 (x.88, 41446, y.19, 5222)) Jul 21 16:23:57 c2s56213ec30250 info Client connected Jul 21 16:23:57 runner-uMe6u0-J0t0 debug creating new coroutine Jul 21 16:23:57 c2s56213ec30250 debug Client sent opening <stream:stream> to y Jul 21 16:23:57 c2s56213ec30250 debug Sending[c2s_unauthed]: <?xml version='1.0'?> Jul 21 16:23:57 c2s56213ec30250 debug Sent reply <stream:stream> to client Jul 21 16:23:57 c2s56213ec30250 debug Not offering authentication on insecure connection Jul 21 16:23:57 c2s56213ec30250 debug Not offering authentication on insecure connection Jul 21 16:23:57 c2s56213ec30250 debug Sending[c2s_unauthed]: <stream:features> Jul 21 16:23:57 c2s56213ec30250 debug Received[c2s_unauthed]: <starttls xml:lang='en' xmlns='urn:ietf:params:xml:ns:xmpp-tls'> Jul 21 16:23:57 c2s56213ec30250 debug Sending[c2s_unauthed]: <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'> Jul 21 16:23:57 connUZECvuvwqtHL debug Start TLS after write Jul 21 16:23:57 c2s56213ec30250 debug TLS negotiation started for c2s_unauthed... Jul 21 16:23:57 connUZECvuvwqtHL debug Prepared to start TLS Jul 21 16:23:57 connUZECvuvwqtHL debug Starting TLS now Jul 21 16:23:57 connUZECvuvwqtHL debug TLS handshake complete (TLSv1.3 with TLS_AES_128_GCM_SHA256) Jul 21 16:23:57 c2s56213ec30250 debug Client sent opening <stream:stream> to y Jul 21 16:23:57 c2s56213ec30250 debug Sending[c2s_unauthed]: <?xml version='1.0'?> Jul 21 16:23:57 c2s56213ec30250 debug Sent reply <stream:stream> to client Jul 21 16:23:57 c2s56213ec30250 info Stream encrypted (TLSv1.3 with TLS_AES_128_GCM_SHA256) Jul 21 16:23:57 runner-uMe6u0-J0t0 debug changed state from ready to error (ready) Jul 21 16:23:57 c2s56213ec30250 error Traceback[c2s]: .../lib64/prosody/community-modules/mod_sasl2/mod_sasl2.lua:61: attempt to call a nil value (method 'ssl_info') stack traceback: .../lib64/prosody/community-modules/mod_sasl2/mod_sasl2.lua:61: in field '?' /usr/lib64/prosody/util/events.lua:81: in function </usr/lib64/prosody/util/events.lua:77> (...tail calls...) /usr/lib64/prosody/modules/mod_c2s.lua:132: in field '_streamopened' /usr/lib64/prosody/modules/mod_c2s.lua:328: in upvalue 'func' /usr/lib64/prosody/util/async.lua:144: in function </usr/lib64/prosody/util/async.lua:142> What version of the product are you using? On what operating system? prosody-0.12.4 mod_sasl2 current from the repository tested with lua 5.1 and lua 5.4, no difference gentoo linux actual user authentication happens over dovecot ldap, but i would not expect this to have an effect on the issue at hand.

Thanks for the report. This module is not compatible with Prosody 0.12. I updated the documentation: https://hg.prosody.im/prosody-modules/rev/da942a3f3660

• tags Component-Community Status-WontFix