-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Centos 7 installation - xcauth cli working - but Nextcloud won't login chat #81
Comments
Maybe only has to do with permissions somewhere? |
BTW, here's what appears in console.log after failed login via NC
|
Do you have any errors in your ejabberd or sys log? Apparmor installed? |
ejabberd error.log entries: 2019-07-25 09:03:18.786 [error] <0.13210.7>@extauth:handle_info:153 External authentication program '/opt/xmpp-cloud-auth/xcauth.py' has terminated unexpectedly (pid=20136), restarting via supervisor... |
no apparmor |
httpd error log: [Wed Jul 24 02:15:43.324796 2019] [auth_digest:notice] [pid 515] AH01757: generating secret for digest authentication ... |
I notice other parts of ejabberd error log have this as well: 2019-07-25 09:55:49.775 [error] <0.31299.7>@extauth:handle_info:153 External authentication program '/opt/xmpp-cloud-auth/xcauth.py' has terminated unexpectedly (pid=5073), restarting via supervisor... |
I am having the same issue. Setup:
I notice that the docs say that we may need a wrapper, Any ideas how to fix this issue? ejabberd Log:
|
I think I got the same problem after debian buster upgrade. I didn't find a solution and needed to restore the server backup with debian stretch. |
Looks like it's definitely an issue in Buster (I checked and the server it was not working on was running Buster). Looks like staying on Stretch is the way to go currently. |
Are there any error messages in I also fixed #83 today, which was related to startup on newer versions of Debian/Ubuntu. Maybe updating hepls? |
Hi, I'm running on a budget OpenVZ instance GNU kernel 2.6 with miminal Centos 7.
Nextcloud 16 with Ejabberd 18
Centos 7 comes with python 2.7 preinstalled.
I installed python 3 according to https://linuxize.com/post/how-to-install-python-3-on-centos-7/
Installed Berkeley Database so that python- bsddb3 module could be installed.
http://www.linuxfromscratch.org/blfs/view/svn/server/db.html
All done and so I was able to install from source the latest version of xcauth
sudo git clone https://github.com/jsxc/xmpp-cloud-auth
Revised Makefile, here is the diff ouput
_BTW After the build and failed tests, I manually added user ejabberd to group xcauth and vice versa to see if that was my issue, this command that I commented out above perplexes me "adduser ejabberd xcauth;" I just get the "--help" screen when I try that command on my Centos server _
Here is my xcauth.conf
ejabberd.yml
`
systemctl status ejabberd :
OK so, let's test this baby...
command line, wow! it seems to work... it seems to affirm that user db5d has a matching pw.
But when I try via Nextcloud... does not work.
I'm not getting any log entries in my /var/log/xcauth/ folder which has permissions shown below. I tried changing owner to root, apache and xcauth, but still no logs appear.
Here are bosh stanzas after failed login attempt.
file: 'settings'
{"JSON":{"result":"success","data":{"serverType":"external","loginForm":{"enable":true,"startMinimized":false},"screenMediaExtension":{"firefox":"","chrome":""},"xmpp":{"url":"/bosh","domain":"aho.we1.cloud","resource":"","overwrite":true,"onlogin":null},"adminSettings":{"xmppDomain":"aho.we1.cloud"}}},"Response payload":{"EDITOR_CONFIG":{"text":"{\"result\":\"success\",\"data\":{\"serverType\":\"external\",\"loginForm\":{\"enable\":true,\"startMinimized\":false},\"screenMediaExtension\":{\"firefox\":\"\",\"chrome\":\"\"},\"xmpp\":{\"url\":\"\\/bosh\",\"domain\":\"aho.we1.cloud\",\"resource\":\"\",\"overwrite\":true,\"onlogin\":null},\"adminSettings\":{\"xmppDomain\":\"aho.we1.cloud\"}}}","mode":"application/json"}}}
bosh (1 of 2)
<body xmpp:version='1.0' authid='3432347219603930566' xmlns='http://jabber.org/protocol/httpbind' sid='fdd10f2e385854cb2150730e7fb4fc8a7d130348' wait='60' ver='1.11' polling='2' inactivity='30' hold='1' xmpp:restartlogic='true' requests='2' secure='true' maxpause='120' xmlns:xmpp='urn:xmpp:xbosh' xmlns:stream='http://etherx.jabber.org/streams' from='aho.we1.cloud'><stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism><mechanism>X-OAUTH2</mechanism></mechanisms><register xmlns='http://jabber.org/features/iq-register'/></stream:features></body>
bosh (2 of 2)
<body xmlns='http://jabber.org/protocol/httpbind'><failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><not-authorized/><text xml:lang='en'>Invalid username or password</text></failure></body>
And so it says I have invalid user name or password, yet am using correct un/pw.
Thank you for you time in helping troubleshoot this!
The text was updated successfully, but these errors were encountered: