[Bug]: /ui is not accessible

[thibmaek]

What happened?

This happened after I pulled the latest image. I failed to fix it with my existing containers so here's what I did:

1. Verify LiteLLM is still available as an API → ✅
2. Listed models via /v1/models and saved the response as a backup
3. Removed the running container and deleted the image: docker stop litellm && docker rm litellm && docker image rm ghcr.io/berriai/litellm:main-latest
4. Recreated the container: docker compose up -d
5. Disabled pi-hole on the network just in case

The DB seems to work fine, but even after this the UI remains inaccessible and shows the log output below and the following in the browser:

---

My compose.yaml:

services:
  litellm:
    image: ghcr.io/berriai/litellm:main-latest
    container_name: litellm
    env_file: litellm.env
    volumes:
      - ./data/config.yaml:/app/config.yaml
    ports:
      - 4000:4000
    command: ['--config=/app/config.yaml']
    restart: unless-stopped

  litellm_db:
    image: postgres
    container_name: litellm_db
    env_file: litellm.env
    ports:
      - 5432:5432
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -d litellm -U llmproxy"]
      interval: 1s
      timeout: 5s
      retries: 10
    restart: unless-stopped

My litellm.env file:

DATABASE_URL="postgresql://llmproxy:*******@litellm_db:5432/litellm"
STORE_MODEL_IN_DB=True
MASTER_KEY="*******"

POSTGRES_DB=litellm
POSTGRES_USER=llmproxy
POSTGRES_PASSWORD=*******

# Ollama
OLLAMA_API_BASE=*******
OLLAMA_API_KEY=""

MISTRAL_API_KEY=*******

LANGFUSE_PUBLIC_KEY=pk-*******
LANGFUSE_SECRET_KEY=sk-*******
LANGFUSE_HOST=*******

My LiteLLM config:

general_settings:
  master_key: os.environ/MASTER_KEY
  pass_through_endpoints:
    - path: "/mistral/v1/ocr"
      target: "https://api.mistral.ai/v1/ocr"
      headers:
        Authorization: "bearer os.environ/MISTRAL_API_KEY"
        content-type: application/json
        accept: application/json
      forward_headers: True

model_list: []

Relevant log output

litellm  | INFO:     Shutting down
litellm  | INFO:     Waiting for application shutdown.
litellm  | INFO:     Application shutdown complete.
litellm  | INFO:     Finished server process [1]
litellm  | prisma:warn Prisma doesn't know which engines to download for the Linux distro "wolfi". Falling back to Prisma engines built "debian".
litellm  | Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros.
litellm  | Prisma schema loaded from schema.prisma
litellm  | Datasource "client": PostgreSQL database "litellm", schema "public" at "litellm_db:5432"
litellm  |
litellm  | The database is already in sync with the Prisma schema.
litellm  |
Running generate... - Prisma Client Python (v0.11.0)
litellm  |
litellm  | Some types are disabled by default due to being incompatible with Mypy, it is highly recommended
litellm  | to use Pyright instead and configure Prisma Python to use recursive types. To re-enable certain types:
litellm  |
litellm  | generator client {
litellm  |   provider             = "prisma-client-py"
litellm  |   recursive_type_depth = -1
litellm  | }
litellm  |
litellm  | If you need to use Mypy, you can also disable this message by explicitly setting the default value:
litellm  |
litellm  | generator client {
litellm  |   provider             = "prisma-client-py"
litellm  |   recursive_type_depth = 5
litellm  | }
litellm  |
litellm  | For more information see: https://prisma-client-py.readthedocs.io/en/stable/reference/limitations/#default-type-limitations
litellm  |
✔ Generated Prisma Client Python (v0.11.0) to ./../../prisma in 388ms
litellm  |
litellm  | INFO:     Started server process [1]
litellm  | INFO:     Waiting for application startup.
litellm  | INFO:     Application startup complete.
litellm  | INFO:     Uvicorn running on http://0.0.0.0:4000 (Press CTRL+C to quit)
litellm  |
litellm  | #------------------------------------------------------------#
litellm  | #                                                            #
litellm  | #           'It would help me if you could add...'            #
litellm  | #        https://github.com/BerriAI/litellm/issues/new        #
litellm  | #                                                            #
litellm  | #------------------------------------------------------------#
litellm  |
litellm  |  Thank you for using LiteLLM! - Krrish & Ishaan
litellm  |
litellm  |
litellm  |
litellm  | Give Feedback / Get Help: https://github.com/BerriAI/litellm/issues/new
litellm  |
litellm  |
litellm  | INFO:     192.168.1.x:58284 - "GET /ui/ HTTP/1.1" 200 OK
litellm  | INFO:     192.168.1.x:58284 - "GET /litellm2/_next/static/chunks/webpack-a426aae3231a8df1.js HTTP/1.1" 404 Not Found
litellm  | INFO:     192.168.1.x:58285 - "GET /litellm2/_next/static/chunks/fd9d1056-205af899b895cbac.js HTTP/1.1" 404 Not Found
litellm  | INFO:     192.168.1.x:58284 - "GET /litellm2/_next/static/chunks/117-c4922b1dd81b62ce.js HTTP/1.1" 404 Not Found
litellm  | INFO:     192.168.1.x:58286 - "GET /litellm2/_next/static/chunks/main-app-4f7318ae681a6d94.js HTTP/1.1" 404 Not Found

