Aaron van Meerten

Yeah seems good to me.

Yes, it's clear that some of our automation will not work as expected with a list in XMPP_SERVER. Jigasi in particular I'll need @damencho to help me with, as I'm...

> Won't this break scalable infrastructure like K8s? > > For example using multiple JVBs with one WS proxy won't work with these changes This is true, I was considering...

> Couldn't one just allow a regex for the WS_SERVER_ID and carry the matched text over into the proxy_pass? I.e. just make what previously was `([a-zA-Z0-9-\.]+)` configurable. It seems to...

It is not recommended, as jibri-spawned chrome uses quite a bit of CPU, as does the jitsi-videobridge. Your best performance will be if they are on separate instances.

Is the public address of the site different than the one that jibri is trying to connect to? We've seen this problem when jibri assume the xmpp domain name is...

So there's two pieces. The xmpp_domain is the string that will be used when talking to the XMPP server. But then when the jibri starts selenium/chrome, it will generate a...

Configure your jitsi meet instance (the prosody part, but also config.js in jitsi-meet) to use the same xmpp domain to match your web-accessible URL.

This all looks correct to me. There's nothing immediately obvious to me about what is wrong with your configuration. I'll continue to review but maybe some of the other team...

The https requirement comes from the fact that Jibri uses Chrome to connect to the meeting. Chrome in turns requires https to properly fully support WebRTC functions. Hence, Jibri requires...