Closed sarah4d2 closed 3 weeks ago
Thank you for the detailed report!
Could you check if the following changes to group_vars/matrix_servers
fix the issue for you:
-jitsi_turn_port: "{{ matrix_coturn_container_stun_plain_host_bind_port if matrix_coturn_enabled else '' }}"
-jitsi_turns_port: "{{ matrix_coturn_container_stun_tls_host_bind_port if matrix_coturn_enabled else '' }}"
+jitsi_turn_port: "{{ matrix_coturn_container_stun_plain_host_bind_port.split(':')[-1] if matrix_coturn_enabled else '' }}"
+jitsi_turns_port: "{{ matrix_coturn_container_stun_tls_host_bind_port.split(':')[-1] if matrix_coturn_enabled else '' }}"
That does appear to fix it. Thank you!
I am using the playbook on a machine with multiple external IP addresses. In my vars.yml I have lines like the following:
This works as expected to cause coturn to bind to a.b.c.d, instead of trying to bind 0.0.0.0. However, the complete IP:port string is also passed unchanged into jitsi/prosody/config/conf.d/jitsi-meet.cfg.lua, resulting in broken syntax like this:
Instead of the correct syntax:
This causes Prosody to output a config parse error and fail to start.
The Jitsi vars are being set at group_vars/matrix_servers:3556:
OS: Arch Architecture: amd64