issue: Front-End fails silently once JWT Token expires #5280

Closed
opened 2025-11-11 16:16:14 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @cmbaatz on GitHub (May 22, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Other

Open WebUI Version

v0.6.10

Ollama Version (if applicable)

No response

Operating System

Kubernetes

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

It appears in v0.6.10 a change was made as response to Issue 5866 that did the majority of the work to address this issue. However, that solution depending on the Svelte onMount triggers to happen in a specific order. If they do not then even when the JWT token expiration is set the UI will silently fail during session time outs.

Actual Behavior

When a JWT token expiration is set the UI does not guide users through the timeout experience.

Steps to Reproduce

  1. Log into the UI
  2. Wait until the session timed out
  3. Try to access any page

Logs & Screenshots

After debugging this during the login cycle using Oauth SSO the onMount function in routes/+layout.svelte is called before the onMount function in routes/auth/+page.svelte. This is a problem as the token added to local storage in +page.svelte and +layout.svelte will only configures the tokenTimer if the token is found in local storage @ ln 579.

Additional Information

No response

Originally created by @cmbaatz on GitHub (May 22, 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 Other ### Open WebUI Version v0.6.10 ### Ollama Version (if applicable) _No response_ ### Operating System Kubernetes ### 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 It appears in v0.6.10 a change was made as response to [Issue 5866](https://github.com/open-webui/open-webui/issues/5866) that did the majority of the work to address this issue. However, that solution depending on the Svelte onMount triggers to happen in a specific order. If they do not then even when the JWT token expiration is set the UI will silently fail during session time outs. ### Actual Behavior When a JWT token expiration is set the UI does not guide users through the timeout experience. ### Steps to Reproduce 1. Log into the UI 2. Wait until the session timed out 3. Try to access any page ### Logs & Screenshots After debugging this during the login cycle using Oauth SSO the onMount function in routes/+layout.svelte is called before the onMount function in routes/auth/+page.svelte. This is a problem as the token added to local storage in +page.svelte and +layout.svelte will only configures the tokenTimer if the token is found in local storage @ ln 579. ### Additional Information _No response_
GiteaMirror added the bug label 2025-11-11 16:16:14 -06:00
Author
Owner

@tjbck commented on GitHub (May 22, 2025):

Might be addressed with cbe84d7139

@tjbck commented on GitHub (May 22, 2025): Might be addressed with cbe84d71390a8c2ff85ebc07010f35f3a59110ec
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#5280