Skip to main content

Browser Extension isn't connected with MuteDeck

With every browser extension, you're able to check the extension status by clicking the MuteDeck icon in your extensions list. It'll show this popup:

browser extension popup

If the extension isn't connected to the MuteDeck application, it'll say that at the top. If possible, that message will also indicate a fix. If it indicated that it's not connected to MuteDeck without a reason or possible fix, please check the extensions logs for an indication.

  • Chrome: Settings -> Extensions -> Details on MuteDeck -> Inspect views (service worker)
  • Firefox: Settings -> Add-ons and themes -> Click on MuteDeck -> Click on the gear icon -> Debug add-ons -> Click the Inspect button on MuteDeck

This will open a new window where the extension log messages are displayed. The MuteDeck extension is rather verbose, and it's likely that that reason why it's not able to connect is being displayed there.

If the Extension is not Connected​

Click the MuteDeck extension icon in your browser. If it shows "Not connected":

  1. Ensure MuteDeck is running on your computer
  2. Check for firewall blocking localhost connections
  3. Try different browser to isolate the issue
  4. Check extension logs:
    • Chrome: chrome://extensions/ → Details → Inspect views
    • Firefox: about:debugging → This Firefox → Inspect

If the Popup is Empty​

If the popup is empty with no connection status, no values for the Call status: and other status fields, it's likely that the extension is not allowed to run on the current page. If you've just installed the extension, close the tab and open a new one to ensure the extension is loaded.

This can happen if the Chrome security settings are blocking the extension via the runtime_blocked_hosts setting. Sometimes, companies have policies in place that block extensions from running on certain pages, such as Google Meet.

For more information, see the Chrome Enterprise Help.

If the extension popup mentions an SSL certificate error, it means that the browser is blocking the connection to the MuteDeck application. This can happen if the MuteDeck extension is running inside Firefox or Firefox-based browsers - as they require SSL connections to external apps like MuteDeck. To fix this, you need to accept the SSL certificate for the MuteDeck application. You can do this by clicking the link in the popup, or by visiting https://localhost:3493/ in your browser and accepting the SSL certificate. After that, the extension should be able to connect to MuteDeck.

accept ssl certificate

A new tab opens with a warning about the SSL certificate. Click "Advanced" and then "Accept the Risk and Continue". Reload any meeting tabs you have open, and the extension should now be able to connect to MuteDeck.

Other Things to Check​

Extension Permissions​

The extension needs these permissions:

  • Access browsing history: For "bring to front" feature (not actually reading history)
  • Access data for websites: To detect and control meeting interfaces

Brave Browser Specific​

  1. Visit http://localhost:3491/
  2. Disable Brave Shields for localhost
  3. Also disable Shields for meet.google.com or your meeting platform