-
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
Install on FreeBSD? #35
Comments
I would guess that it only differs in the I haven't been doing *BSD work in the past decade, so I would be glad if someone (you?) could add the appropriate user/group additions. Otherwise, instead of running (On an unrelated notice, if you know your way around *BSD: Would you be willing to write a replacement for the |
@MarcelWaldvogel Thanks for the info. I really would love to help do that. Unfortunately I'm just not experienced enough yet. Above the basics, I'm learning as I go. Sorry that's not helpful now. If I get enough figured out to be able to contribute, I will. |
I'm still attempting this install but I've got a question: On this page: https://github.com/jsxc/xmpp-cloud-auth/blob/master/doc/Installation.md It's written to set:
But in the yml file contents you provide here: https://github.com/jsxc/xmpp-cloud-auth/wiki/ejabberd It's a different script:
Which one should I be using? |
Just wanted to update and ask a for some input. I've managed to get ejabberd running. Got the plugin installed in the nextcloud and the bosh url gave green checkmark. I added the api url and secret key to the xcauth.conf file (which I have where your code is installed and one in /etc/) wasn't sure which... and when I log into NC (after logging out) I don't get logged into chat. I checked logs and not seeing any adds there. Not sure yet, is ejabberd supposed to be executing your code through the .sh file I give path to? Do I need to manually run/start xcauth? Would very much appreciate some input to troubleshoot this. Here's what I have in console:
Also wanted to add that trying the ejabberd.yml file contents from wiki did not work. I restored yml that came with ejabberd, but changed the enternal auth, hosts, and ip and only then was able to get ejabberd responding to requests and bosh url in NC greenlighted. Thank you for your help. One more thing... This is what I'm using with nginx within the NC server block:
Which worked with this added to the modified default ejabberd.yml:
|
Figured I'd keep updating this... hoping to get a reply with any suggestions. In my quest to make this work, trying things and looking at logs, and back at docs (endless loop :) it seems) I have made some progress and found more info. First, before I forget, on: https://github.com/jsxc/xmpp-cloud-auth/wiki/ejabberd In the ejabberd.yml example and diffs, you have "use_auth_cache" and that should be "auth_use_cache" as written in the description "This cache interferes with multiple valid passwords (app passwords, tokens) and thus needs to be deactivated with auth_use_cache: false." Currently, if I login with an NC admin account, login is quick. Non admin hangs till the "wait" time and then eventually redirects to files. Haven't yet determined why. In either case, upon login I'm still not logged into chat. Logs: /var/log/xcauth/xcauth.err
There is db file: /var/cache/xcauth/user-cache.db.db and seems it's updated based on size and modtime. /var/log/xcauth/xcauth.log
/var/log/ejabberd/error.log
/var/log/ejabberd/ejabberd.log
Also trying to login with pidgin produced this: /var/log/ejabberd/crash.log
I'm not sure yet, but search lead me to an issue with BOSH on ejabberd which may be playing a role here: |
The script's name is now `xcauth.py`. Feel free to correct it.
|
What happens when you try to manually log in? (Maybe the JSXC app is not active)
|
Do you mean by clicking relogin in the sidebar after logging into NC? Same thing as when logging into NC. Other lines in below log are same as sample above. Console:
Only /var/log/ejabberd/ejabberd.log has been written to this attempt:
|
@MarcelWaldvogel |
@MarcelWaldvogel |
I'm trying to get ejabberd and xmpp-cloud-auth up and running on FreeBSD but the install.sh is not setup for FreeBSD. Any plans for FreeBSD installs?
The text was updated successfully, but these errors were encountered: