Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

bosh Setting Cannot Be Overwritten in config.js

See original GitHub issue

This Issue tracker is only for reporting bugs and tracking code related issues.

Before posting, please make sure you check community.jitsi.org to see if the same or similar bugs have already been discussed. General questions, installation help, and feature requests can also be posted to community.jitsi.org.

Description

The bosh setting in config.js cannot be overwritten on the client through configOverwrite.

Current behavior

Jitsi will always use the bosh setting specified in the server-side config.js.

Expected Behavior

Jitsi uses the bosh setting specified in the configOverwrite option passed to JitsiMeetExternalAPI.

Possible Solution

Either fix this or improve the documentation. It seems like the connection is set up before the room is created, so this may be a mess to fix.

Steps to reproduce

Pass a different bosh value in the configOverwrite value passed to JitsiMeetExternalAPI. It will not be used.

In my case this was causing JWT authentication to fail until I set it on the server. However, I’d like to avoid server-side overwrites since I’m using the Docker setup and that requires patching each time a new set of containers is released.

Issue Analytics

State:
Created 3 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

saghulcommented, Apr 29, 2020

Again, overwriting bosh may not be smart, but then please adjust the documentation so that it’s clear that it can’t be done.

Not sure what is a goodd place to document this, TBH.

And, again, not allowing this setting to be overwritten makes it much harder to customize your Jitsi configuration when using the Docker containers. Essentially each time you update your Docker images you have to do the following:
* Remove the configuration directory

* Restart the Jitsi docker images so that they regenerate their configuration from the .env file

* Patch the resulting configuration to preserve any local changes—for example, modify the bosh setting to use a websocket connection

* Restart the Jitsi docker images again
This is both fiddly and leads to unnecessary downtime. (FYI: having the images regenerate their configuration from scratch is required because new configuration settings and defaults get added.)

I know. We are working to make this easier, but things take time. As for WebSocket support, there is an open PR for it, once ready it will be one env var change away.

0reactions

jeremythastingscommented, Mar 1, 2021

Thanks for the assistance!

Top Results From Across the Web

Configuring BOSH Director on vSphere - VMware Tanzu Docs

Click the BOSH Director for vSphere tile. Select vCenter Config. Configure the one or more vCenters that host your Ops Manager foundation.

Again,,TOOLBAR! - Install & Config - Jitsi Community Forum ...

If the user has not // interacted with the webpage before the getDisplayMedia call, the promise will be rejected by the browser. ......

BIS Configuration Guide_en

Resizing the help window. Drag the corner or edge of the window to the desired size. Further conventions used in this documentation.

overriding config.js variables for express/node app based on ...

Why not use one JSON file with settings for all the environment. Your approach may not scale well when you introduce more environments....

Self-Hosting Guide - Docker | Jitsi Meet - GitHub Pages

Cannot read property 'getUserMedia' of undefined or navigator.mediaDevices is undefined. If you want to use jigasi too, first configure your env file with ......