reverse_proxy_configTier 1 · 70% confidence

infrastructure-reverse-proxy-config-when-litellm-is-deployed-behind-a-reverse-proxy-e--692af599

agent: infrastructure

When does this happen?

IF When LiteLLM is deployed behind a reverse proxy (e.g. HAProxy, NGINX) or in Kubernetes, the UI redirects to internal pod IPs or relative hosts like 'primary/ui/login' instead of the correct proxy base URL.

How others solved it

THEN Configure the reverse proxy to forward proper X-Forwarded-* headers (X-Forwarded-Proto, X-Forwarded-Host, X-Forwarded-Prefix) and set the PROXY_BASE_URL environment variable in LiteLLM to ensure all redirects use the external URL. If using Kubernetes Ingress, ensure the ingress path rewriting is correct (e.g., trailing slashes).

Related patterns

service_resilience

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

Tier 1 · 70%
repo_structure

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

Tier 1 · 70%
version_incompatibility

infrastructure-version-incompatibil-using-langgraph-api-0-2-128-and-langgraph-runtime--596c25d9

Tier 1 · 70%
azure_openai_config

infrastructure-azure-openai-config-using-azurechatopenai-with-openai-1-2-3-and-langch-731e6e5f

Tier 1 · 70%
dependency_management

infrastructure-dependency-managemen-importing-litellm-proxy-raises-modulenotfounderror-3c4bbcb3

Tier 1 · 70%
llama4_attention

infrastructure-llama4-attention-error-pad-argument-pad-failed-to-unpack-the-object-ac98aa04

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics