Integrate BigBlueButton with Nextcloud

01

Choose the supported integration path

Nextcloud’s BigBlueButton Integration app provides the supported user-facing route. Match the app release to the Nextcloud major version shown in the App Store before enabling it.

• Supported Nextcloud and PHP release.
• Compatible BBB app version from the Nextcloud App Store.
• BBB/Scalelite URL, secret and administrator access.

02

Prepare BigBlueButton and credentials

Use a production BigBlueButton endpoint with a trusted TLS certificate. Keep the API shared secret or LTI secret on the server side: it is equivalent to an application credential and must never be placed in browser code, a public repository or a screenshot.

1. 1

   Confirm the BigBlueButton server is healthy and that its public hostname resolves correctly.

2. 2

   Retrieve the API URL and shared secret with sudo bbb-conf --secret, or create a dedicated LTI key and secret where the integration uses LTI.

3. 3

   Record the platform version, connector version, owner and rollback point before making the change.

sudo bbb-conf --check
sudo bbb-conf --secret

03

Configure Nextcloud

Make the first connection in a staging course, workspace or tenant. Use a dedicated test teacher and test learner so role mapping can be observed rather than inferred from an administrator account.

1. 1

   Open Apps, search for BigBlueButton Integration and verify the release supports your Nextcloud major.

2. 2

   Install and enable the app, then open its administration settings.

3. 3

   Enter the BBB API URL and secret and configure room-creation permissions.

4. 4

   Create a room from a test user account and share it with a controlled group.

04

Run an end-to-end acceptance test

A green “connection successful” message proves only that one API request worked. The useful test follows the complete classroom lifecycle from creation through recording publication.

1. 1

   Join from two Nextcloud accounts and one unauthorized account.

2. 2

   Verify moderator assignment, lobby/guest behaviour and screen sharing.

3. 3

   Record, end and confirm playback/listing behaviour.

4. 4

   Upgrade the app in staging against the next Nextcloud major before core upgrade.

05

Common problems and practical fixes

Start with timestamps, browser developer tools and the logs on both sides. Repeatedly replacing secrets rarely fixes a hostname, TLS, role or callback problem and makes the evidence harder to follow.

• “Server not reachable” often means URL path, TLS trust or outbound firewall.
• App version incompatibility can disable the app during a Nextcloud upgrade.
• Use group restrictions so every user cannot create unrestricted public rooms by default.

06

Production hardening and upgrades

Restrict who can create rooms, define recording retention, test accessibility and document the integration owner. Pin or approve connector updates, subscribe to upstream releases and repeat the acceptance test after changes to the LMS, connector, BigBlueButton or reverse proxy.

• Do not expose the BigBlueButton shared secret to course authors or client-side JavaScript.
• Use least-privilege teacher roles and test guest, suspended and unenrolled users.
• Monitor API errors, failed joins, recording processing and disk growth.
• Keep a short rollback runbook: previous package, configuration backup and maintenance window.