It looks like there is a small typo in jitsi-meet-prosody.postinst:
# For those deployments that don't have the config in the jitsi-meet prosody config add the new jaas file
if [ ! -f $JAAS_HOST_CONFIG ] && ! grep -q "VirtualHost \"jigasi.meet.jitsi\"" $PROSODY_HOST_CONFIG; then
cp /usr/share/jitsi-meet-prosody/jaas.cfg.lua $JAAS_HOST_CONFIG
sed -i "s/jitmeet.example.com/$JVB_HOSTNAME/g" $JAAS_HOST_CONFIG
This ends up with /etc/prosody/conf.d/jaas.cfg.lua that has the following inside:
The domain name is not properly replaced, it doesn’t work and there is error in prosody. It should either be:
sed -i "s/meet.jitsi/$JVB_HOSTNAME/…
or the template should be with “jitmeet.example.com” instead of “meet.jitsi”.
That should be a warning, not an error, right?
The certificates for non of the virtual host is actually used and all a self signed. The connection is done using http for the bosh and websocket on localhost.
The only exception is maybe the vhosts for jibri and jvb where those components connect on 5222…
And if I remember correctly some of those warnings go away if you disable the https thingy with: