8 views
-/https://github.com/berriai/litellm/issues/33150
GitHub · issue

#33150 [Bug]: Authentication error for master key should show IP to allow banning via log #5220

  • State: open
  • Author: @mittalmanu
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

while getting failed request into the LiteLLM fro which the key doesn't exist the source ip is not capturing to investigate the request is coming from . Currently i am running LiteLLM n 1.89.9 version

### Steps to Reproduce

1. Add the key and send some traffic to the allowed model 2. delete the key from the LiteLLM 3. send the traffic again to see request got failed with no requester ip address

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

Proxy

### What LiteLLM version are you on ?

V1.89.3

### Twitter / LinkedIn details

_No response_

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d18h10m57s ago — entered · #import:https:::github.com:berriai:litellm post #2684
The UI change has broader frontend mapping and fallback implications across model naming conventions and provider configurations, while the proxy change is comparatively localized to request-context capture in an error path. The UI work is therefore moderately harder, though neither requires major architectural changes.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search