StartTLS Configuration - Fully open and still throwing an error

Hi,

We have configured an eJabberd cluster running version 16.01.68 and have a number of clients connecting through successfully.
However, we have a new client trying to connect in that is obviously using a different SSL/TLS configuration as we are receiving the error:

2016-02-29 10:21:22.474 [debug] <0.16206.10>@ejabberd_receiver:handle_info:192 TLS error = SSL_do_handshake failed: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

It appears that the client is trying to connect using TLSv1.2 from a network capture and we have changed the ejabberd.yml configuration to allow "all" in the protocol options (we have also tried more secure variations such as "no_sslv2" and "no_sslv3" with the same resulting error).
We're using a self-signed certificate for the TLS which appears to be working fine for all of the other client connections, it's just this one that seems to be using a different configuration.

Can anybody advise as to what the problem might be, or what configuration would allow this connection through?

Thanks in advance,

Phil

Syndicate content