baqir123 / gtalksms

Automatically exported from code.google.com/p/gtalksms
0 stars 0 forks source link

Can't connect to ejabberd server: No response from server #262

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I have a fresh install of ejabberd-2.1.10 on our linux server.
I have gtalksms v3.5 installed on Samsung Galaxy Note I717 with Android 2.3.6.
I've checked and rechecked the gtalksms settings, several times, even tried 
copy/pasting info in.
My ejabberd server logs show it's accepting a connection, but doesn't even seem 
to attempt authentication.
Gtalksms is showing no errors, just an hour glass after a while.

I can log into the server without any issues with Pidgin (windows 7 x64) and 
Xabber (same phone). Both clients have no issues connecting, authenticating, 
and exchanging messages.

Is there something I'm missing?
Maybe a server requirement or setting that gtalksms needs to authenticate and 
connect?

Attached is my log from boot until gtalksms refuses to connect.

Original issue reported on code.google.com by swashbun...@gmail.com on 6 Apr 2012 at 4:50

Attachments:

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Here's an interesting note. I switched to Openfire server changed nothing in 
the gtalksms (accept user name from <name@domain.net> to <name>) and it logs 
right in. (although I have no muc)
So note to anyone wanting to run a server for gtalksms, openfire alot less 
trouble than ejabberd.
I still have no clue why stock ejabbrad rejects gtalksms.

Original comment by swashbun...@gmail.com on 9 Apr 2012 at 8:45

GoogleCodeExporter commented 9 years ago
Indeed smack/gtalksms does not receive an auth challenge after login:
04-06 00:31:38.036 E/gtalksms(  987): xmpp login failed: No response from the 
server.

It would be great, if you could get a trace of the xmpp stanzas of the login 
sequence from gtalksms with ejabberd.

Original comment by fschm...@gmail.com on 9 Apr 2012 at 5:46

GoogleCodeExporter commented 9 years ago
No user feedback in months

Original comment by fschm...@gmail.com on 11 Nov 2012 at 11:18

GoogleCodeExporter commented 9 years ago
This is not done

Original comment by ivebeenl...@gmail.com on 14 Nov 2012 at 8:41

GoogleCodeExporter commented 9 years ago
Then we need (at least) some logs
http://code.google.com/p/gtalksms/wiki/GenerateAppLog

*and*

the trace of the XMPP stanzas that I request in #3

Original comment by fschm...@gmail.com on 15 Nov 2012 at 9:25

GoogleCodeExporter commented 9 years ago
I ran into the same issue. Cannot connect to ejabberd server. Openfire server 
is ok.
I attached the asmack log.
ejabberd server is jappix.com
user: testabc@jappix.com
password: 123456
can login with pidgin

Original comment by hongbin....@gmail.com on 23 Mar 2013 at 6:54

Attachments:

GoogleCodeExporter commented 9 years ago
Reopen because we get these reports @ aSmack too. See 
https://github.com/Flowdalic/asmack/issues/30

Original comment by fschm...@gmail.com on 28 Mar 2013 at 12:39

GoogleCodeExporter commented 9 years ago
Oh and thanks @hongbin.li87 for providing the log. Good job! :)

Original comment by fschm...@gmail.com on 28 Mar 2013 at 12:45

GoogleCodeExporter commented 9 years ago
@hongbin.li87 The server sends a not-authorized failure stanza after the SASL 
challenge

<failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
  <not-authorized/>
</failure>

That usually indicates a wrong username/password.

Original comment by fschm...@gmail.com on 28 Mar 2013 at 1:26

GoogleCodeExporter commented 9 years ago
I have had the same issue with ejabberd and simly used the local part (all 
before the @ of the jid) as username and the password and changed the server in 
the settings. this worked without any issue now. HTH

Original comment by ronny.bo...@googlemail.com on 21 Feb 2014 at 9:43