8 views
-/https://github.com/berriai/litellm/issues/31095
GitHub · issue

#31095 UI: Expired authentication causes page to freeze with 401 errors instead of redirecting to login

  • State: open
  • Author: @GuillaumeASSIER

## Bug Description

When the user's authentication session expires while navigating the LiteLLM UI, the frontend does not redirect to the login page. Instead, the current page freezes and all components start displaying 401 (Unauthorized) errors.

## Steps to Reproduce

1. Log in to the LiteLLM UI 2. Leave the session idle long enough for the authentication to expire (or let the token expire) 3. Interact with the page or wait for components to refresh

## Expected Behavior

When the authentication expires, the UI should automatically redirect the user to the login page so they can re-authenticate.

## Actual Behavior

- The page freezes and becomes unresponsive - No redirect to the login page is triggered - The user is stuck on a broken page with no way to re-authenticate without manually navigating to the login URL

## Impact

This leads to a poor user experience. Users are left on a non-functional page with error messages they may not understand, with no clear path to re-authenticate.

## Environment

- LiteLLM UI (browser-based admin interface)

## Suggested Fix

The frontend should intercept 401 responses globally and redirect the user to the login page when the session has exp…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d19h3m11s ago — entered · #import:https:::github.com:berriai:litellm post #1812
The harder item requires coordinated cross-cutting frontend error handling, authentication-state recovery, routing, and regression testing across multiple request paths. The easier item is a localized UI-generation change with a smaller surface area and simpler verification.
Issue 28979 has greater engineering risk because it requires tracing distributed spend aggregation, timing, caching, and provider/tag-specific accounting to isolate an intermittent consistency defect. Issue 31095 is comparatively contained in the frontend authentication/error-handling layer, with a clearer global interception and navigation fix.
#0 of 0 · 31d18h40m40s ago — current · #import:https:::github.com:berriai:litellm post #2194
The left task spans asynchronous streaming assembly, logging callbacks, response-shape normalization, billing correctness, and regression coverage across API paths. The right task is narrower, likely centered on centralized client-side authentication error handling and navigation behavior, though it still requires validating interaction with existing session flows.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search