Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix [Bug]: AWS Bedrock model down - LiteLLM unresponsive

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Which is likely due to the timeout issue and getting an HTML page/error

Code Example

ON the webui, when I try to log in I get:


Unexpected token '<', "<html> <h"... is not valid JSON


Which is likely due to the timeout issue and getting an HTML page/error
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

Not sure what happened. We have been getting timeouts from AWS Bedrock models. Which isnt your problem or LiteLLM's for that matter.

However, with those calls timing out, it seems that LiteLLM is completely hanging. I cannot load the webgui or the swagger main page. It times out MOST of the time...

Steps to Reproduce

Connect to failing AWS Bedrock Sonnet models (Though we are in fedrmap environment with Claude Sonnet 4.5)

These are timing out it seems, and this appears to be locking up litellm process

If I remove my AWS Bedrock models (Leaving in my azure and local vLLM models, everything starts to work again.

Relevant log output

ON the webui, when I try to log in I get:


Unexpected token '<', "<html> <h"... is not valid JSON


Which is likely due to the timeout issue and getting an HTML page/error

What part of LiteLLM is this about?

No response

What LiteLLM version are you on ?

v1.85.1

Twitter / LinkedIn details

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - 💡(How to fix) Fix [Bug]: AWS Bedrock model down - LiteLLM unresponsive