search

getkaiwa / kaiwa

[UNMAINTAINED] A modern XMPP Web client
http://getkaiwa.com
MIT License
1.33k stars 154 forks source link

Help setting up with docker #101

Open dfherr opened 7 years ago

dfherr commented 7 years ago

Is there any mailinglist or irc/slack channel for kaiwa where I can get some help setting it up?

I can get the individual servers started, but for the heck of it can't login to the kaiwa client. I guess because some connection between kaiwa / kaiwa-server / ldap is not correctly setup.

Giving a example configuration for localhost and a simple admin/admin user/user ldap entry would also help a lot.

dfherr commented 7 years ago

To be a little bit more specific. I have postgres, kaiwa, kaiwa-server and ldap running. I have added the security exception by going to https://localhost:5281/xmpp-websocket/

Then i connect to localhost:8000 I see the kaiwa "connecting" and getting a login form. But logging simply returns me back to login or is stuck at connecting. I have no idea why and I guess it's because of wrongly configured environment options. I try to login with the user/userpass or admin/adminpass specified in my ldap config file. I get a error on the kaiwa-server logs (see below)

My ldap has following environment options (the syntax is crane and not the issue):

env:
   - "LDAP_DOMAIN=MyDomain"
   - "LDAP_ORGANISATION=MyOrga"
   - "LDAP_ROOTPASS=ldappass"

and i added the base user file without getting errors

my kaiwa-server:

env:
    - "XMPP_DOMAIN=localhost"
    - "DB_NAME=kaiwa"
    - "DB_USER=kaiwa"
    - "DB_PWD=chatup"
    - "LDAP_HOST=ldap"
    - "LDAP_USER_BASE=ou=users,dc=mygroup"
    - "LDAP_GROUP_BASE=ou=groups,dc=mygroup"
    - "LDAP_DN=cn=admin,dc=mygroup"
    - "LDAP_PWD=ldapper"
    - "LDAP_GROUP=mygroup"

my kaiwa:

env:
   - "XMPP_NAME=kaiwa-server"
   - "XMPP_DOMAIN=localhost"
   - "XMPP_WSS=ws://localhost:5280/xmpp-websocket"
   - "XMPP_MUC=chat.localhost"
   - "XMPP_STARTUP=groupchat/home%40chat.localhost"
   - "XMPP_ADMIN=admin"
   - "LDAP_HOST=ldap"
   - "LDAP_USER_BASE=ou=users,dc=mygroup"
   - "LDAP_GROUP_BASE=ou=groups,dc=mygroup"
   - "LDAP_DN=cn=admin,dc=mygroup"
   - "LDAP_PWD=ldapper"
   - "LDAP_GROUP=mygroup"

ldap log shows:

*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 7

my kaiwa log shows:

Running container kaiwa ...
Configuring dev_config.json...
Configuring kaiwa...
dev environment detected
Client app ready
Cache manifest generated
Kaiwa running...
Hostname:eea2cb810521
Port:8000

and finally my kaiwa-server throws this error 

Apr 25 21:53:06 socket  debug   server.lua: accepted new client connection from 172.18.0.1:38100 to 5280
Apr 25 21:53:06 http.server debug   Firing event: GET localhost/xmpp-websocket
Apr 25 21:53:06 c2s280ffd0  info    Client connected
Apr 25 21:53:06 mod_websocket   debug   Websocket received frame: opcode=1, 94 bytes
Apr 25 21:53:06 c2s280ffd0  debug   Client sent opening <stream:stream> to localhost
Apr 25 21:53:06 c2s280ffd0  debug   Sent reply <stream:stream> to client
Apr 25 21:53:06 mod_websocket   debug   Websocket received frame: opcode=1, 96 bytes
Apr 25 21:53:06 c2s280ffd0  debug   Received[c2s_unauthed]: <auth mechanism='PLAIN' xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
Apr 25 21:53:06 c2s280ffd0  error   Traceback[c2s]: /usr/lib/prosody/modules/ldap.lib.lua:217: attempt to index local 'ld' (a nil value)
stack traceback:
    /usr/lib/prosody/modules/ldap.lib.lua:217: in function 'singlematch'
    /usr/lib/prosody/modules/ldap.lib.lua:187: in function </usr/lib/prosody/modules/ldap.lib.lua:179>
    (tail call): ?
    /usr/lib/prosody/modules/mod_auth_ldap2.lua:54: in function 'plain_test'
    /usr/lib/prosody/util/sasl/plain.lua:72: in function </usr/lib/prosody/util/sasl/plain.lua:38>
    (tail call): ?
    /usr/lib/prosody/modules/mod_saslauth.lua:77: in function </usr/lib/prosody/modules/mod_saslauth.lua:66>
    (tail call): ?
    /usr/lib/prosody/util/events.lua:73: in function </usr/lib/prosody/util/events.lua:69>
    (tail call): ?
    /usr/lib/prosody/core/stanza_router.lua:149: in function 'core_process_stanza'
    /usr/lib/prosody/modules/mod_c2s.lua:244: in function 'func'
    /usr/lib/prosody/util/async.lua:88: in function </usr/lib/prosody/util/async.lua:86>
Apr 25 21:53:31 socket  debug   server.lua: client 172.18.0.1:46776 read error: closed
Apr 25 21:53:31 socket  debug   server.lua: closed client handler and removed socket from list

which seems to tell me ldap isn't reachable or has some other problem. any tips?