Originally created by @maksir on GitHub (Apr 28, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Git Clone
Open WebUI Version
0.6.5
Ollama Version (if applicable)
No response
Operating System
Debian 12
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 listed steps to reproduce the bug in detail.
Expected Behavior
After update Open WebUI in docker all user api tokens stay old.
Actual Behavior
After update Open WebUI in docker, all user api tokens have become new. We have to update them in all programs (RooCode, Cline, etc.).
Steps to Reproduce
Go to User settings
Open API Keys
Create new key
Remeber key
Save settings
Update OpenWebUI
Go to User settings
Open API keys
Compare key with previous
Logs & Screenshots
No logs
Additional Information
No response
Originally created by @maksir on GitHub (Apr 28, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Git Clone
### Open WebUI Version
0.6.5
### Ollama Version (if applicable)
_No response_
### Operating System
Debian 12
### 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 listed steps to reproduce the bug in detail.
### Expected Behavior
After update Open WebUI in docker all user api tokens stay old.
### Actual Behavior
After update Open WebUI in docker, all user api tokens have become new. We have to update them in all programs (RooCode, Cline, etc.).
### Steps to Reproduce
1. Go to User settings
2. Open API Keys
3. Create new key
5. Remeber key
4. Save settings
6. Update OpenWebUI
7. Go to User settings
8. Open API keys
9. Compare key with previous
### Logs & Screenshots
No logs
### Additional Information
_No response_
GiteaMirror
added the bug label 2025-11-11 16:08:53 -06:00
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 @maksir on GitHub (Apr 28, 2025).
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
0.6.5
Ollama Version (if applicable)
No response
Operating System
Debian 12
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
After update Open WebUI in docker all user api tokens stay old.
Actual Behavior
After update Open WebUI in docker, all user api tokens have become new. We have to update them in all programs (RooCode, Cline, etc.).
Steps to Reproduce
Logs & Screenshots
No logs
Additional Information
No response
@Classic298 commented on GitHub (Apr 28, 2025):
Cannot reproduce. JWT keys get renewed, yeah, but API keys stay the same for me.
@tjbck commented on GitHub (Apr 28, 2025):
PLEASE check for existing discussions/issues first.
related: https://docs.openwebui.com/getting-started/env-configuration/#webui_secret_key
@Classic298 commented on GitHub (Apr 28, 2025):
Good thought! If the user is not properly setting the secret key.. yeah