Are you a ML Ops Team?

No

What LiteLLM version are you on ?

always the latest main-stable

Twitter / LinkedIn details

No response

[thibmaek]

I find it weird that it's trying to look to the /litellm2/... directory for assets and after opening a shell in the container I can confirm the assets it's looking for are available in /app/ui/litellm-dashboard/out/_next/static/chunks

[AdithyanI]

Ah, someone created this! Thank you. I was going crazy thinking that I made a mistake and doing different things to bring it back up. Looks like it's a bug.

+1 to @thibmaek . I can't access the UI pane. I did some analysis and debugged and found the exact lines exactly as Thib wrote here: #11531 (comment)

Fix would be nice here please 🙏🏽 . Can't access the admin panel anymore!

[JerryAlbeg]

can confirm that the same issue stated for me after pulling the latest docker
same 4 error lines appear in logs when accessing /ui
the system works, just can't access the admin panels.

[frenzybiscuit]

I cannot access /ui on the latest docker...

[nmcbride]

Same issue here.

[mckenna654]

I am getting the same issue since updating my docker today.

INFO: 192.168.0.82:54185 - "GET /ui/ HTTP/1.1" 304 Not Modified
INFO: 192.168.0.82:54185 - "GET /litellm2/_next/static/chunks/webpack-a426aae3231a8df1.js HTTP/1.1" 404 Not Found
INFO: 192.168.0.82:54186 - "GET /litellm2/_next/static/chunks/fd9d1056-205af899b895cbac.js HTTP/1.1" 404 Not Found
INFO: 192.168.0.82:54186 - "GET /litellm2/_next/static/chunks/117-c4922b1dd81b62ce.js HTTP/1.1" 404 Not Found
INFO: 192.168.0.82:54185 - "GET /litellm2/_next/static/chunks/main-app-4f7318ae681a6d94.js HTTP/1.1" 404 Not Found

[VigneshwarRajasekaran]

This was an issues with new ui build and was fixed in 1.72.3. Please check using the latest version.

Cheers!

[thibmaek]

Can confirm this is fixed in main-stable aka main-v1.72.2.rc. Seems like main-latest still needs the fix

services:
  litellm:
+ image: ghcr.io/berriai/litellm:main-v1.72.2.rc

[mrexodia]

I am having the exact same issue on v1.72.2.rc:

pip install "litellm[proxy] @ git+https://github.com/BerriAI/litellm.git@v1.72.2.rc" --upgrade

Jun 09 10:36:06 litellm service.sh[12659]: INFO:     192.168.10.135:0 - "GET /ui/ HTTP/1.1" 200 OK
Jun 09 10:36:06 litellm service.sh[12659]: INFO:     192.168.10.135:0 - "GET /litellm2/_next/static/chunks/webpack-a426aae3231a8df1.js HTTP/1.1" 404 Not Found
Jun 09 10:36:06 litellm service.sh[12659]: INFO:     192.168.10.135:0 - "GET /litellm2/_next/static/chunks/fd9d1056-205af899b895cbac.js HTTP/1.1" 404 Not Found
Jun 09 10:36:06 litellm service.sh[12659]: INFO:     192.168.10.135:0 - "GET /litellm2/_next/static/chunks/main-app-4f7318ae681a6d94.js HTTP/1.1" 404 Not Found
Jun 09 10:36:06 litellm service.sh[12659]: INFO:     192.168.10.135:0 - "GET /litellm2/_next/static/chunks/117-c4922b1dd81b62ce.js HTTP/1.1" 404 Not Found
Jun 09 10:36:06 litellm service.sh[12659]: INFO:     192.168.10.135:0 - "GET /favicon.ico HTTP/1.1" 404 Not Found

[mrexodia]

My bad, it looks like --upgrade does not correctly update everything 🤦‍♂. I solved it with the following command:

pip install "litellm[proxy] @ git+https://github.com/BerriAI/litellm.git@v1.72.2.rc" --upgrade --force-reinstall

[seonghobae]

This bug still occurs on 1.17.2.rc.

[frenzybiscuit]

This is not fixed on docker.

[OrionCodeDev]

pip install litellm
also don't working /ui