Hello everyone,
I am setting up a development environment for custom UI work on BigBlueButton 3.0. I am experiencing a persistent "Oops, something went wrong" blue screen when attempting to join a meeting, despite a clean check from the configuration tools.
Environment & SetupVersion: BigBlueButton 3.0
Installation: Installed via bbb-install.sh using -v focal-300.
OS: Ubuntu 20.04.6 LTS (Focal)
VM Environment: Local VirtualBox VM.
Networking: Running on a local IP (10.0.2.15).
SSL: Configured with a self-signed certificate for local development.
When accessing the server via HTTPS, the landing page loads, but joining a meeting results in the "Oops, something went wrong" error.
Diagnostic Observations:
bbb-conf --check: Returns no errors. All requirements appear satisfied.
Systemd Services: When checking the status of the HTML5 components, systemctl status bbb-html5 (and variants like bbb-html5-backend/frontend) returns Unit service could not be found.
Package Status: dpkg -l | grep bbb-html5 confirms that bbb-html5 is indeed installed (ii 1:3.0-1580).
Browser Console: I am seeing warnings related to resources being requested over http instead of https, and navigator.mediaDevices being unavailable due to the insecure context/mixed content, even though the main page is accessed via the self-signed HTTPS.
It appears that the installation package is present, but the systemd service units for the HTML5 client are either not being created or not registered correctly in this v3.0 build.
Has the service naming convention changed in v3.0 beyond the backend/frontend split?
Is there a known issue with the focal-300 post-install scripts failing to register services when a local IP/self-signed cert is detected?
What is the recommended way to force the regeneration of the HTML5 service units in this version?
Any insights would be greatly appreciated as I need to align this local environment with our company's v3.0 deployment for UI development.
Best regards,
Prince