SSL/TLS handshake error about docker-ejabberd HOT 6 CLOSED

Ok, I solved it myself. I switched from Psi to Adium…

from docker-ejabberd.

I have the same problem now; a previous version of docker-ejabberd (or more likely the culprit, ejabberd) didn't have an issue with Psi.

from docker-ejabberd.

Presumably it is related to this: 741b835

I'm no SSL expert, but Psi hasn't been updated in a long time.

from docker-ejabberd.

I think this is an issue with older OS X versions. Does it work if you re-enable TLSv1?

from docker-ejabberd.

It is not exclusive to OSX, I have the problem one various versions of Windows as well.

I renabled both TLSv2 and SSL3 (made harder by the fact that I couldn't figure out a simple way to modify the config file in the running container for testing a changed config), and the SSL problem is gone.

Now a separate problem appeared with Psi, immediately after login:

 2015-06-17 10:35:46.899 [error] <0.617.0> CRASH REPORT Process <0.617.0> with 0 neighbours exited with reason: bad argument in call to xml:element_to_binary({xmlel,<<"message">>,[{<<"from">>,<<"[email protected]">>},{<<"to">>,<<"annemarie@foo....">>},...],...}) in ejabberd_c2s:send_element/2 line 1908

This is on OSX, I will try some Windows.

from docker-ejabberd.

Ok, the relevant bug report in ejabberd is here: processone/ejabberd#479

from docker-ejabberd.