ejabberd - Comments for "Clients and Ejabberd ... HAYELP!!!"

maybe it's a missing ssl certificate problem

mfoss — Fri, 14 Jan 2005 19:45:00 +0000

From your answers, it seems you can login on the same machine, but not in others. Port 5222 and machine name seem to be correct.

5. Does any error appear on ejaberd.log or sasl.log? Search for 'ERROR' and 'CRASH' on those files.
6. If no errors appear: you tried Exodus and failed. Try again, disabling SSL/STARTTLS/SASL on Exodus.
7. If it fails: did you setup a SSL certificate to be able to use SSL/STARTTLS/SASL? If yes, try other clients like Psi, Pandion or Tkabber, both enabling and disabling SSL and/or STARTTLS, SASL.

PD: If you want to write the 'less than' symbol (<) on a comment here, you must put

& l t ;

without spaces.

Got IMCOM to work

Argon0 — Fri, 14 Jan 2005 11:35:39 +0000

1. On port 5222, couldn't get conferencing to work though... But I can send/receive messages...

Nope, able to resolve name

Argon0 — Fri, 14 Jan 2005 10:45:42 +0000

1. Haven't got X working on the server - is there a text based version?
2. Yup
3. yup
4. yup - and how do you post the "?xml version='1.0'?>stream:stream xmlns='jabber:client' xmlns:stream='ht..." Properly?

Port 5222 bloqued or unable to resolve name

mfoss — Thu, 13 Jan 2005 18:24:37 +0000

On the server machine: did you try a normal client? Psi, Gaim, Kopete and Tkabber are on Debian and should work.
On another machine: does 'ping your-jabber-server.org' work?
Does 'telnet your-jabber-server.org 5222' connect?
If so, write something, like 'test'. Does the server answer '<?xml version='1.0'?>...' ?