[PR #172] [MERGED] docs: mention ways to bypass HTTPS restrictions on chromium + untested ways on firefox #302

New issue

Closed

opened 2026-10-18 14:10:57 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 14:10:57 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/docs/pull/172
Author: @thiswillbeyourgithub
Created: 8/7/2024
Status: ✅ Merged
Merged: 8/7/2024
Merged by: @justinh-rahb

Base: main ← Head: docs_whitelist_ssl_https

📝 Commits (1)

d6a1cf2 docs: mention ways to bypass HTTPS restrictions on chromium + untested ways on firefox

📊 Changes

2 files changed (+8 additions, -1 deletions)

View changed files

📝 docs/features.mdx (+1 -1)
📝 docs/troubleshooting/index.mdx (+7 -0)

📄 Description

As recommended here by @justinh-rahb here's a documentation PR to mention how to whitelist a URL on chromium based browsers to enable microphone support on non HTTPS connections.

I mentioned firefox too but my particular firefox are somewhat modified so I'd appreciate if someone could give it a try.

Notes:

A stackoverflow post of 2021 mentions that there is no way on firefox to whitelist as easily. It links to a bugzilla ticket that is still opened.
In my specific case on firefox when manually allowing the microphone permission via the padlock and setting media.devices.insecure.enabled to True, clicking on "Record voice" gets me the following error message: Permission denied when accessing microphone: NotAllowedError: The request is not allowed by the user agent or the platform in the current context.. Clicking on "Call" gets me Permission denied when accessing media devices.
This PR is relevant to at least #1148, #3765 and #4020

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/docs/pull/172 **Author:** [@thiswillbeyourgithub](https://github.com/thiswillbeyourgithub) **Created:** 8/7/2024 **Status:** ✅ Merged **Merged:** 8/7/2024 **Merged by:** [@justinh-rahb](https://github.com/justinh-rahb) **Base:** `main` ← **Head:** `docs_whitelist_ssl_https` --- ### 📝 Commits (1) - [`d6a1cf2`](https://github.com/open-webui/docs/commit/d6a1cf29b72877277787343cb34388865e8fdc81) docs: mention ways to bypass HTTPS restrictions on chromium + untested ways on firefox ### 📊 Changes **2 files changed** (+8 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/features.mdx` (+1 -1) 📝 `docs/troubleshooting/index.mdx` (+7 -0) </details> ### 📄 Description As recommended [here](https://github.com/open-webui/open-webui/discussions/4352#discussioncomment-10254871) by @justinh-rahb here's a documentation PR to mention how to whitelist a URL on chromium based browsers to enable microphone support on non HTTPS connections. I mentioned firefox too but my particular firefox are somewhat modified so I'd appreciate if someone could give it a try. ## Notes: - A [stackoverflow post](https://stackoverflow.com/questions/66678123/is-there-an-equivalent-of-insecure-origins-treated-as-secure-of-chrome-flag-in) of 2021 mentions that there is no way on firefox to whitelist as easily. It links to [a bugzilla](https://bugzilla.mozilla.org/show_bug.cgi?id=1410365) ticket that is still opened. - In my specific case on firefox when manually allowing the microphone permission via the padlock and setting `media.devices.insecure.enabled` to `True`, clicking on "Record voice" gets me the following error message: `Permission denied when accessing microphone: NotAllowedError: The request is not allowed by the user agent or the platform in the current context.`. Clicking on "Call" gets me `Permission denied when accessing media devices`. - This PR is relevant to at least [#1148](https://github.com/open-webui/open-webui/discussions/1148), [#3765](https://github.com/open-webui/open-webui/discussions/3765) and [#4020](https://github.com/open-webui/open-webui/discussions/4020) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-18 14:10:57 +00:00