-
Notifications
You must be signed in to change notification settings - Fork 26
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
Playbook not working any more for Debian 10? #21
Comments
Hi, the playbook does not install jitsi-meet-tokens. I don't know what modifications that package does to the resulting install but it shouldn't be required when using this playbook. |
Hi, but how is token based authentication working as described under "User authentication support"? |
The jitsi-meet-tokens package does not install anything, it simply modifies configuration files. That's the same thing the ansible playbook does. So if you install it (jitsi-meet-tokens) you may break the playbook's work. Logs may be helpful in order to debug your installation not working. |
I didn't install the token-plugin when i used the playbook. I only installed it, when installing jitsi on my own. Well, as i told you: the playbook runs through without errors, but then jitsi is not working. in older installations it worked fine. |
Thanks for the offer. I'll try to set up a new VM to test it and get back to you as time permits. |
Thank you very much! |
Hello inittab, |
Hi, I'm sorry I didn't have the time. I'll try to look at it this week, hopefully tomorrow, and get back to you. Sorry again. |
Hi, I'm very sorry this took so long. I think the issue was the jicofo user was not created in prosody. My last commit fixes that. Please let me know if that fixes it for you. Else, please send me as much logs as possible after the playbook is run. Thanks, Alberto |
Hi, thanks for trying to help, but it still doesn't work. I get an "Unfortunately something went wrong" error when opening a meeting. prosody.txt Let me know, if you need other logs. |
Hi, from the jicofo logs, the problem seems to be the one fixed in my commit (Jicofo not authenticating itself in prosody). Did you try the playbook on a new deployment or on one already deployed? Can you check the password value in the "client" section of /etc/jitsi/jicofo/jicofo.conf matches with the one in /var/lib/prosody/auth.YOURDOMAIN/focus.dat. If you check your jicofo and prosody logs, you can see that jicofo first connects OK: Thanks, Alberto |
Hi, Thanks again |
Sorry, I meant /var/lib/prosody/auth.YOURDOMAIN/accounts/focus.dat, yes. Does that file contain: |
Hello,
one year ago I installed Jitsi with this playbook and it worked like a charm on Debian 10. But now with the newer Jitsi versions Jitsi is not working any more. The playbook installs everything without errors.. But when i call jitsi in the browser, it tries to start but shows the error "something went wrong ..."
I think, that the jitsi-token-modul causes the problems. I installed a normal Jitsi on my own, which worked fine, but after installing token-module also crashed.
I can use an older playbook and manually edit it to use
But this is no solution because Chrome doesn't support this old versions correct anymore.
I use a clean Debian 10 VM on Hetzner cloud.
Thanks for helping.
Oe
The text was updated successfully, but these errors were encountered: