A class is about to start, a student clicks to join the audio, and instead of a voice they get a short message with a number in it. The teacher has a room full of people waiting, and nobody knows what the number means.
BigBlueButton shows these codes on purpose: each one points to a specific part of the connection that failed. Once you know what the code refers to, the fix is usually quick.
How to use BBBerror
BBBerror is a free lookup for BigBlueButton error codes (for BigBlueButton 3.0.x; not affiliated with BigBlueButton). It works in three steps:
- Search the code you see on screen, for example 1007.
- Read what it means and the most likely causes.
- Follow the fix for your role: there are separate steps for students, teachers and server admins.
Before following the steps, check who is affected. If only one or a few users see the error, the problem is most likely on their side. If everyone in one room sees it, look at that room or meeting. If everyone in every room sees it, it is most likely a server problem.
Common error code families
WebSocket errors: 1001 and 1002
1001 – "WebSocket disconnected" means the browser lost the audio signalling connection after it had connected. Typical causes are unstable Wi‑Fi, a VPN disconnecting, or the laptop going to sleep. Students: reload the page, rejoin and use a wired connection if possible, in an up-to-date Chrome, Firefox or Edge. Server admins: make sure nginx proxies WebSocket upgrades to bbb-webrtc-sfu and check its logs. Full steps for 1001.
1002 – "Could not make a WebSocket connection" means the browser could not open the connection to the audio service at all, often because a firewall or proxy blocks it. Students: try another network such as a mobile hotspot and disable strict VPN browser extensions. Teachers: make sure everyone uses the official join link from your LMS or invitation. Server admins: verify TLS certificates, DNS and the nginx configuration, then run sudo bbb-conf --check. Full steps for 1002.
ICE connection errors: 1007 and 1010
1007 – "Connection failure" means the audio connection could not be negotiated, often because UDP traffic is blocked. Students: allow microphone permission, then leave the audio and join again; on school Wi‑Fi, try mobile data once to confirm a firewall issue. Teachers: suggest a wired connection for the presenter and share the network requirements with IT. Server admins: check the TURN (coturn) configuration and that the UDP media range is open. Full steps for 1007.
1010 – "Connection negotiation timeout" means the audio connection timed out before it was established. Students: wait a few seconds, close other video calls using bandwidth, then leave and rejoin the audio. Full steps for 1010. (Code 1011 is a legacy code that BigBlueButton 3.0 no longer shows to users.)
Screen sharing errors: 11xx
Codes in the 1100 range relate to screen sharing. 1101 means screen sharing lost its connection to the media server: keep the meeting tab focused and click Share screen again. 1102 means it could not connect at all: try another network to check whether yours blocks the connection. 1104 means the shared screen could not be played in the browser: try a different browser or device, and update to a supported version. See all screen sharing codes.
Test your room before class
Many of these errors can be caught before anyone is waiting. The free Room Tester checks microphone, camera and connection before class, so class starts on time.
If it keeps happening
If the same error comes back for many users, or for everyone on the server, the cause is usually in the server setup rather than in each browser. Our hosting team can help you find and fix it.
