Issues with joining a conference set up by lib-jitsi-meet in a headless browser environment

Other Questions Headless Browser
1

I’m attempting to start a conference utilizing lib-jitsi-meet in a headless Chrome setup with Puppeteer and want to join it from a separate browser using the Jitsi External API (iframe API). Although I can successfully initiate a meeting in the headless environment, I face a problem when trying to access that meeting from another browser. Instead of joining the existing conference, a new one with the same title is created, leaving me as the sole participant. I would greatly appreciate any suggestions or guidance regarding this issue. Here’s a snippet of my Puppeteer setup:

const puppeteer = require('puppeteer');
const browser = await puppeteer.launch({
    headless: false,
    product: 'chrome',
    defaultViewport: { width: 1600, height: 1600 }
});
const page = (await browser.pages())[0];
await page.goto('https://jitsi-liveroom.s3.eu-central-1.amazonaws.com/index.html');
2

It sounds like there might be an issue with how the connection or the room name is being handled between the headless browser and the regular browser. The first thing to check is the server you are connecting to, ensuring both clients are reaching the same host and that your headless setup isn’t inadvertently creating a new session. Also, verify any authentication or domain restrictions, as these could be silently affecting the connections. Try logging the room name on both ends to confirm consistency. You might also want to explore session persistence settings in your Puppeteer setup to ensure continuity between the instances.