9 views
-/https://github.com/berriai/litellm/issues/23993
GitHub · issue

#23993 [Bug]: Intermittent LiteLLM UI Load Failure After Some Days

  • State: open
  • Author: @manalijj
  • 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? LiteLLM UI is not loading after some days even though container is up and running. Uncaught SyntaxError: Unexpected end of input (at 7e417dd24c8becd0.js:1:20481) Uncaught SyntaxError: Unexpected end of input (at 47812e8f19218c74.js:1:12287)

<img width="1908" height="761" alt="Image" src="https://github.com/user-attachments/assets/7e30e6e7-2cef-4e6d-84b7-acdc07de4ea9" />

### Steps to Reproduce

1. Create litellm-config.yml file:

``` general_settings: master_key: "<key-value>" maximum_spend_logs_retention_period: 30d maximum_spend_logs_retention_interval: 7d database_url: os.environ/DATABASE_URL store_model_in_db: true store_prompts_in_spend_logs: true litellm_settings: cache: true cache_params: type: local ssl_verify: true ssl_security_level: 1 use_litellm_proxy: false ssl_certificate: "<cert-path-goes-here>" redact_user_api_key_info: true ```

2. Create compose.yml file ``` version: "3.11" services: litellm: image: docker.io/litellm/litellm:1.81.16-nightly container_name: <container-name> network_…

Open on GitHub

GitHub resolver

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

Refresh page
vote history (6 events)
#0 of 0 · 31d19h24m10s ago — entered · #import:https:::github.com:berriai:litellm post #1677
-/https://github.com/berriai/litellm/issues/23993⭐4:1-/https://github.com/berriai/litellm/issues/30657
The left issue is harder because it involves diagnosing an intermittent, time-delayed frontend failure with potentially broad interactions among asset delivery, caching, container lifecycle, and deployment state. The right issue is a comparatively contained provider-integration change involving endpoint routing, model translation, and focused regression tests.
#0 of 0 · 31d19h22m34s ago · #import:https:::github.com:berriai:litellm post #1704
-/https://github.com/berriai/litellm/issues/23993⭐5:1-/https://github.com/berriai/litellm/issues/32425
The right issue is substantially harder because it is an intermittent, long-running UI failure with unclear reproduction and potentially spans frontend assets, deployment/runtime behavior, caching, and observability. The left issue is a localized fallback-semantics defect with a narrowly scoped code change and targeted regression tests.
#0 of 0 · 31d19h17m2s ago · #import:https:::github.com:berriai:litellm post #1783
-/https://github.com/berriai/litellm/issues/23993⭐3:1-/https://github.com/berriai/litellm/issues/35157
The right issue is harder because it involves intermittent, long-running frontend failure with uncertain reproduction and potentially spans asset delivery, caching, container lifecycle, and deployment behavior. The left issue is comparatively localized to an existing backend permission-persistence flow with analogous implementations already available.
#0 of 0 · 31d19h12m42s ago · #import:https:::github.com:berriai:litellm post #1856
-/https://github.com/berriai/litellm/issues/23993⭐3:1-/https://github.com/berriai/litellm/issues/34890
The right issue carries greater implementation uncertainty because it is intermittent, long-lived, and spans frontend assets, serving, caching, and deployment behavior; the left is a more localized request-parameter propagation fix across a few API adapters.
#0 of 0 · 31d19h9m22s ago · #import:https:::github.com:berriai:litellm post #1913
-/https://github.com/berriai/litellm/issues/23993⭐3:1-/https://github.com/berriai/litellm/issues/34226
The UI failure is harder because it requires diagnosing a delayed, environment-sensitive problem across frontend asset delivery, caching, container/runtime behavior, and deployment lifecycle, with substantial reproduction and regression risk. The Langfuse issue is comparatively localized to callback field mapping and can be addressed with focused code changes and integration tests.
#0 of 0 · 31d18h53m15s ago — current · #import:https:::github.com:berriai:litellm post #2187
-/https://github.com/berriai/litellm/issues/23993⭐3:1-/https://github.com/berriai/litellm/issues/25456
The right issue is harder because it involves intermittent, long-lived behavior with potentially broad frontend, caching, deployment, and backend interactions, making reproduction and root-cause isolation uncertain. The left issue is a more bounded translation-path defect with a clearer implementation surface and targeted tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search