Skip to main content
Crossed-out camera or microphone icons in a Real-Time Video call mean the site or the operating system blocked the devices, or a stored permission or extension is denying access. The origin that must be allowed is meet.gcore.com. Allow the site in the browser first. If the icons stay crossed out, reset that site permission, test extensions, allow the browser in the OS, then confirm that the browser version is supported. If the devices work in the browser but other participants do not receive media, the network is blocking WebRTC. An enabled icon with silence in the room is a different problem — the OS is sending the wrong input device, and that check is in the Windows tab.

​
Check browser permissions

The address bar on the Real-Time Video page shows whether meet.gcore.com may use the camera and microphone. Open the tab for the browser in use.
The padlock in the Chrome address bar shows site permissions for meet.gcore.com. Turn Camera and Microphone on if they are off, then reload the page.
Chrome site permissions for meet.gcore.com with Camera and Microphone toggles
If the padlock is missing or the toggles stay off, open Chrome Settings, select Privacy and security, then open Site settings.
Chrome Settings showing Privacy and security and Site settings
Open Camera and Microphone. Confirm that sites can ask to use the devices and that meet.gcore.com is not blocked.
Chrome Site settings list with Camera and Microphone
On Android Chrome, tap the lock icon on the Real-Time Video page and allow Camera and Microphone.

​
Reset site permissions

If the address-bar toggles were changed but the icons stay crossed out, the browser is still applying a stored permission for meet.gcore.com. Reset that origin only, then reload the page.
In the padlock menu, click Reset permissions, then reload the page. Chrome asks for camera and microphone access again.

​
Check extensions

A third-party extension can deny camera or microphone access on meet.gcore.com. Open the Real-Time Video page in a private or incognito window, where most extensions are off. A private window also uses a separate permission store, so a working call there is not proof that an extension is the cause. If the devices work in the private window, return to the regular window, disable extensions that manage camera, microphone, ads, or privacy one at a time, and reload the call. The extension that restores the devices is the one to leave off during Real-Time Video sessions.

​
Check operating-system permissions

The operating system can block the browser even when the site permission is on. Open the tab for the OS in use.
Windows 11 can deny camera or microphone access to the browser. Open Settings → Privacy & security, then select Camera or Microphone. Turn camera access or Microphone access on, then allow the browser in the app list.
Windows 11 Microphone access and per-app microphone permissions
If the icon is already enabled but the room hears nothing, the default input is wrong. Open Settings → System → Sound. Under Input, select the device that should capture the call.
Windows 11 Sound settings with Input devices

​
Confirm the browser version

If permissions are correct and the icons are still crossed out, confirm that the browser meets the minimum supported version. Update from the vendor page in the same row if the installed version is lower.

​
Check the network

This step applies only after the camera and microphone are available in the browser — the local preview works, the icons are not crossed out, and the OS permission is on. Corporate networks and strict firewalls can still block WebRTC media, so other participants do not receive audio or video. Switching browsers does not bypass a network that drops those connections. Join the call from another network, or ask the network administrator to allow WebRTC traffic for meet.gcore.com.