-
Hello there. I'm in doubt where is a bug, so I write here first. :) I have |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
My
|
Beta Was this translation helpful? Give feedback.
-
So i think this is caused by misconfiguration of xmpp.jp server, it looks like it have srv records for both xmpp-server and xmpps-server pointing to this same address/port, and i think that port works only as xmpp-server (it requires using starttls). And looks like we try first to connect to it using direct tls, and when that fails we abort connection completely. Probably changing our code to try to connect to next choice when that happens is something that we should add, i will look at that. |
Beta Was this translation helpful? Give feedback.
-
I added commit 8e7489c that should help here. |
Beta Was this translation helpful? Give feedback.
-
Yeah, i missed some things, i commited fix for that today, so if you can try current master. |
Beta Was this translation helpful? Give feedback.
So i think this is caused by misconfiguration of xmpp.jp server, it looks like it have srv records for both xmpp-server and xmpps-server pointing to this same address/port, and i think that port works only as xmpp-server (it requires using starttls). And looks like we try first to connect to it using direct tls, and when that fails we abort connection completely. Probably changing our code to try to connect to next choice when that happens is something that we should add, i will look at that.