I've been struggling through the setup and configuration of this module, and have made some progress:

I'm using ejabberd on a debian server.
I've got an admin account set up, which I can access using GAIM.
I've got http-bind set up and properly redirecting (no more 404's in the watchdog).

However, anytime I hit the 'Launch chat' button, I get an offline status, which cannot be changed. Additionally, new users are not registered in ejabberd. I have the following settings in place:

from admin/xmppframework/client:
(Not checked): Launch XWChat Client on user Login
XWChat HTTP Mode: HTTP Bind
XWChat Authentication Type: NONSASL
XWChat Mutli-User Chat Conference Server: xmpp.example.com
XWChat Jabber User Directory: xmpp.example.com
XWChat Locale Setting: English

from admin/xmppframework/settings:
XMPP API: XMPP API

from admin/xmppframework/user:
(checked) Show XMPP User Password Field
(checked) Show XMPP User Resource Field
(not checked) Store Login password as XMPP Password
XMPP Server Domain: xmpp.example.com
(checked) Provision XMPP for Drupal Users

from admin/xmppframework/xmpp_api:
XMPP Server: xmpp.example.com
XMPP Port: 2222
Admin JID: admin@xmpp.example.com
Admin JID Password: ********
Admin JID Server: xmpp.example.com

Please, if there's anything I'm missing, please let me know. I'm not using LDAP (and don't even know what that means).

Thanks,
Aaron

Comments

aaron’s picture

aaron commented

for reference, here's my ejabberd setup:

sudo su
apt-get ejabberd
ejabberdctl register admin xmpp.example.com password

in vim /etc/ejabberd/ejabberd.cfg:

{acl, admin, {user, "admin", "xmpp.example.com"}}.
{listen,
[
  ...
  {5280, ejabberd_http, [
                         {http_bind,
                         http_poll,
                         web_admin
                        ]}
]}.
{modules,
[
  ...
  {mod_http_bind,  []},
]}.

misc:
open up ports 5222 and 5280 in the firewall
redirect example.com/html-bind/* to xmpp.example.com:5280/html-bind/* in apache

aaron’s picture

aaron commented
Status: Active » Fixed

working now. apparently, mod_proxy default policy is deny...

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.