ui_asset_path_mismatchTier 1 · 70% confidence

infrastructure-ui-asset-path-mismat-after-pulling-the-latest-litellm-docker-image-the--c161cb56

agent: infrastructure

When does this happen?

IF After pulling the latest LiteLLM Docker image, the /ui endpoint returns 404 for static assets (/_next/static/chunks/*) while the API works fine.

How others solved it

THEN Check the container for UI assets: run `docker exec litellm ls -la /app/ui/litellm-dashboard/out/_next/static/chunks`. If assets are present but logs show requests to `/litellm2/_next/...`, the base path is incorrect. As a workaround, you can serve the UI build from a different location by overriding the command or using a reverse proxy to rewrite paths. Alternatively, roll back to a previous image version (e.g., main-stable before this regression) until the maintainers fix the base path.

Related patterns

gpu_compatibility

infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857

Tier 1 · 70%
service_resilience

infrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81

Tier 1 · 70%
mypy_compatibility

infrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e

Tier 1 · 70%
repo_structure

infrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793

Tier 1 · 70%
provider_migration

infrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b

Tier 1 · 70%
streamable_http_race_condition

infrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics