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

#29340 [Bug]: /ui/login returns 404

  • State: open
  • Author: @powellnorma
  • Labels: bug, ui-dashboard

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

I installed 1.85.1 via pip, and while `/fallback/login` works, `/ui` -> `/ui/login` returns a 404 page.

I saw there are special nginx rules, maybe that's why this does not happen in the docker container?

https://github.com/BerriAI/litellm/blob/f11c12d1574fb51acd958bc7173a74e994aacf19/ui/nginx.conf#L82-L86

### Steps to Reproduce

1. pip install litellm==1.85.1 2. litellm --config config.yaml --host 127.0.0.1 --port 1234 3. Open 127.0.0.1:1234/ui in a browser

### Relevant log output

```shell INFO: 127.0.0.1:0 - "GET /login HTTP/1.1" 404 Not Found ```

### What part of LiteLLM is this about?

UI Dashboard

### What LiteLLM version are you on ?

1.85.1

### Twitter / LinkedIn details

_No response_

Open on GitHub

GitHub resolver

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

Refresh page
vote history (4 events)
#0 of 0 · 31d19h7m2s ago — entered · #import:https:::github.com:berriai:litellm post #1772
-/https://github.com/berriai/litellm/issues/300083:1-/https://github.com/berriai/litellm/issues/29340⭐
#30008 is harder because it requires tracing configuration from persistence through runtime guardrail construction, correcting parameter propagation, and adding coverage for multiple formatting paths; #29340 is more localized to deployment-time UI routing and static fallback behavior.
#0 of 0 · 31d19h3m16s ago · #import:https:::github.com:berriai:litellm post #1822
-/https://github.com/berriai/litellm/issues/277365:1-/https://github.com/berriai/litellm/issues/29340⭐
The left task requires coordinated state handling across distributed proxy instances, with concurrency, consistency, and regression-testing risks. The right task is comparatively localized to dashboard routing or packaging configuration.
#0 of 0 · 31d18h58m41s ago · #import:https:::github.com:berriai:litellm post #1899
-/https://github.com/berriai/litellm/issues/253864:1-/https://github.com/berriai/litellm/issues/29340⭐
The left issue is harder because it requires coordinating several persistence and lifecycle paths, preserving budget semantics across existing and newly created records, and adding regression coverage around background processing. The right issue appears narrower, centered on request routing or UI asset serving with a more localized fix.
#0 of 0 · 31d18h41m29s ago — current · #import:https:::github.com:berriai:litellm post #2191
-/https://github.com/berriai/litellm/issues/274593:1-/https://github.com/berriai/litellm/issues/29340⭐
27459 requires tracing and correcting metadata propagation across translation and streaming response paths, with provider-specific regression coverage; 29340 is more likely a localized UI routing or static-serving configuration fix.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search