7 views
-/https://github.com/berriai/litellm/issues/23451
GitHub · issue

#23451 [Bug]: Can't login despite setting password

  • State: open
  • Author: @markg85
  • 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 am setting the environment variables for the password but the UI simply doesn't allow me to login. Not with `admin` not with `sk-1234` not with anything.

I'm using whatever it is that's in the docker image (ghcr.io/berriai/litellm:main-stable)

As an aside, please provide an option to **not** have a login at all. I get it from a security point of view, fine. But i'm running this is a local environment on a local pc. It really makes no sense to have a login in that case. Which i'd argue is a high percentage of your users too.

### Steps to Reproduce

My docker-compose: ``` services: litellm: image: ghcr.io/berriai/litellm:main-stable container_name: litellm ports: - '4400:4000' dns: # ← Add explicit DNS servers - 8.8.8.8 - 1.1.1.1 env_file: - .env environment: - DEEPINFRA_API_KEY=${DEEPINFRA_API_KEY} - LITELLM_MASTER_KEY=sk-1234 - MASTER_KEY=admin - LITELLM_LOG=INFO - UI_USERNAME=admin - UI_PASSWORD=admin volumes: - ./config.yaml:/app/config.yaml:…

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d17h58m43s ago — entered · #import:https:::github.com:berriai:litellm post #2891
The right-side change has substantially greater scope and risk: it affects credential data modeling, authorization semantics, routing precedence, backward compatibility, and integration testing. The left-side work is comparatively narrower, centered on diagnosing and correcting authentication configuration behavior.
#0 of 0 · 31d17h46m7s ago — current · #import:https:::github.com:berriai:litellm post #3115
The right is harder because it requires tracing authentication configuration across the container, backend, and dashboard, while safely handling a potentially security-sensitive login-bypass option. The left is a narrowly identified dependency-boundary and release-integration regression with an existing fix to validate and backport.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search