I have an ejabberd served with external authentication which is working fine supporting a notification system for my web application. (currently I´m using Strophe.js to perform XMPP over BOSH connection)
Due some new requirements I need to implement the xmpp bosh communication over HTTPS using TLS, but I could not make it work.
My ejabberd.cfg is configured like this:
{listen,
[
{5280, ejabberd_http, [
%%{request_handlers, [
%% {["web"], mod_http_fileserver}
%%]},
{certfile, "C:\\Program Files (x86)\\ejabberd-2.1.10\\conf\\server.pem"}, tls,
captcha,
http_bind,
http_poll,
web_admin
]}
]}.
I tried to connecting using jwchat, strophe.js and even with pidgin xmpp client. In all the cases, the connection is not achieved correctly.
Is there any step missing? Should I use extra proxies or something like that to make it work?
Thanks in Advance,
Renato.
It works correctly for me
It works correctly for me using ejabberd 2.1.13 configured like you:
... {5282, ejabberd_http, [ {certfile, "/etc/ejabberd/ssl.pem"}, tls, http_bind, web_admin ]}, ...Then I started the client Gajim 0.14.4, configured an account with Connection, Proxy, Type: BOSH, and URL BOSH:
It can login correctly, Gajim shows the lock icon, and ejabberd logs:
=INFO REPORT==== 24-Sep-2013::19:30:39 === I(<0.440.0>:ejabberd_listener:281) : (#Port<0.4427>) Accepted connection {{127,0,0,1},54799} -> {{127,0,0,1},5282} =INFO REPORT==== 24-Sep-2013::19:30:39 === I(<0.460.0>:ejabberd_http:146) : started: {tls, {tlssock,#Port<0.4427>, #Port<0.4428>}} =INFO REPORT==== 24-Sep-2013::19:30:40 === I(<0.462.0>:ejabberd_c2s:787) : ({socket_state,ejabberd_http_bind,{http_bind, <0.461.0>,{{127,0,0,1},54799}},ejabberd_http_bind}) Accepted authentication for user11 by [] =INFO REPORT==== 24-Sep-2013::19:30:40 === I(<0.462.0>:ejabberd_c2s:941) : ({socket_state,ejabberd_http_bind,{http_bind, <0.461.0>,{{127,0,0,1},54799}},ejabberd_http_bind}) Opened session for user11@localhost/Gajim