I know you can run a Jitsi server on a Raspberry Pi 4. But is it any good? That's something I wanted to find out.
Have questions about your setup? Ask in our forums.
Check out the IL Wishlist for upcoming project ideas.
Hi there!
I really enjoyed this youtube video and I have followed the post as exactly as possible however, I'm stuck. Whenever I try to start a jitsi meet I have to authenticate. I do that then I have to say "I am the host". I click that and authenticate again and it just goes round and round in circles.Â
I have set jitsi up at meet.mydomain.com and I have tried these username combinations:
myusername
myusername@mydomain.com
myusername@meet.mydomain.com
I believe that the correct username should be myusername@meet.mydomain.com
Any suggestions on how I can debug this issue?
Thanks 😀
@deskimo The username will be the one chosen on step 16 of the guide.
sudo prosodyctl register user your_domain password
Â
If my domain was meet.interface.com and my user was venn using 12345 as the password, it would look like this.
sudo prosodyctl register venn meet.interface.com 12345
When logging into a room, my username would be venn and the password would be 12345.
Check out the IL Wishlist for upcoming project ideas.
Thanks so much for the response. I realize now that authentication is actually working (I think). While logging in, I have a ssh window open and did: tail -f /var/log/prosody
I can see that I am authenticating but whenever I click "I am the host" two lines are added to the prosody log and it ends with "session close". (I substituted my domain in the following lines.)
May 27 20:10:04 bosh3fba0aa5-454c-4434-9e84-dfb284b53d6d info Authenticated as dan@meet.mydomain.com
May 27 20:10:06 bosh3fba0aa5-454c-4434-9e84-dfb284b53d6d info BOSH client disconnected: session close
May 27 20:10:07 mod_bosh info New BOSH session, assigned it sid '79772bac-3c95-4e63-b6a4-53eb0691fe54'
May 27 20:10:07 bosh79772bac-3c95-4e63-b6a4-53eb0691fe54 info BOSH client disconnected: session close
May 27 20:10:10 mod_bosh info New BOSH session, assigned it sid 'f05c36f5-bd80-49e2-bcec-40f689806de9'
May 27 20:10:10 boshf05c36f5-bd80-49e2-bcec-40f689806de9 info Authenticated as dan@meet.mydomain.com
May 27 20:10:14 mod_bosh info New BOSH session, assigned it sid '3122e86b-64af-4731-8728-6acd7bc3979d'
May 27 20:10:14 bosh3122e86b-64af-4731-8728-6acd7bc3979d info BOSH client disconnected: session close
Any ideas as to what I need to do?Â
Are you running the exact versions from the guide with a Raspberry Pi 4?
jitsi-meet=2.0.8719-1 jicofo=1.0-1038-1 jitsi-meet-web=1.0.7322-1 jitsi-meet-web-config=1.0.7322-1 jitsi-meet-prosody=1.0.7322-1 jitsi-videobridge2=2.3-25-g1da507fa-1 jitsi-meet-turnserver=1.0.7322-1
Â
I pinned those specific versions because they were the only ones that functioned correctly on my Raspberry Pi 4.
Check out the IL Wishlist for upcoming project ideas.
This is command I did to install (copied from my history):
sudo apt install jitsi-meet=2.0.8719-1 jicofo=1.0-1038-1 jitsi-meet-web=1.0.7322-1 jitsi-meet-web-config=1.0.7322-1 jitsi-meet-prosody=1.0.7322-1 jitsi-videobridge2=2.3-25-g1da507fa-1 jitsi-meet-turnserver=1.0.7322-1
I must have messed up along the way, I'm thinking of wiping and trying it all again 😉
Nuke and pave, while not optimal, is a completely valid option with jitsi.
It's been seven months since the original guide, and the latest version of jitsi may work out of the box.
If you want to give that a try.
sudo apt-get -y install jitsi-meet
Check out the IL Wishlist for upcoming project ideas.