github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-08 04:16:03 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #20673] issue: Setting ENABLE_API_KEYS to true doesn't work #34787

New Issue
Closed
opened 2026-04-25 08:58:07 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-25 08:58:07 -05:00
Owner
Copy Link

Originally created by @uponminiature on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20673

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

0.7.2

Ollama Version (if applicable)

No response

Operating System

NixOS 25.11

Browser (if applicable)

No response

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

I should be able to view the API key sections after doing the appropriate steps.

Actual Behavior

I cannot see the API key sections.

Steps to Reproduce

  1. Installed Open WebUI via a Docker compose file; never had API Key enabled before.
  2. After many updates, decided I want API Keys. Also noticed ENABLE_PERSISTENT_CONFIG in docs.
  3. Set ENABLE_PERSISTENT_CONFIG to false, set ENABLE_API_KEYS to true. Restarted container.
  4. Created a new user group named "API Access" with the "API Key" permission enabled, added it to myself (admin user).
  5. Did not unlock any API Key sections. Could not get it working after countless restarts.

Logs & Screenshots

Settings -> Account:
Image

Admin -> Users -> Groups -> API Access:
Image
Image
Image

Also noticed a request to a "config" file, located at https://<open_webui>/api/config, I see enable_api_keys is false there.
Image

I validate that the container indeed does have its new environment variables set:
Image

Additional Information

No response

Originally created by @uponminiature on GitHub (Jan 15, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/20673 ### 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) _No response_ ### Operating System NixOS 25.11 ### Browser (if applicable) _No response_ ### 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 I should be able to view the API key sections after doing the appropriate steps. ### Actual Behavior I cannot see the API key sections. ### Steps to Reproduce 1. Installed Open WebUI via a Docker compose file; never had API Key enabled before. 2. After many updates, decided I want API Keys. Also noticed `ENABLE_PERSISTENT_CONFIG` in docs. 3. Set `ENABLE_PERSISTENT_CONFIG` to `false`, set `ENABLE_API_KEYS` to `true`. Restarted container. 4. Created a new user group named "API Access" with the "API Key" permission enabled, added it to myself (admin user). 5. Did not unlock any API Key sections. Could not get it working after countless restarts. ### Logs & Screenshots Settings -> Account: <img width="1651" height="909" alt="Image" src="https://github.com/user-attachments/assets/d89952df-b8ca-422a-8c51-35886f3edd04" /> Admin -> Users -> Groups -> API Access: <img width="386" height="120" alt="Image" src="https://github.com/user-attachments/assets/69160a49-dd62-48e6-a566-89a1a2bd23d3" /> <img width="1101" height="364" alt="Image" src="https://github.com/user-attachments/assets/0b24232f-77cc-492a-be90-75d308018469" /> <img width="965" height="308" alt="Image" src="https://github.com/user-attachments/assets/572c257b-8dcb-4952-bbdd-fed01119f5c6" /> Also noticed a request to a "config" file, located at `https://<open_webui>/api/config`, I see enable_api_keys is false there. <img width="405" height="159" alt="Image" src="https://github.com/user-attachments/assets/6aee2971-bdc6-4045-9fc8-2675eb1ce671" /> I validate that the container indeed does have its new environment variables set: <img width="992" height="230" alt="Image" src="https://github.com/user-attachments/assets/a421eb76-e919-4209-b63f-b6fefc83c653" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-25 08:58:07 -05:00
GiteaMirror commented 2026-04-25 08:58:08 -05:00
Author
Owner
Copy Link

@owui-terminator[bot] commented on GitHub (Jan 15, 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. #20389 issue: ENABLE_SIGNUP not working properly
    by jayteaftw • Jan 05, 2026 • bug

  2. #19853 issue: NOT ABLE TO CREATE A NEW API KEY:
    by Code-With-Samuel • Dec 10, 2025 • bug

  3. #19420 issue: Unable to create new api-keys - 403 forbidden
    by DominikStarke • Nov 24, 2025 • bug

  4. #20361 Issue: Large-scale model setting-related functionality fails.
    by shentong0722 • Jan 04, 2026 • bug

  5. #20064 issue: Create new API key (CRITICAL)
    by richrich89 • Dec 20, 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:3753048659 --> @owui-terminator[bot] commented on GitHub (Jan 15, 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. [#20389](https://github.com/open-webui/open-webui/issues/20389) **issue: ENABLE_SIGNUP not working properly** *by jayteaftw • Jan 05, 2026 • `bug`* 2. [#19853](https://github.com/open-webui/open-webui/issues/19853) **issue: NOT ABLE TO CREATE A NEW API KEY:** *by Code-With-Samuel • Dec 10, 2025 • `bug`* 3. [#19420](https://github.com/open-webui/open-webui/issues/19420) **issue: Unable to create new api-keys - 403 forbidden** *by DominikStarke • Nov 24, 2025 • `bug`* 4. [#20361](https://github.com/open-webui/open-webui/issues/20361) **Issue: Large-scale model setting-related functionality fails.** *by shentong0722 • Jan 04, 2026 • `bug`* 5. [#20064](https://github.com/open-webui/open-webui/issues/20064) **issue: Create new API key (CRITICAL)** *by richrich89 • Dec 20, 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.
GiteaMirror commented 2026-04-25 08:58:09 -05:00
Author
Owner
Copy Link

@uponminiature commented on GitHub (Jan 15, 2026):

There is a third step I missed, where there is a "Enable API Keys" in the Admin Panel. It is confusing why I would have to confirm it again after specifically asking for it to be enabled via env var.

Image
<!-- gh-comment-id:3753058882 --> @uponminiature commented on GitHub (Jan 15, 2026): There is a third step I missed, where there is a "Enable API Keys" in the Admin Panel. It is confusing why I would have to confirm it again after specifically asking for it to be enabled via env var. <img width="1988" height="74" alt="Image" src="https://github.com/user-attachments/assets/dda571bb-a08f-499e-8207-85467e11038d" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#34787
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?