Field diagnostics
Webcam and screen sharing troubleshooting
Camera and screen-share failures look similar to users but take different paths through permissions, browser capture and the media stack. Separate “cannot publish” from “others cannot receive” before investigating.
Executive brief
What matters
- 01
Use two participants on different networks to distinguish publishing from receiving.
- 02
Test camera and screen sharing independently; browser permissions and capture APIs differ.
- 03
If failure grows with concurrency, inspect CPU and network before blaming individual devices.
01
Reproduce with a controlled pair
Create a new meeting with one publisher and one viewer. Record browser versions, operating systems, networks and the exact result: preview absent, publishing spinner, black frame, frozen video or only one viewer affected. Check whether audio works in the same meeting.
02
Resolve capture problems
For webcam, verify operating-system privacy settings, browser permission, selected device and whether another application owns the camera. For screen share, confirm the browser supports capture, the intended window or display is selected and managed-device policy permits it. HTTPS is required for modern media capture.
03
Follow the media path
If preview works but remote users see nothing, inspect browser diagnostics and server logs at the timestamp. Validate firewall, NAT and TURN. Compare a different external network. A widespread issue after a change suggests media-service, proxy or configuration regression rather than hundreds of camera failures.
04
Check policy and load
Webcam limits and instructor guidance protect both capacity and classroom usability. Observe CPU and outbound bandwidth during the failure. Reproduce at low and representative load, then verify that the repair survives reconnect, multiple cameras, screen-share handoff and a second room.
Evidence base
Sources and further reading
We prefer project documentation and first-party product guidance. Community links are included where they reveal recurring operational questions rather than establish product guarantees.
Practical answers
Questions teams ask
Why does my camera preview work but nobody sees it?+
Local capture is working, but publication or remote subscription may be failing. Test with another viewer and inspect WebRTC/server evidence.
Does screen sharing require a browser extension?+
Current supported browsers generally provide native screen-capture APIs. Exact support and managed-device policy vary, so check the browser and BigBlueButton version.
Can too many webcams cause failures?+
They increase server and network demand. Enforce a tested classroom policy and monitor saturation rather than relying on an arbitrary universal limit.
Continue the research
Related guides and infrastructure
Diagnose BigBlueButton audio and WebRTC failures
Diagnose BigBlueButton microphone, listen-only, ICE, firewall, NAT and TURN failures with a repeatable evidence-first workflow.
Read next → Planning & architectureHow to size a BigBlueButton server
Size BigBlueButton servers using concurrent meetings, participants, webcams, screen sharing, recordings and measured headroom.
Read next → Technical guideBigBlueButton firewall ports and network prerequisites
Understand BigBlueButton firewall requirements including TCP 80/443, UDP 16384–32768, HTTPS, WebRTC and TURN planning.
Read next →