Clients and Ejabberd ... HAYELP!!!

I've got Ejabberd up and running - a few problems - but mainly due to Debian not Ejabberd...

JWChat works nicely, but I also need to connect to the server using a client - preferably Exodus. However I don't seem to be able to connect!!! IS there anything specific I need to set up to be able to connect to the server...

In Exodus I have tried choosing both normal and Http type connections, tried letting Exodus search for and specifying my server (I know that to have search working I need to edit the DNS Servers db) & port, both in Normal and HTTP mode. Using the Debug mode in Exodus I just get :

Looking up SRV: _xmpp-client._tcp.ukec4deb1.crystaleu.net
Direct DNS failed.. Using server: ukec4deb1.crystaleu.net
RECV:
Using specified Host/Port: ukec4deb1.crystaleu.net 5222
RECV:
Using specified Host/Port: ukec4deb1.crystaleu.net 5222
RECV:
Using specified Host/Port: ukec4deb1.crystaleu.net 5222
SENT:
Using specified Host/Port: ukec4deb1.crystaleu.net 5222

But nothing else - connection fails EVERY TIME!!!

HAYELP!!!

Port 5222 bloqued or unable to resolve name

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

Nope, able to resolve name

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?

Got IMCOM to work

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

maybe it's a missing ssl certificate problem

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.

Syndicate content