Not able to set microphone perms- no drop down option

Browser Support
, , ,
1

Description of the issue:
Unable to change Microphone permission settings for individual, local site. When looking at the permissions for the site specifically, several options cant be changed such as Camera perm or Microphone permissions but other options are changeable (Solana, Images, Sound etc)

Steps to Reproduce (add as many as necessary): 1. 2. 3.
When using any remote site with a FQD address, I will get a pop up asking to allow microphone access (like google hangouts). Click ok and that works as intended.
When connecting to a local ip or non FQD, no popup asking for access. It does however give the error that the browser does not have access to the microphone, please change settings in browser.
Actual Result (gifs and screenshots are welcome!):
Alert stating no access:

image
image1636×977 98.9 KB

Site specific permissions: options in blue square are immutable, cannot be change from this screen. Options above and below are changeable. Reset to default with same problem. Created a new profile, disabled all extensions, turned off safe browsing, turned off shields for this site, allowed cookies and fingerprinting. Relaunched browser and options are still locked out. Tried a private window and tried using the ip instead of a hostname, still unable to change mic options. Reset permissions from that screen, same issue.

image
image1312×962 137 KB

When trying the local IP without the port it does allow me to change microphone permissions

image
image714×634 19.7 KB

When adding the port, the site specific options are immutable again and stuck at blocked.

image
image731×723 24.5 KB

Expected result:
Should be able to change microphone access for a local web page but the options are not changeable, no drop down.

Reproduces how often:
Every time I visit the local site. FQD remote sites, even with a port added work as intended, options are changeable.

Operating System and Brave Version(See the About Brave page in the main menu):
Brave is up to date
Brave 1.79.119 (Official Build) (64-bit)
Chromium: 137.0.7151.68

Edition Windows 10 Pro
Version 2009
Installed on ‎8/‎16/‎2023
OS Build 19045.5965

Additional Information:
Anythingllm (10.10.10.131:3001) is a ‘web interface’ for communicating with AI LLM’s if that makes a difference.

Love Brave, this is very strange but perhaps I’m missing something easy? Also tried Brave (latest) 1.79.119 on Ubuntu 22.04 with the exact same issues.
Thanks

2

I think those are security restrictions enforced by Chromium on HTTP sites.

Does it work if you try with localhost / 127.0.0.1?

2 Likes
3

If that doesn’t work, you can try adding your hostname to brave://flags/#unsafely-treat-insecure-origin-as-secure as a work-around.

1 Like
4

localhost with no port, the option for perms was changeable. localhost:3001 the option for mic perms was grayed out/locked.

1 Like
5

The flag fixed the problem. Thank you for the flag info, much appreciated.
Considered closed

2 Likes
6

As you are using Brave, it automatically blocks any attempt by other sites to access microphone, camera and some of the permissions. There is nothing you can do about it. But still there are some workarounds like:

  1. Try with localhost / 127.0.0.1
    [or]
  2. Add your hostname to brave://flags/#unsafely-treat-insecure-origin-as-secure

You can get help from Leo AI, ChatGPT, Gemini for exact steps to follow.

7

Thanks for the info Bryan, I’m still not understanding the entire issue. This is unfortunate as most people treat LAN as trusted, the OS sees the interface as private and trusted but anyway-

After returning access to the defaults:
Http://10.10.10.130 will ask to use the microphone via popup. Going in to site specific access, all devices you can change the drop down to allow ask or block.

Reset defaults access again, relaunch browser and try http://10.10.10.130:3001. No prompt to allow mic access, site specific access for mic access is not changeable.

Simply adding a port number to the url changes the ability to adjust permissions. If it was a host origin or non local address problem then http://10.10.10.130 would not work?
I’ll make it work and you can consider this closed but it looks like adding a non standard port to the url causes my issue
Cheers