CCCHH/ansible-infra
CCCHH/ansible-infra
Watch
3
2
Fork
You've already forked ansible-infra
 1
Code Issues 19 Pull requests 17 Wiki Activity Actions

Make Jitsi JVB work correctly with IPv6
All checks were successful
/ build (push) Successful in 25s
Details
/ Ansible Lint (push) Successful in 3m43s
Details

Browse source 
Since the Jitsi Docker Compose stack does not properly take IPv6 into consideration, patch the JVB config to add mappings from the private IPv6 address of the Docker network to the public IPv6 address.

This should be the source of the reported problems with conferences with 3+ people.
This commit is contained in:
Stefan Bethke 2026-10-20 15:34:05 +02:00
commit ce96105463
9 changed files with 76 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
roles/jitsi/README.md
View file

@ -35,8 +35,14 @@ Should work on Debian-based distributions.
- `jitsi__timezone`: The time zone for the containers.
Defaults to `Europe/Berlin`.
- `jitsi__jvb_advertise_ips`: List of IP addresses the JVB should advertise for media (`JVB_ADVERTISE_IPS`).
- `jitsi__jvb_advertise_ips`: List of IP addresses the JVB should advertise for media.
IPv4 addresses are put into `JVB_ADVERTISE_IPS`, which docker-jitsi-meet maps to the IPv4 address of the JVB container.
IPv6 addresses are mapped to the IPv6 address of the JVB container in `custom-jvb.conf` instead, for which the `meet.jitsi` network gets a fixed IPv6 subnet and the JVB a fixed IPv6 address.
Defaults to `[ ]`.
- `jitsi__ipv6_subnet`: The IPv6 subnet of the `meet.jitsi` network, if IPv6 addresses are advertised.
Defaults to `fd4a:7c1e:93b5:1::/64`.
- `jitsi__jvb_ipv6_address`: The IPv6 address of the JVB container within `jitsi__ipv6_subnet`.
Defaults to `fd4a:7c1e:93b5:1::10`.
- `jitsi__whiteboard`: Whether to deploy the Excalidraw whiteboard backend (`whiteboard.yml`).
Defaults to `false`.
- `jitsi__turn`: Whether to deploy coturn and configure Jitsi to use it.