7 views
-/https://github.com/berriai/litellm/issues/27048
GitHub · issue

#27048 Chat UI (/ui/chat) returns 404 - Next.js static export routing issue

  • State: open
  • Author: @nobu007
  • Labels: stale

## Problem

The Chat UI feature added on March 6, 2026 (PR #22937) is not accessible at `/ui/chat`. Accessing this endpoint returns `404 Not Found`.

## Investigation

- Chat UI code exists in GitHub repository: `ui/litellm-dashboard/src/app/chat/page.tsx` - Chat UI artifacts exist in Docker image: `chat.html`, `chat/` directory in `/app/litellm/proxy/_experimental/out/` - However, Next.js `__next._tree.txt` does not include the chat route - GitHub latest commit (934ecdca78daf7ec9514efd47df77bf7495c822d) also has this issue

## Root Cause

Next.js static export routing issue. The `__next._tree.txt` file does not include the chat route, even though the chat page source code exists.

## Expected Behavior

`/ui/chat` should serve the Chat UI page.

## Environment

- LiteLLM Version: 1.83.10 (latest main-stable) - Docker Image: docker.litellm.ai/berriai/litellm:main-stable - Next.js Config: `output: "export"`, `basePath: ""`

Open on GitHub

GitHub resolver

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

Refresh page
vote history (5 events)
#0 of 0 · 31d18h2m42s ago — entered · #import:https:::github.com:berriai:litellm post #2803
-/https://github.com/berriai/litellm/issues/262143:1-/https://github.com/berriai/litellm/issues/27048⭐
The right issue is harder because it requires diagnosing and safely adapting cross-provider request translation, handling provider-specific parameter compatibility, and adding regression coverage across proxy and model integrations. The left issue is comparatively localized to frontend static-export route generation and build validation.
#0 of 0 · 31d17h43m0s ago · #import:https:::github.com:berriai:litellm post #3153
-/https://github.com/berriai/litellm/issues/347715:1-/https://github.com/berriai/litellm/issues/27048⭐
The left task requires coordinating authentication state, redirect handling, protocol semantics, and compatibility across multiple clients and upstream providers, creating substantially higher regression and security risk. The right task is comparatively localized to frontend build and route-generation configuration.
#0 of 0 · 31d17h42m40s ago · #import:https:::github.com:berriai:litellm post #3158
-/https://github.com/berriai/litellm/issues/27048⭐4:1-/https://github.com/berriai/litellm/issues/34231
The right issue involves diagnosing and correcting a framework build/export and deployed-route integration, with broader configuration and validation risk; the left is a localized UI styling/data-mapping change.
#0 of 0 · 31d17h41m56s ago · #import:https:::github.com:berriai:litellm post #3170
-/https://github.com/berriai/litellm/issues/311793:1-/https://github.com/berriai/litellm/issues/27048⭐
MCP compatibility requires deeper protocol, session, routing, and client-interoperability investigation, with greater regression risk. The UI problem is more localized to frontend static-export/build configuration and should have a narrower validation surface.
#0 of 0 · 31d17h40m16s ago — current · #import:https:::github.com:berriai:litellm post #3199
-/https://github.com/berriai/litellm/issues/321935:1-/https://github.com/berriai/litellm/issues/27048⭐
Issue 32193 is substantially harder: it requires designing a general configuration and SDK contract, implementing provider-agnostic matching and transformation logic across varied error paths, handling streaming and sensitive-data safety, and preserving compatibility across proxy and client surfaces. Issue 27048 is comparatively localized to diagnosing and correcting a frontend static-export route/build integration.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search