Jitsi Camera or Microphone Not Working: Fixes for Every Browser

Jitsi camera or microphone not working

Updated September 26, 2026Tested on Jitsi Meet stable-11031By the Jitsi Help engineering team

Short answer

Browsers only allow camera and microphone access on HTTPS pages with a trusted certificate. On a self-hosted server, make sure the site is served over valid HTTPS and set ENABLE_HTTP_REDIRECT=1 so http:// never loads. For individual users, check the browser's site permission, close other apps using the camera, and allow camera and microphone in the iframe if Jitsi is embedded.

Camera and microphone problems split into two groups: the whole server is misconfigured (everyone is affected) or one person’s device or browser is (one person is affected).

Everyone is affected: check HTTPS

Browsers expose the camera and microphone only in a secure context: an HTTPS page with a certificate the browser trusts. If your Jitsi opens over http://, or over https:// with a self-signed certificate, it cannot use devices properly.

On Docker Jitsi:

ENABLE_HTTP_REDIRECT=1
ENABLE_LETSENCRYPT=1
LETSENCRYPT_DOMAIN=meet.example.com

ENABLE_HTTP_REDIRECT=1 matters: without it, someone typing the address without https:// lands on a page that loads but shows an unsupported-browser message. We enable it on every server we deploy for exactly this reason. See Let’s Encrypt SSL for Jitsi.

One person is affected

Work through these in order:

Site permission. Click the padlock or camera icon in the address bar and set Camera and Microphone to Allow, then reload.
Another app holds the camera. Close Zoom, Teams, OBS or another browser tab using it. On Windows, only one app can use many webcams at a time.
Operating system privacy settings. On macOS: System Settings, Privacy and Security, Camera and Microphone, enable the browser. On Windows: Settings, Privacy, Camera and Microphone, allow desktop apps.
Wrong device selected. In the meeting, open the arrow next to the mic or camera button and pick the right device.
Browser. Try a current Chrome, Edge or Firefox. Disable extensions that block media or scripts.

Embedded Jitsi (iframe or IFrame API)

The parent page must be HTTPS, and the iframe must be granted access:

<iframe src="https://meet.example.com/room"
        allow="camera; microphone; display-capture; autoplay; clipboard-write; fullscreen"></iframe>

The IFrame API adds these permissions for you; a hand-written iframe does not.

Mobile

In mobile browsers the same rules apply: HTTPS and site permissions. In the Jitsi Meet app, check the app’s camera and microphone permission in the phone settings.

Still stuck?

Ask an engineer and include the browser, the device and whether everyone or one person is affected.

Frequently asked questions

Why does Jitsi say my browser is not supported?

Often because the page was opened over plain HTTP or with an untrusted certificate, which blocks camera and microphone APIs. Open the https:// address with a valid certificate. Very old browsers are also unsupported; use a current Chrome, Edge, Firefox or Safari.

Why does the camera work in Chrome but not in my embedded app?

An iframe needs explicit permission. Add allow="camera; microphone; display-capture; autoplay; clipboard-write" to the iframe tag, and serve the parent page over HTTPS too.

Stuck, or would rather not do this by hand?

Deploy it in one click

A private Jitsi server in your own AWS account with SSL, your domain and optional recording, transcription and JWT. Free 15 minute trial.

Start free trial

Talk to a Jitsi engineer

Setup, fixes, branding, recording, scaling. Tell us what is happening and we reply with a plan and a quote.

Get expert help