Silent failure: HTML5 bundle missing after jammy-300 install

[viminc-22]

I’m deploying BigBlueButton 3.0 on Ubuntu 22.04 using jammy-300.
The install completed without errors, but the HTML5 bundle was missing (/usr/share/meteor/bundle), and port 3000 was closed.
bbb-html5 was marked installed, but no files were present.
I resolved it by manually cloning bbb-html5, running npm install and npm run build, and copying the bundle manually.
I’m sharing this in case others encounter the same silent failure.
Would love to know if this is a known issue or if a patch is planned.

[ffdixon]

The install completed without errors, but the HTML5 bundle was missing (/usr/share/meteor/bundle), and port 3000 was closed.

BigBlueButton 3.0 does not use meteor anymore, so there is no /usr/share/meteor/bundle directory, nor does it use port 3000.

I'm not sure it completed without errors. Check /var/log/apt/term.log -- do you see any errors?

[viminc-22]

I understand BigBlueButton 3.0 no longer uses Meteor or port 3000, so this may reflect a transition in architecture. If there’s a new intended path for serving the HTML5 client, I’d be grateful for guidance.

[viminc-22]

it wasn’t obvious during install, and there were no error messages to guide recovery

[gustavotrott]

The new client directory is /usr/share/bigbluebutton/html5-client

[viminc-22]

The HTML5 client isn’t functioning properly—whether due to routing, missing assets, or service conflicts—therefore BBB does feel unstable and hence unusable, even if the backend services are running. Is anyone else experiencing the same.

[gustavotrott]

Browser console logs or network tab print would be helpful for us to understand the issue!

[viminc-22]

I may have confirmed:
• Nginx is correctly serving the HTML5 client
• HAProxy is routing securely on port 443 → 81
• The favicon is missing (404), which is cosmetic
• The issue lies in index.js, line 37
I’d appreciate your insight into whether this Auth.set function is part of your integration or if it should be refactored or removed.

[viminc-22]

[Report Only] Refused to frame 'https://ogs.google.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self'".
Understand this error
[Report Only] Refused to frame 'https://ogs.google.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self'".
Understand this error
csp.withgoogle.com/csp/frame-ancestors/a00d54fdef4a77536baac3725d1409f8:1 POST https://csp.withgoogle.com/csp/frame-ancestors/a00d54fdef4a77536baac3725d1409f8 net::ERR_FAILEDUnderstand this error