github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-17 07:46:16 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #17969] issue: Default User Role resets after redeploy or few minutes #105448

New Issue
Closed
opened 2026-05-18 03:27:53 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-18 03:27:53 -05:00
Owner
Copy Link

Originally created by @aimendenche-nw on GitHub (Oct 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17969

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.6.32

Ollama Version (if applicable)

No response

Operating System

ubuntu

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

The default user role setting should persist across time and pod restarts. Once set to user, new users should automatically get the user role without requiring manual approval.

Actual Behavior

When we set the default user role from pending to user, the setting does not persist:

After a few minutes, it automatically reverts back to pending.

If we redeploy the pod, it also resets back to pending

Impact:
This forces us to manually approve every new user on their first login, even though the admin already configured the default role as user.

Steps to Reproduce

Steps to Reproduce:

Go to Settings → Authentication in OpenWebUI.

Change Default User Role from pending to user.

Save the settings.

Confirm that new users are initially created with the user role.

Wait a few minutes or redeploy the OpenWebUI pod (in Kubernetes / Docker).

Check the Default User Role setting again → it has reverted back to pending.

New users must again be manually approved.

Logs & Screenshots

Image

Additional Information

No response

Originally created by @aimendenche-nw on GitHub (Oct 1, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17969 ### 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 am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.6.32 ### Ollama Version (if applicable) _No response_ ### Operating System ubuntu ### 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 The default user role setting should persist across time and pod restarts. Once set to user, new users should automatically get the user role without requiring manual approval. ### Actual Behavior When we set the default user role from pending to user, the setting does not persist: After a few minutes, it automatically reverts back to pending. If we redeploy the pod, it also resets back to pending Impact: This forces us to manually approve every new user on their first login, even though the admin already configured the default role as user. ### Steps to Reproduce Steps to Reproduce: Go to Settings → Authentication in OpenWebUI. Change Default User Role from pending to user. Save the settings. Confirm that new users are initially created with the user role. Wait a few minutes or redeploy the OpenWebUI pod (in Kubernetes / Docker). Check the Default User Role setting again → it has reverted back to pending. New users must again be manually approved. ### Logs & Screenshots <img width="1389" height="141" alt="Image" src="https://github.com/user-attachments/assets/f9b0e6ce-fd46-48eb-8263-308f23571e00" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-18 03:27:53 -05:00
GiteaMirror commented 2026-05-18 03:27:55 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 1, 2025):

Unable to reproduce, you're likely resetting the persistent config.

<!-- gh-comment-id:3357359225 --> @tjbck commented on GitHub (Oct 1, 2025): Unable to reproduce, you're likely resetting the persistent config.
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#105448
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?