Meet configuration requires hardcoded focus component domain

[cbeckr]

By default, hosts.focus is commented out in /etc/jitsi/meet/yourdomain.config.js and will therefore default to focus.<domain>.
Since Jibri's Selenium component connects using recorder.<domain>, it will try (and fail) to find focus on focus.recorder.<domain>.
To work around this, the focus domain must be hardcoded in the config.
Note that this is very tricky to catch via the instructions ("Manually testing Jibri") since it suggests connecting to the regular room URL (sans recorder prefix etc.)

[nightstryke]

@cbeckr can you give an example of what a hardcoded focus domain should look like?

[cbeckr]

@nightstryke if your domain is example.com, you would hardcode the focus domain in config.js (usually in /etc/jitsi/meet) as follows:

var config = {
   ...
    hosts: {
        ...
        focus: 'focus.example.com',
    },

[nightstryke]

my setup is trying to use subdomain.example.com instead of the normal example.com.

[aaronkvanmeerten]

I would very much recommend using the latest java-based jibri from our debian respository. It's easier to use and is much more reliable about getting connected. I'm going to close this issue, but please open a new one if you run into any problems with the new java-based jibri!