mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
[GH-ISSUE #20531] issue: STT Whisper Local giving permission error in WebUI after upgrade to 0.7.0 and 0.7.1 #57877
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SenorLAN on GitHub (Jan 9, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20531
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.7.1 (appeared on 0.7.0)
Ollama Version (if applicable)
No response
Operating System
Ubuntu 24.03
Browser (if applicable)
Firefox 146.0.1 (64-bit), Safari on ios 26.1
Confirmation
README.md.Expected Behavior
In a new or existing chat, a user can click on either the microphone icon or the Voice mode icon and speak to chat session and have Local Whisper use STT to convert this and either paste into the chat or continue a voice mode conversation.
Actual Behavior
After speaking (and visual feedback is shown that audio is being captured), an error toast appears that says "You do not have permission to access this resource. Please contact your administrator for assistance."
Steps to Reproduce
Logs & Screenshots
docker.log
browser.log
Additional Information
No response
@owui-terminator[bot] commented on GitHub (Jan 9, 2026):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#20125 issue: STT local whisper failure
by ALIENvsROBOT • Dec 22, 2025 •
bug#20173 issue: STT local whisper issue (Please don't turn this to discussion)
by ALIENvsROBOT • Dec 25, 2025 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@Classic298 commented on GitHub (Jan 9, 2026):
A lot changed between 0.6.5 and 0.7 especially on the audio front, you will most likely need to re-configure some stuff. Did you check out the new guides on the docs and what is your precise setup? Feel free to also ask the bot in the #questions channel on discord, it can help with audio setups. It has access to the latest docs.
@SenorLAN commented on GitHub (Jan 9, 2026):
I checked my setup and "Whisper (Local)" is the default.
I changed to OpenAI and it worked, I then changed back and it failed to work again on Whisper (Local)
I confirmed the STT Model of base, and also tried to change to tiny. Both have the same result. I do not know of other troubleshooting steps.
This functioned properly on 0.6.43 (as I have been upgrading with each and every release since I originally installed). When upgrading to 0.7.0 this occurred.
I see that 0.6.43 has updates to STT default content type handling, but I had no issues with that version running.
I see no release notes in 0.7.0 for Speech to Text or Whisper (except as an example for how to quick search admin menu topics).
@Classic298 am I missing something. I am open to try other steps to assist in troubleshooting.
To be clear this worked on the prior production release of 0.6.43 release 2025-12-22 on two different installations that I have.
@mclarkson commented on GitHub (Jan 9, 2026):
Same here. It was working fine before, but after upgrading to 0.7.1, from 0.6.43, I get the same red box as @SenorLAN. I'm not on Discord to check there but I've gone through all the docs with AI, and it didn't have any good advice.
I'm running OWUI under Podman on Fedora Server 43, and have been using it as the initial Admin user.
I get this forbidden log entry:
2026-01-09 23:40:30.603 | INFO | uvicorn.protocols.http.httptools_impl:send:483 - 192.168.1.xx:0 - "POST /api/v1/audio/transcriptions HTTP/1.1" 403
@SenorLAN commented on GitHub (Jan 9, 2026):
FWIW, this is my compose file. The issue occurs logged in as either an admin or standard user.
I have also tried reverting my "BYPASS_ADMIN_ACCESS_CONTROL" to True and the problem remained
@Classic298 commented on GitHub (Jan 9, 2026):
BYPASS_ADMIN_ACCESS_CONTROL is not related to audio - has nothing to do with this.
@SenorLAN
your most likely issue here is this CC @mclarkson
🔑 Image Generation, Web Search, and Audio (TTS/STT) API endpoints now enforce permission checks on the backend, closing a security gap where disabled features could previously be accessed via direct API calls. https://github.com/open-webui/open-webui/pull/20471
@Classic298 commented on GitHub (Jan 9, 2026):
can you check if you enabled all permissions as needed?
@mclarkson commented on GitHub (Jan 9, 2026):
I'm running as the Admin user, but still I enabled every permission in everything I could find. I also set up a normal user to give that all the permissions but it was the same result.
There was one place in the manual where it says to go to the Permissions section within the Workspace but I couldn't find that screen anywhere. I asked AI, pointing it at OWUI docs, and it just repeated the same thing back to me. I'm fairly new to OWUI so I could be missing something obvious.
@SenorLAN commented on GitHub (Jan 9, 2026):
Just to confirm, we are speaking of these permissions correct? This is the default set and the group that my admin is a member of.
@Classic298 commented on GitHub (Jan 9, 2026):
Please send me the link
Enable permissions in admin panel > Users > groups > default permissions
there, enable all audio related permissions
Calls, transcription, voice and what they are called
@Classic298 commented on GitHub (Jan 10, 2026):
@SenorLAN
did you configure a TTS engine?
@Classic298 commented on GitHub (Jan 10, 2026):
@SenorLAN commented on GitHub (Jan 10, 2026):
@Classic298 Yes it was configured before and remained through the upgrade as Whisper (local) with a model of "base". I also tried "tiny" with the same result.
This is what you are speaking of correct? If I change to OpenAI it works fine. But when I switch back to Whisper (local) the issue returns.
@Classic298 commented on GitHub (Jan 10, 2026):
any logs? on debug level?
@Classic298 commented on GitHub (Jan 10, 2026):
ok found the issue
@mclarkson commented on GitHub (Jan 10, 2026):
@Classic298 https://docs.openwebui.com/features/rbac/permissions - The top of that page:
"The Permissions section of the Workspace within Open WebUI allows administrators to configure access controls..."
@Classic298 commented on GitHub (Jan 10, 2026):
STT_ENGINE = "" means local whisper
the new backend checks unfortunately check for = "" on STT_ENGINE
PR that was merged assumed that "" means not configured
but "" is used for the default, which is local whisper
that is why it doesn't work
temporary fix for you: modify the audio.py in the backend and comment out this check
then it should work
@Classic298 commented on GitHub (Jan 10, 2026):
@mclarkson thanks will address that.
@SenorLAN commented on GitHub (Jan 10, 2026):
BTW - thank you for being a part of building such a great product @Classic298 !
@Classic298 commented on GitHub (Jan 10, 2026):
@silentoplayz please throw out a PR for this
@mclarkson commented on GitHub (Jan 10, 2026):
Works for me! Thank you! 🎊
@Classic298 commented on GitHub (Jan 10, 2026):
Since this should be easily fixable even in containerized environments (connect into docker, modify file - or run a script on startup that replaces the audio.py within the docker before open-webui starts up, or a one-liner that removes or comments out the offending lines after container startup), I don't think a new release with a fix for specifically this is highly urgent.
PR will be incoming soon anyways, and this will surely be fixed in the next version.
Keeping this issue open until it is fixed in dev (pr merged).
Thanks everyone
@Classic298 commented on GitHub (Jan 10, 2026):
@mclarkson docs will be updated in 2min with corrections on that page.
@Classic298 commented on GitHub (Jan 10, 2026):
https://github.com/open-webui/open-webui/pull/20534
@silentoplayz commented on GitHub (Jan 10, 2026):
My apologies for the confusion caused by this bug! Testing is requested with #20534 to confirm it resolves the issue(s) you all have reported here. Thank you all for the detailed bug report and comments that helped to identify and fix this!
@mclarkson commented on GitHub (Jan 10, 2026):
That's much better 👍
I'm seriously impressed with the quick fixes, thanks so much!
@Classic298 commented on GitHub (Jan 10, 2026):
Pr is merged thanks everyone
@ALIENvsROBOT commented on GitHub (Jan 10, 2026):
when can we expect the next release ??
@Classic298 commented on GitHub (Jan 10, 2026):
@ALIENvsROBOT no timeline can be given.
If this is an issue for you apply the patch posted above manually as a temporary fix.
This is not an urgent issue as if it affects you drastically, you can easily fix it for now.
@ALIENvsROBOT commented on GitHub (Jan 10, 2026):
sure thanks so far I fixed it by commenting out those lines
@quantumalchemy commented on GitHub (Jan 21, 2026):
Recurring again on latest 0.7.2 -> You need to authenticate by providing a session cookie or Authorization header (Bearer token). -- browser: chrome, ff even if default
@Classic298 commented on GitHub (Jan 21, 2026):
@quantumalchemy
that just means your session expired. refresh or log out and in again
@quantumalchemy commented on GitHub (Jan 21, 2026):
But only does this when using audio mic..stt tts. I stay logged in ok
But when doing voice
Mic stt transcribed ok.. but when submitted I get this error again using any browser.. also mobile chrome
I have cleared cache.. cleared data cache.. reinstalled.. thought it was ssl but running on https any insight?
@Classic298 commented on GitHub (Jan 21, 2026):
steps to repro? For me voice and transcription works on all devices on 0.7.2
@quantumalchemy commented on GitHub (Jan 22, 2026):
Close it.. it was the LLM provider endpoint ok for text / but forgets auth if audio used .. strange but tested with anther openai compat provider and Ok