[GH-ISSUE #20531] issue: STT Whisper Local giving permission error in WebUI after upgrade to 0.7.0 and 0.7.1 #57877

Closed
opened 2026-05-05 21:48:37 -05:00 by GiteaMirror · 35 comments
Owner

Originally created by @SenorLAN on GitHub (Jan 9, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20531

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

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

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

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

  1. Start with clean Ubuntu 24.04.3 installation
  2. Add docker official key and sources.
  3. Install docker
  4. create directory for openwebui
  5. Create compose.yaml file and paste template from GitHub
  6. (Somehow pull in version prior to 0.7.0, currently have two installs that were originally 0.6.5 and another was 0.6.22)
  7. Configure to work with Whisper (Local) for STT with STT Model of base
  8. Use Cloudflare for DNS to front end and provide an SSL web connection (proxy on)
  9. Confirm you can chat in Voice mode and also that you can record with the microphone.
  10. Upgrade to 0.7.0 with docker compose pull, then docker compose down, then docker compose up --force-recreate
  11. Log in and hard refresh the web page to ensure cache is clear.
  12. Create a new chat and attempt to use the microphone or Voice chat
Image

Logs & Screenshots

docker.log
browser.log

Image

Additional Information

No response

Originally created by @SenorLAN on GitHub (Jan 9, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20531 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### 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 - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### 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 1. Start with clean Ubuntu 24.04.3 installation 2. Add docker official key and sources. 3. Install docker 4. create directory for openwebui 5. Create compose.yaml file and paste template from GitHub 6. (Somehow pull in version prior to 0.7.0, currently have two installs that were originally 0.6.5 and another was 0.6.22) 7. Configure to work with Whisper (Local) for STT with STT Model of base 8. Use Cloudflare for DNS to front end and provide an SSL web connection (proxy on) 9. Confirm you can chat in Voice mode and also that you can record with the microphone. 10. Upgrade to 0.7.0 with docker compose pull, then docker compose down, then docker compose up --force-recreate 11. Log in and hard refresh the web page to ensure cache is clear. 12. Create a new chat and attempt to use the microphone or Voice chat <img width="1041" height="250" alt="Image" src="https://github.com/user-attachments/assets/5b98a81d-5756-4d48-9db3-562c306c61fa" /> ### Logs & Screenshots [docker.log](https://github.com/user-attachments/files/24537081/docker.log) [browser.log](https://github.com/user-attachments/files/24537082/browser.log) <img width="476" height="490" alt="Image" src="https://github.com/user-attachments/assets/2de6475f-4244-4987-9fdd-22e33cead01d" /> ### Additional Information _No response_
GiteaMirror added the confirmedbugconfirmed issue labels 2026-05-05 21:48:38 -05:00
Author
Owner

@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:

  1. #20125 issue: STT local whisper failure
    by ALIENvsROBOT • Dec 22, 2025 • bug

  2. #20173 issue: STT local whisper issue (Please don't turn this to discussion)
    by ALIENvsROBOT • Dec 25, 2025 • bug


💡 Tips:

  • If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
  • If you found a solution in any of these issues, please share it here to help others

This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.

<!-- gh-comment-id:3730893554 --> @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: 1. [#20125](https://github.com/open-webui/open-webui/issues/20125) **issue: STT local whisper failure** *by ALIENvsROBOT • Dec 22, 2025 • `bug`* 2. [#20173](https://github.com/open-webui/open-webui/issues/20173) **issue: STT local whisper issue (Please don't turn this to discussion)** *by ALIENvsROBOT • Dec 25, 2025 • `bug`* --- 💡 **Tips:** - If this is a duplicate, please consider closing this issue and adding any additional details to the existing one - If you found a solution in any of these issues, please share it here to help others *This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
Author
Owner

@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.

<!-- gh-comment-id:3730908273 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:3730952780 --> @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.
Author
Owner

@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

<!-- gh-comment-id:3730966506 --> @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
Author
Owner

@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

services:
  open-webui:
     image: ghcr.io/open-webui/open-webui:main
     restart: always
     ports:
       - "0080:8080"
     extra_hosts:
       - "host.docker.internal:host-gateway"
     volumes:
       - open-webui:/app/backend/data
     environment:
       - OPENAI_API_KEY=sk-(redacted)
       - TTS_REQ_TIMEOUT=600
       - BYPASS_ADMIN_ACCESS_CONTROL=False

volumes:
     open-webui:
       external: true
<!-- gh-comment-id:3730971491 --> @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 ``` services: open-webui: image: ghcr.io/open-webui/open-webui:main restart: always ports: - "0080:8080" extra_hosts: - "host.docker.internal:host-gateway" volumes: - open-webui:/app/backend/data environment: - OPENAI_API_KEY=sk-(redacted) - TTS_REQ_TIMEOUT=600 - BYPASS_ADMIN_ACCESS_CONTROL=False volumes: open-webui: external: true ```
Author
Owner

@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

<!-- gh-comment-id:3731004691 --> @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
Author
Owner

@Classic298 commented on GitHub (Jan 9, 2026):

can you check if you enabled all permissions as needed?

<!-- gh-comment-id:3731005474 --> @Classic298 commented on GitHub (Jan 9, 2026): can you check if you enabled all permissions as needed?
Author
Owner

@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.

<!-- gh-comment-id:3731021423 --> @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.
Author
Owner

@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.

Image Image
<!-- gh-comment-id:3731025763 --> @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. <img width="886" height="555" alt="Image" src="https://github.com/user-attachments/assets/cfffc2a7-0407-47ee-b6f1-edc251936939" /> <img width="885" height="561" alt="Image" src="https://github.com/user-attachments/assets/1d4bb6f7-e36d-444c-bcc4-f1e362cfd5b2" />
Author
Owner

@Classic298 commented on GitHub (Jan 9, 2026):

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.

Please send me the link

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.

Enable permissions in admin panel > Users > groups > default permissions

there, enable all audio related permissions

Calls, transcription, voice and what they are called

<!-- gh-comment-id:3731028388 --> @Classic298 commented on GitHub (Jan 9, 2026): > 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. Please send me the link > 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. Enable permissions in admin panel > Users > groups > default permissions there, enable all audio related permissions Calls, transcription, voice and what they are called
Author
Owner

@Classic298 commented on GitHub (Jan 10, 2026):

@SenorLAN

did you configure a TTS engine?

<!-- gh-comment-id:3731058194 --> @Classic298 commented on GitHub (Jan 10, 2026): @SenorLAN did you configure a TTS engine?
Author
Owner

@Classic298 commented on GitHub (Jan 10, 2026):

Image
<!-- gh-comment-id:3731058542 --> @Classic298 commented on GitHub (Jan 10, 2026): <img width="558" height="172" alt="Image" src="https://github.com/user-attachments/assets/0d146a05-8c90-42ec-ad10-8c1d86a96d59" />
Author
Owner

@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.

Image
<!-- gh-comment-id:3731076693 --> @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. <img width="1160" height="240" alt="Image" src="https://github.com/user-attachments/assets/daa3f479-5307-444a-a85a-3815bb85a1c2" />
Author
Owner

@Classic298 commented on GitHub (Jan 10, 2026):

any logs? on debug level?

<!-- gh-comment-id:3731080658 --> @Classic298 commented on GitHub (Jan 10, 2026): any logs? on debug level?
Author
Owner

@Classic298 commented on GitHub (Jan 10, 2026):

ok found the issue

<!-- gh-comment-id:3731093073 --> @Classic298 commented on GitHub (Jan 10, 2026): ok found the issue
Author
Owner

@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..."

<!-- gh-comment-id:3731094852 --> @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..."
Author
Owner

@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

Image
<!-- gh-comment-id:3731096447 --> @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 <img width="543" height="276" alt="Image" src="https://github.com/user-attachments/assets/aef8a052-2d6d-442b-b534-69bcec79a2b1" />
Author
Owner

@Classic298 commented on GitHub (Jan 10, 2026):

@mclarkson thanks will address that.

<!-- gh-comment-id:3731097832 --> @Classic298 commented on GitHub (Jan 10, 2026): @mclarkson thanks will address that.
Author
Owner

@SenorLAN commented on GitHub (Jan 10, 2026):

BTW - thank you for being a part of building such a great product @Classic298 !

<!-- gh-comment-id:3731097882 --> @SenorLAN commented on GitHub (Jan 10, 2026): BTW - thank you for being a part of building such a great product @Classic298 !
Author
Owner

@Classic298 commented on GitHub (Jan 10, 2026):

@silentoplayz please throw out a PR for this

<!-- gh-comment-id:3731098090 --> @Classic298 commented on GitHub (Jan 10, 2026): @silentoplayz please throw out a PR for this
Author
Owner

@mclarkson commented on GitHub (Jan 10, 2026):

Works for me! Thank you! 🎊

Image
<!-- gh-comment-id:3731113025 --> @mclarkson commented on GitHub (Jan 10, 2026): Works for me! Thank you! 🎊 <img width="411" height="241" alt="Image" src="https://github.com/user-attachments/assets/b7a0ebd4-b96b-4a23-9ba6-857efc7fa4f5" />
Author
Owner

@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

<!-- gh-comment-id:3731127363 --> @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
Author
Owner

@Classic298 commented on GitHub (Jan 10, 2026):

@mclarkson docs will be updated in 2min with corrections on that page.

<!-- gh-comment-id:3731133766 --> @Classic298 commented on GitHub (Jan 10, 2026): @mclarkson docs will be updated in 2min with corrections on that page.
Author
Owner

@Classic298 commented on GitHub (Jan 10, 2026):

https://github.com/open-webui/open-webui/pull/20534

<!-- gh-comment-id:3731147580 --> @Classic298 commented on GitHub (Jan 10, 2026): https://github.com/open-webui/open-webui/pull/20534
Author
Owner

@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!

<!-- gh-comment-id:3731153081 --> @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!
Author
Owner

@mclarkson commented on GitHub (Jan 10, 2026):

@mclarkson docs will be updated in 2min with corrections on that page.

That's much better 👍

I'm seriously impressed with the quick fixes, thanks so much!

<!-- gh-comment-id:3731164802 --> @mclarkson commented on GitHub (Jan 10, 2026): > [@mclarkson](https://github.com/mclarkson) docs will be updated in 2min with corrections on that page. That's much better 👍 I'm seriously impressed with the quick fixes, thanks so much!
Author
Owner

@Classic298 commented on GitHub (Jan 10, 2026):

Pr is merged thanks everyone

<!-- gh-comment-id:3732491197 --> @Classic298 commented on GitHub (Jan 10, 2026): Pr is merged thanks everyone
Author
Owner

@ALIENvsROBOT commented on GitHub (Jan 10, 2026):

when can we expect the next release ??

<!-- gh-comment-id:3732801673 --> @ALIENvsROBOT commented on GitHub (Jan 10, 2026): when can we expect the next release ??
Author
Owner

@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.

<!-- gh-comment-id:3732887320 --> @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.
Author
Owner

@ALIENvsROBOT commented on GitHub (Jan 10, 2026):

sure thanks so far I fixed it by commenting out those lines

<!-- gh-comment-id:3732888144 --> @ALIENvsROBOT commented on GitHub (Jan 10, 2026): sure thanks so far I fixed it by commenting out those lines
Author
Owner

@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

<!-- gh-comment-id:3778469489 --> @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
Author
Owner

@Classic298 commented on GitHub (Jan 21, 2026):

@quantumalchemy
that just means your session expired. refresh or log out and in again

<!-- gh-comment-id:3779429466 --> @Classic298 commented on GitHub (Jan 21, 2026): @quantumalchemy that just means your session expired. refresh or log out and in again
Author
Owner

@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?

<!-- gh-comment-id:3779666676 --> @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?
Author
Owner

@Classic298 commented on GitHub (Jan 21, 2026):

steps to repro? For me voice and transcription works on all devices on 0.7.2

<!-- gh-comment-id:3779677241 --> @Classic298 commented on GitHub (Jan 21, 2026): steps to repro? For me voice and transcription works on all devices on 0.7.2
Author
Owner

@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

<!-- gh-comment-id:3784635055 --> @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
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#57877