Originally created by @aleontiev on GitHub (Oct 7, 2024).
Bug Report
Installation Method
Kubernetes via Helm
Environment
Open WebUI Version: was happening on v0.3.30, tried upgrading to v0.3.32 but same issue
Ollama: disabled
Pipelines: disabled
Confirmation:
I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
After login, I am able to use OpenWebUI. This was the case for the first day after installation - had no issues, was able to login with username/password and also with Google OAuth.
Actual Behavior:
Login is successful, I can see the toast message indicating that I have signed in. However, afterwards the screen remains blank and I can see errors in console:
...and network tab shows that some (but not all??) of the startup API requests are failing with 401 errors, particularly "tools" and sometimes "banners":
I tried clearing localStorage and cookies, this resets the login. But after logging in again, same issue. Nothing obvious in backend logs except for the 401s I am seeing on the client side. All other requests are 200s
Description
See Expected/Actual
Reproduction Details
Steps to Reproduce:
Install on Kubernetes via Helm (mostly default settings, Ollama and Pipelines disabled)
Create initial account
Log out
Log back in
Logs and Screenshots
See Actual Behavior
Additional Information
Loved using OpenWebUI for about a day until this started happening consistently :(
Originally created by @aleontiev on GitHub (Oct 7, 2024).
# Bug Report
## Installation Method
Kubernetes via Helm
## Environment
- **Open WebUI Version:** was happening on v0.3.30, tried upgrading to v0.3.32 but same issue
- **Ollama**: disabled
- **Pipelines**: disabled
**Confirmation:**
- [x] I have read and followed all the instructions provided in the README.md.
- [x] I am on the latest version of both Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
After login, I am able to use OpenWebUI. This was the case for the first day after installation - had no issues, was able to login with username/password and also with Google OAuth.
## Actual Behavior:
Login is successful, I can see the toast message indicating that I have signed in. However, afterwards the screen remains blank and I can see errors in console:

...and network tab shows that some (but not all??) of the startup API requests are failing with 401 errors, particularly "tools" and sometimes "banners":

I tried clearing localStorage and cookies, this resets the login. But after logging in again, same issue. Nothing obvious in backend logs except for the 401s I am seeing on the client side. All other requests are 200s
## Description
See Expected/Actual
## Reproduction Details
**Steps to Reproduce:**
- Install on Kubernetes via Helm (mostly default settings, Ollama and Pipelines disabled)
- Create initial account
- Log out
- Log back in
## Logs and Screenshots
See Actual Behavior
## Additional Information
Loved using OpenWebUI for about a day until this started happening consistently :(
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 @aleontiev on GitHub (Oct 7, 2024).
Bug Report
Installation Method
Kubernetes via Helm
Environment
Confirmation:
Expected Behavior:
After login, I am able to use OpenWebUI. This was the case for the first day after installation - had no issues, was able to login with username/password and also with Google OAuth.
Actual Behavior:
Login is successful, I can see the toast message indicating that I have signed in. However, afterwards the screen remains blank and I can see errors in console:
...and network tab shows that some (but not all??) of the startup API requests are failing with 401 errors, particularly "tools" and sometimes "banners":
I tried clearing localStorage and cookies, this resets the login. But after logging in again, same issue. Nothing obvious in backend logs except for the 401s I am seeing on the client side. All other requests are 200s
Description
See Expected/Actual
Reproduction Details
Steps to Reproduce:
Logs and Screenshots
See Actual Behavior
Additional Information
Loved using OpenWebUI for about a day until this started happening consistently :(