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
0.7.2
Ollama Version (if applicable)
0.12.6
Operating System
Ubuntu 24.04.3 LTS
Browser (if applicable)
N/A
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
After upgrade, existing API settings should persist and API should still operate as it did before the upgrade
Actual Behavior
API access deactivated - had to manually re-activate it.
Users who had API access before the upgrade lost access after the upgrade.
Users are now getting a mixture of {"detail":"Method Not Allowed"} and {"detail":"API key not allowed to access this endpoint."}
Steps to Reproduce
Use last latest version before 0.7.2, enable API access for user accounts and confirm API access works.
Upgrade to 0.7.2.
Observe API is now disabled, and when manually re-enabled, API access is not possible.
Logs & Screenshots
N/A
Additional Information
No response
Originally created by @huornlmj on GitHub (Jan 23, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20901
### 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
0.7.2
### Ollama Version (if applicable)
0.12.6
### Operating System
Ubuntu 24.04.3 LTS
### Browser (if applicable)
N/A
### 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
After upgrade, existing API settings should persist and API should still operate as it did before the upgrade
### Actual Behavior
API access deactivated - had to manually re-activate it.
Users who had API access before the upgrade lost access after the upgrade.
Users are now getting a mixture of `{"detail":"Method Not Allowed"}` and `{"detail":"API key not allowed to access this endpoint."}`
### Steps to Reproduce
Use last latest version before 0.7.2, enable API access for user accounts and confirm API access works.
Upgrade to 0.7.2.
Observe API is now disabled, and when manually re-enabled, API access is not possible.
### Logs & Screenshots
N/A
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-20 01:44:32 -05:00
@owui-terminator[bot] commented on GitHub (Jan 23, 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:
#20840issue: OTEL seems not working on 0.7.2 by tnndclub • Jan 21, 2026 • bug
#20812issue: Unable to start Open WebUI on SaaS platforms (Render, Koyeb) after updating to v0.7.2 by tempppabx1 • Jan 20, 2026 • bug
#20128issue: Characters are broken in 0.6.43 by frenzybiscuit • Dec 22, 2025 • bug
#20327issue: Unable to use any Open WebUI version newer than 0.6.25 due to hybrid search performance by galvanoid • Jan 02, 2026 • bug
#18145issue: 0.6.33 regression by Ark-Levy • Oct 08, 2025 • bug
Show 5 more related issues
#19496issue: 500 internal server error appears in v0.6.40 by cloudtuotuo • Nov 26, 2025 • bug
#19417issue: v0.6.37 SQL Error by AKHYP • Nov 24, 2025 • bug
#14529issue: Open WebUI does not work on versions after version 0.6.7 by OpenSoftware-World • May 30, 2025 • bug
#16025issue: 404 and style errors in 0.6.15+ by drewbroadbent • Jul 25, 2025 • bug
#20087issue: Audio transcript broken at 0.6.42 by zilingzhang • Dec 22, 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:3791113665 -->
@owui-terminator[bot] commented on GitHub (Jan 23, 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. [#20840](https://github.com/open-webui/open-webui/issues/20840) **issue: OTEL seems not working on 0.7.2**
*by tnndclub • Jan 21, 2026 • `bug`*
2. [#20812](https://github.com/open-webui/open-webui/issues/20812) **issue: Unable to start Open WebUI on SaaS platforms (Render, Koyeb) after updating to v0.7.2**
*by tempppabx1 • Jan 20, 2026 • `bug`*
3. [#20128](https://github.com/open-webui/open-webui/issues/20128) **issue: Characters are broken in 0.6.43**
*by frenzybiscuit • Dec 22, 2025 • `bug`*
4. [#20327](https://github.com/open-webui/open-webui/issues/20327) **issue: Unable to use any Open WebUI version newer than 0.6.25 due to hybrid search performance**
*by galvanoid • Jan 02, 2026 • `bug`*
5. [#18145](https://github.com/open-webui/open-webui/issues/18145) **issue: 0.6.33 regression**
*by Ark-Levy • Oct 08, 2025 • `bug`*
<details>
<summary>Show 5 more related issues</summary>
6. [#19496](https://github.com/open-webui/open-webui/issues/19496) **issue: 500 internal server error appears in v0.6.40**
*by cloudtuotuo • Nov 26, 2025 • `bug`*
7. [#19417](https://github.com/open-webui/open-webui/issues/19417) **issue: v0.6.37 SQL Error**
*by AKHYP • Nov 24, 2025 • `bug`*
8. [#14529](https://github.com/open-webui/open-webui/issues/14529) **issue: Open WebUI does not work on versions after version 0.6.7**
*by OpenSoftware-World • May 30, 2025 • `bug`*
9. [#16025](https://github.com/open-webui/open-webui/issues/16025) **issue: 404 and style errors in 0.6.15+**
*by drewbroadbent • Jul 25, 2025 • `bug`*
10. [#20087](https://github.com/open-webui/open-webui/issues/20087) **issue: Audio transcript broken at 0.6.42**
*by zilingzhang • Dec 22, 2025 • `bug`*
</details>
---
💡 **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.
Sorry - false positive. The issue is actually different now, in that previous models I had made are not visible now via API, but other models that are just available from a simple ollama pull are working.
<!-- gh-comment-id:3791175427 -->
@huornlmj commented on GitHub (Jan 23, 2026):
Sorry - false positive. The issue is actually different now, in that previous models I had made are not visible now via API, but other models that are just available from a simple ollama pull are working.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @huornlmj on GitHub (Jan 23, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20901
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.7.2
Ollama Version (if applicable)
0.12.6
Operating System
Ubuntu 24.04.3 LTS
Browser (if applicable)
N/A
Confirmation
README.md.Expected Behavior
After upgrade, existing API settings should persist and API should still operate as it did before the upgrade
Actual Behavior
API access deactivated - had to manually re-activate it.
Users who had API access before the upgrade lost access after the upgrade.
Users are now getting a mixture of
{"detail":"Method Not Allowed"}and{"detail":"API key not allowed to access this endpoint."}Steps to Reproduce
Use last latest version before 0.7.2, enable API access for user accounts and confirm API access works.
Upgrade to 0.7.2.
Observe API is now disabled, and when manually re-enabled, API access is not possible.
Logs & Screenshots
N/A
Additional Information
No response
@owui-terminator[bot] commented on GitHub (Jan 23, 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:
#20840 issue: OTEL seems not working on 0.7.2
by tnndclub • Jan 21, 2026 •
bug#20812 issue: Unable to start Open WebUI on SaaS platforms (Render, Koyeb) after updating to v0.7.2
by tempppabx1 • Jan 20, 2026 •
bug#20128 issue: Characters are broken in 0.6.43
by frenzybiscuit • Dec 22, 2025 •
bug#20327 issue: Unable to use any Open WebUI version newer than 0.6.25 due to hybrid search performance
by galvanoid • Jan 02, 2026 •
bug#18145 issue: 0.6.33 regression
by Ark-Levy • Oct 08, 2025 •
bugShow 5 more related issues
#19496 issue: 500 internal server error appears in v0.6.40
by cloudtuotuo • Nov 26, 2025 •
bug#19417 issue: v0.6.37 SQL Error
by AKHYP • Nov 24, 2025 •
bug#14529 issue: Open WebUI does not work on versions after version 0.6.7
by OpenSoftware-World • May 30, 2025 •
bug#16025 issue: 404 and style errors in 0.6.15+
by drewbroadbent • Jul 25, 2025 •
bug#20087 issue: Audio transcript broken at 0.6.42
by zilingzhang • Dec 22, 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.
@huornlmj commented on GitHub (Jan 23, 2026):
Sorry - false positive. The issue is actually different now, in that previous models I had made are not visible now via API, but other models that are just available from a simple ollama pull are working.