wbroom

Browser meeting mic not working: permission, device, tab mute

Fix permission, device, and tab mute first. If media never starts after that, debug the network path.

They say the room is silent and your level meter never moves. A browser meeting with no sound is usually permission or device — not the room ID.

For browser meeting mic not working, split the fault: did this origin get the mic, did the OS pick the right input, and can this tab call getUserMedia?

Site microphone permission OS input device Busy device and embedded preview

Four usual causes

01

Permission blocked or asked once

After Block, Chrome / Edge / Safari / Firefox rarely prompt again. Set the site to Allow in the address-bar controls and reload the room.

02

The OS input is not the mic you are using

Built-in mics, Bluetooth headsets, and dock audio all appear as inputs. Match the OS list to the device the browser lists for this site.

03

Another tab or call holds the device

A second meeting or a recorder tab can keep exclusive access on some systems. Close extras and keep one capturing tab.

04

The page cannot reach the microphone

Non-HTTPS (and not localhost), IDE previews, and some in-app browsers fail outright. Use a system browser. Do not join from an editor preview.

Four steps in order

  1. 1

    Open the room in a system browser

    Create or join from the wbroom homepage. Chrome, Edge, Safari, or Firefox. Steps: create and join a room.

  2. 2

    Allow this site to use the microphone

    Choose Allow when asked. If you already blocked it, flip the site setting and reload. Short notes: voice and camera tips.

  3. 3

    Confirm the device and wear headphones

    Pick the input you are speaking into. Headphones reduce echo. Unmute the hardware key and the browser tab mute.

  4. 4

    If nobody has media, debug the path

    Permission and device look fine but the mesh is silent: firewall, VPN, browser version — WebRTC connection troubleshooting. On phones, stay in the system browser: mobile browser.

1 origin
Each site origin needs its own mic grant
0 accounts
A no-login room cannot restore permission via signup
8 max
People per room — get your own audio working first

Which layer first

Symptom Check first On wbroom
No permission prompt HTTPS / localhost, or an embedded preview Open the homepage room in a system browser
Prompt appeared, you blocked it Address-bar site settings Allow, then reload the same room ID
You hear them; they do not hear you Input device, hardware mute, exclusive capture Keep a single capturing tab
Nobody hears anybody VPN, corporate network, stale browser Follow the WebRTC help page or recreate the room

Product limits on the features page: voice first, camera and screen on demand. The room ID is the credential — share it only with this session.

Let the browser accept this microphone before you blame the room. The network layer only matters after permission succeeds.

# Local checks before you recreate the room
# 1) System browser (not an IDE preview)
# 2) Address bar: microphone = Allow
# 3) One capturing tab only
HTTPS or localhost
Outside a secure context, pages usually cannot open the mic. Embedded previews are often neither.
Cameras can stay off
Rooms cap cameras. Get voice first; presenters add video. Capacity is eight people.

Still deciding?

Do I need an account to use the microphone?

No. wbroom uses a room ID. The grant is to this site origin in the browser, not to a login.

Are Safari and Chrome settings the same?

The menus differ; the model does not: allow or block per site. Change the microphone control for this origin, then reload the room.

No sound on a phone browser?

Use system Safari or Chrome, not an in-app WebView. Allow the browser to use the mic in OS settings, and avoid a second live call at the same time.

Start a meeting