6 views
-/https://github.com/berriai/litellm/issues/14635
GitHub · issue

#14635 [Bug]: "litellm.Timeout: Connection timed out after None seconds. "

  • State: open
  • Author: @johann-petrak
  • Labels: bug

### What happened?

LiteLLM SDK version 1.77.1

I am getting the following error from litellm: "litellm.Timeout: Connection timed out after None seconds."

There is obviously a bug in how the timeout gets measured by LiteLLM as it always shows "None seconds"

It would also be interesting to understand if where that timeout actually comes from, and e.g. if the underlying methods for establishing the connection could get parametrized with a longer timeout or if the remote API server has ended the connection? What kind of timeout is this?

### Are you a ML Ops Team?

No

### What LiteLLM version are you on ?

1.77.1

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d18h32m27s ago — entered · #import:https:::github.com:berriai:litellm post #2335
The right issue is harder because it requires tracing deployment identity through multiple proxy, passthrough, normalization, and spend-logging paths, then preserving consistent behavior without affecting cost attribution or analytics. The left issue is more localized to timeout propagation and error reporting.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search