Mod_auth_dovecot failure due to SSL version mismatch

Hi everyone,

I am trying to get some sort of authentication working. Ideally dovecot.

The error on the jitsi meet side was “socket closed”
On the dovecot host:

imap-login: Disconnected (no auth attempts in 4 secs): user=<>, rip=xx.xx.xx.104, lip=xx.xx.xx.103, TLS handshaking: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number, session=

The dovecot server does not accept TLS V 1.2 for security reasons since it was deprecated recently.
But I lowered the TLS version level to 1 and still it does not work. Same as before. I tried to lower it to SSLV3 even. since the message said ssl3. That did not change anything either.

But I am open to suggestions.

Here’s the prosody log:

Aug 19 20:42:59 startup info Hello and welcome to Prosody version 0.12.1
Aug 19 20:42:59 general warn Lua 5.1 has several issues and support is being phased out, consider upgrading
Aug 19 20:43:00 startup info Prosody is using the epoll backend for connection handling
Aug 19 20:43:00 focus.meet.mydomain.me:tls info Certificates loaded
Aug 19 20:43:00 portmanager info Activated service ‘s2s’ on [::]:5269, [*]:5269
Aug 19 20:43:00 portmanager info Activated service ‘s2s_direct_tls’ on no ports
Aug 19 20:43:00 startup warn Attempt to read a non-existent global ‘socket_path’
stack traceback:
…rosody-plugins/mod_auth_dovecot/sasl_dovecot.lib.lua:53: in function ‘connect’
…rosody-plugins/mod_auth_dovecot/sasl_dovecot.lib.lua:128: in function <…rosody-plugins/mod_auth_dovecot/sasl_dovecot.lib.lua:120>
(tail call): ?
…rosody-plugins/mod_auth_dovecot/mod_auth_dovecot.lua:43: in main chunk
[C]: in function ‘xpcall’
/usr/share/lua/5.1/prosody/core/modulemanager.lua:270: in function ‘do_load_module’
/usr/share/lua/5.1/prosody/core/modulemanager.lua:353: in function ‘load’
/usr/share/lua/5.1/prosody/core/usermanager.lua:97: in function ‘?’
/usr/share/lua/5.1/prosody/util/events.lua:81: in function </usr/share/lua/5.1/prosody/util/events.lua:77>
(tail call): ?
/usr/share/lua/5.1/prosody/core/hostmanager.lua:108: in function ‘activate’
/usr/share/lua/5.1/prosody/core/hostmanager.lua:58: in function ‘?’
/usr/share/lua/5.1/prosody/util/events.lua:81: in function </usr/share/lua/5.1/prosody/util/events.lua:77>
(tail call): ?
/usr/share/lua/5.1/prosody/util/startup.lua:428: in function ‘prepare_to_start’
/usr/share/lua/5.1/prosody/util/startup.lua:703: in function ‘f’
/usr/share/lua/5.1/prosody/util/async.lua:156: in function ‘func’
/usr/share/lua/5.1/prosody/util/async.lua:144: in function </usr/share/lua/5.1/prosody/util/async.lua:142>
Aug 19 20:43:00 auth_dovecot error Dovecot connection failure: No data read from socket: closed
Aug 19 20:43:00 modulemanager error Error initializing module ‘auth_dovecot’ on ‘meet.mydomain.me’: …rosody-plugins/mod_auth_dovecot/mod_auth_dovecot.lua
:47: Could not create a new SASL object
stack traceback:
[C]: in function ‘assert’
…rosody-plugins/mod_auth_dovecot/mod_auth_dovecot.lua:47: in main chunk
[C]: in function ‘xpcall’
/usr/share/lua/5.1/prosody/core/modulemanager.lua:270: in function ‘do_load_module’
/usr/share/lua/5.1/prosody/core/modulemanager.lua:353: in function ‘load’
/usr/share/lua/5.1/prosody/core/usermanager.lua:97: in function ‘?’
/usr/share/lua/5.1/prosody/util/events.lua:81: in function </usr/share/lua/5.1/prosody/util/events.lua:77>
(tail call): ?
/usr/share/lua/5.1/prosody/core/hostmanager.lua:108: in function ‘activate’
/usr/share/lua/5.1/prosody/core/hostmanager.lua:58: in function ‘?’
/usr/share/lua/5.1/prosody/util/events.lua:81: in function </usr/share/lua/5.1/prosody/util/events.lua:77>
(tail call): ?
/usr/share/lua/5.1/prosody/util/startup.lua:428: in function ‘prepare_to_start’
/usr/share/lua/5.1/prosody/util/startup.lua:703: in function ‘f’
/usr/share/lua/5.1/prosody/util/async.lua:156: in function ‘func’
/usr/share/lua/5.1/prosody/util/async.lua:144: in function </usr/share/lua/5.1/prosody/util/async.lua:142>

Thanks.