W dniu 01.05.2016, nie o godzinie 18∶57 -0700, użytkownik li...@lazygranch.com napisał: > <id > realm="MYDOMAIN>COM" > permfile="/usr/local/etc/jabberd/jabber.pem" > ciphers="TLSv1.2, TLSv1.0"
This is incorrect. See: http://abadcafe.pl/post/136618589813/configure-jabberd-2-for-xmppnet-score-a > require-starttls='true' You require StartTLS, let's remember that. > register-enable='false' > password-change='false' This is incorrect. These values work by setting them or not setting them - the value itself is irrelevant. > C2S : sx (io.c:301) encoding 250 bytes for writing: <?xml > version='1.0'?> > <stream:stream xmlns:stream='http://etherx.jabber.org/streams' > xmlns='jabber:client' from='MYDOMAIN.COM' version='1.0' > id='LONGRANDOM' xmlns:ack='http://www.xmpp.org/extensions/xep-0198.ht > ml#ns'>; > > C2S : sx (sasl.c:260) ssl not established yet but the app requires > it, not offering mechanisms Here's a first clue. Your server said, that it require ssl, and your connection is not ssl yet, so it wont offer any auth mechanisms. Regardless that auth was not offered yet, your client attempted authentication: > C2S : sx (io.c:255) decoded read data (176 bytes): <iq > id="_xmpp_auth1" > type="set"><query > xmlns="jabber:iq:auth"><username>SOMEUSER</username><password>PASSWOR > D</password> > <resource>profanity</resource></query></iq> No wonder server borked on it. > C2S : Mon May 2 01:08:12 2016 c2s.c:392 pre STARTTLS packet, > dropping It even gave you a plain text description what went wrong: > C2S : sx (error.c:79) prepared error: <stream:error > xmlns:stream='http://etherx.jabber.org/streams'>; > <policy-violation xmlns='urn:ietf:params:xml:ns:xmpp-streams'/> > <text xmlns='urn:ietf:params:xml:ns:xmpp-streams'> > STARTTLS is required for this stream</text></stream:error> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I suggest using a standard conformant XMPP client for your tests. It shall make your live much easier. :-) -- /o__ Q: What's a light-year? (_<^' A: One-third less calories than a regular year.
