36195 2019-02-28 04:23:27 +0300 ejabberd cannot connect to ldap server via TLS 2019-03-12 14:17:30 +0300 1 1 4 Development Sisyphus ejabberd unstable all Linux CLOSED WORKSFORME P3 normal --- 34231 1 vseleznv rider aen darktemplaralt rider qa-sisyphus oldest_to_newest 179051 0 vseleznv 2019-02-28 04:23:27 +0300 $ rpm -q --qf '%{EVR}\n' ejabberd 18.12.1-alt1 $ rpm -q --qf '%{EVR}\n' erlang 1:21.2.4-alt3 $ tail -F /var/log/ejabberd/ejabberd.log 2019-02-28 01:15:45.952 [error] <0.557.0>@eldap:connect_bind:1073 LDAP connection to ldap.server:636 failed: TLS Alert: handshake failure 2019-02-28 01:15:45.955 [error] <0.558.0>@eldap:connect_bind:1073 LDAP connection to ldap.server:636 failed: TLS Alert: handshake failure 2019-02-28 01:15:45.955 [info] <0.590.0> TLS client: In state hello received SERVER ALERT: Fatal - Handshake Failure 2019-02-28 01:15:46.453 [debug] <0.557.0>@eldap:connect_bind:1051 Connecting to LDAP server at ldap.server:636 with options [{packet,asn1},{active,true},{k eepalive,true},binary] 2019-02-28 01:15:46.456 [debug] <0.558.0>@eldap:connect_bind:1051 Connecting to LDAP server at ldap.server:636 with options [{packet,asn1},{active,true},{k eepalive,true},binary] 2019-02-28 01:15:46.461 [info] <0.596.0> TLS client: In state hello received SERVER ALERT: Fatal - Handshake Failure This can be related: https://stackoverflow.com/questions/52637744/why-do-i-get-an-error-with-my-code-in-erlang-21-but-not-in-erlang-20 179189 1 darktemplaralt 2019-03-05 16:58:49 +0300 Можете проверить решает ли ejabberd версии 19.02-alt1 из тестового таска #223782 данную проблему? 179384 2 darktemplaralt 2019-03-12 14:17:30 +0300 Задание отправлено в Сизиф. Если проблема всё ещё воспроизводится с новой версией, прошу предоставить информацию, достаточную для воспроизведения проблемы, и переоткрыть баг.