Self-Hosting Jitsi: Difference between revisions

Initial
 
expanded and added categories
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
<span id="vars"></span>
= Self-Hosting Jitsi Guide =
== VARS ==


<pre class="yml">matrix_jitsi_enabled: true
This guide provides instructions for self-hosting Jitsi as part of a Matrix Docker setup, covering the main configuration variables, troubleshooting known issues, and managing the service.
 
== Configuration Variables (VARS) ==
 
Add the following configuration options to your `vars.yml` file to enable and configure Jitsi:
 
<pre class="yaml">
matrix_jitsi_enabled: true
matrix_jitsi_enable_guests: true
matrix_jitsi_enable_guests: true
matrix_jitsi_enable_lobby: false
matrix_jitsi_enable_lobby: false
jitsi_prosody_auth_matrix_uvs_sync_power_levels: false</pre>
jitsi_prosody_auth_matrix_uvs_sync_power_levels: false
<span id="trouble-shooting"></span>
</pre>
== Trouble Shooting ==
 
These variables control Jitsi's behavior within your Matrix instance:
 
* `matrix_jitsi_enabled`: Enables Jitsi for video conferencing.
* `matrix_jitsi_enable_guests`: Allows guests to join without an account.
* `matrix_jitsi_enable_lobby`: Enables or disables the Jitsi lobby feature for waiting rooms.
* `jitsi_prosody_auth_matrix_uvs_sync_power_levels`: Syncs Jitsi moderation with Matrix power levels.
 
== Managing Jitsi ==
 
To manage the Jitsi service (start, stop, restart), use the following commands:
 
=== Stopping Jitsi ===
 
To stop only the Jitsi service, run:
 
<pre class="shell">
ansible-playbook -i inventory/hosts setup.yml --tags=stop-group --extra-vars=group=jitsi
</pre>
 
=== Restarting Jitsi ===
 
To stop and then start the Jitsi service, run:
 
<pre class="shell">
ansible-playbook -i inventory/hosts setup.yml --tags=stop-group --extra-vars=group=jitsi; ansible-playbook -i inventory/hosts setup.yml --tags=install-service jitsi
</pre>
 
This will ensure Jitsi is properly restarted after changes or issues.
 
== Troubleshooting ==
 
If you encounter issues, here are a few troubleshooting tips:
 
=== No Moderator Assigned to Calls ===
 
This is a common issue tracked on GitHub. You can check this known issue here: [https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2589 No moderator assigned to calls].
 
As a potential fix, you may need to clean up the Jitsi folder:
 
<pre class="shell">
rm -rf /matrix/jitsi
</pre>
 
=== Sync Power Levels ===
 
Ensure that the following variable is set to `false` if you're having issues with Matrix power level synchronization for Jitsi:


Known Issues: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2589 No moderator assigned to calls
<pre class="yaml">
jitsi_prosody_auth_matrix_uvs_sync_power_levels: false
</pre>


<syntaxhighlight lang="shell">rm -rf /matrix/jitsi</syntaxhighlight>
This prevents Jitsi from syncing moderation with Matrix power levels, which can sometimes cause unexpected behavior.
<pre class="yml">jitsi_prosody_auth_matrix_uvs_sync_power_levels: false</pre>
<span id="restarting"></span>
=== Restarting ===


Stop just jitsi
== Additional Resources ==


<syntaxhighlight lang="shell">ansible-playbook -i inventory/hosts setup.yml --tags=stop-group --extra-vars=group=jitsi</syntaxhighlight>
For more detailed documentation and community support, visit the official Matrix Docker Ansible Deploy [GitHub repository](https://github.com/spantaleev/matrix-docker-ansible-deploy).
Or to stop then to start


<syntaxhighlight lang="shell">ansible-playbook -i inventory/hosts setup.yml --tags=stop-group --extra-vars=group=jitsi; ansible-playbook -i inventory/hosts setup.yml --tags=install-service jitsi</syntaxhighlight>
[[Category:Self-hosting]]
[[Category:Jitsi]]
[[Category:Matrix]]
[[Category:Troubleshooting]]
[[Category:Guides]]