[GH-ISSUE #14057] feat: Users should stay logged in across restarts/ upgrades #55789

Closed
opened 2026-05-05 18:03:16 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @luantak on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14057

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Whenever I upgrade or restart my openwebui instance all users have to re-authenticate.

Desired Solution you'd like

I would like for users to not have to re-authenticate (type in their userrname / password) after the instance is restarted.

Alternatives Considered

No response

Additional Context

I'm using the default sqlite backend (if that's relevant)

Originally created by @luantak on GitHub (May 20, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14057 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Whenever I upgrade or restart my openwebui instance all users have to re-authenticate. ### Desired Solution you'd like I would like for users to not have to re-authenticate (type in their userrname / password) after the instance is restarted. ### Alternatives Considered _No response_ ### Additional Context I'm using the default sqlite backend (if that's relevant)
Author
Owner

@athoik commented on GitHub (May 20, 2025):

Check Keeps being logged out after every update?

<!-- gh-comment-id:2892825456 --> @athoik commented on GitHub (May 20, 2025): Check [Keeps being logged out after every update?](https://docs.openwebui.com/getting-started/updating#keeps-being-logged-out-after-every-update)
Author
Owner

@luantak commented on GitHub (May 20, 2025):

Ah ok thanks for this, however why not just persist this token by default somewhere in /app/backend/data (if none is set explicitly?

<!-- gh-comment-id:2892853088 --> @luantak commented on GitHub (May 20, 2025): Ah ok thanks for this, however why not just persist this token by default somewhere in `/app/backend/data` (if none is set explicitly?
Author
Owner

@Classic298 commented on GitHub (May 20, 2025):

Because it is meant to be used as environment variable.

At last, if you use high concurrency setups like k8s/helm or just use multiple uvicorn workers they all need to have it in the environment variable and read it from there. Otherwise multiple processes need to read it from a single file ;)

<!-- gh-comment-id:2893019985 --> @Classic298 commented on GitHub (May 20, 2025): Because it is meant to be used as environment variable. At last, if you use high concurrency setups like k8s/helm or just use multiple uvicorn workers they all need to have it in the environment variable and read it from there. Otherwise multiple processes need to read it from a single file ;)
Author
Owner

@luantak commented on GitHub (May 20, 2025):

@Classic298 so if it isn't set a distributed setup wouldn't work anyway

<!-- gh-comment-id:2893092271 --> @luantak commented on GitHub (May 20, 2025): @Classic298 so if it isn't set a distributed setup wouldn't work anyway
Author
Owner

@Classic298 commented on GitHub (May 20, 2025):

yeah if it isn't used as a distributed setup, it could indeed make itself a persistent value by just reading the same file everytime.

I suspect this wasn't done to keep complexity low (otherwise there'd be two different ways of reading it depending on whether Open WebUI runs with a distributed setup)

<!-- gh-comment-id:2893154622 --> @Classic298 commented on GitHub (May 20, 2025): yeah if it isn't used as a distributed setup, it could indeed make itself a persistent value by just reading the same file everytime. I suspect this wasn't done to keep complexity low (otherwise there'd be two different ways of reading it depending on whether Open WebUI runs with a distributed setup)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#55789