Code 1001
Category: AudioMessage shown in BigBlueButton
WebSocket disconnected (error 1001)
What it means
The browser lost the audio signalling WebSocket (microphone or listen-only) after it had connected.
Likely causes
- Unstable Wi‑Fi or VPN disconnect
- Browser tab slept or laptop closed the lid
- Corporate proxy blocking WebSockets
What to do
First, check who is affected.
- Only one or a few users: most likely a problem on the user's side, so follow the Student and Teacher steps.
- Everyone in one room: check that room/meeting (settings, meeting ended or recreated, room limits).
- Everyone in every room: most likely a server problem, so go to the Admin/server steps.
Students
Reload the page, rejoin the session, and use a wired connection if possible. Try Chrome, Firefox, or Edge (latest version). Check your internet connection (Wi‑Fi signal or cable) before rejoining.
Teachers
Ask participants to refresh. If many users fail at once, check server load and WebSocket settings on the reverse proxy.
Server admins
Ensure nginx proxies WebSocket upgrades to bbb-webrtc-sfu; check bbb-webrtc-sfu logs (journalctl -u bbb-webrtc-sfu). Check that nginx runs and its config is valid (sudo nginx -t, /var/log/nginx/error.log). Run sudo bbb-conf --clean, then sudo bbb-conf --watch while reproducing the error to see log errors live.
Upstream source
- v3.0.x-release · bigbluebutton-html5/public/locales/en.json · app.audioNotification.audioFailedError1001
Dataset ref: v3.0.x-release