litellm - 💡(How to fix) Fix when working with mlx_lm with gemma4, it will invoke /v1/response which mlx_lm serve not supported [1 participants]

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…
GitHub stats
BerriAI/litellm#25418Fetched 2026-04-10 03:41:13
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
labeled ×1

Error Message

on litellm it shows this error

RAW_BUFFERClick to expand / collapse

There's an issue with the selected model (claude-gemma-8bit). It may not exist or you may not have access to it. Run /model to pick a different model.

on litellm it shows this error litellm.exceptions.NotFoundError: litellm.NotFoundError: NotFoundError: OpenAIException - Not Found. Received Model Group=claude-gemma-8bit Available Model Group Fallbacks=None INFO: 192.168.10.29:43018 - "POST /v1/messages?beta=true HTTP/1.1" 404 Not Found

on mlx_lm, it shows this: 127.0.0.1 - - [09/Apr/2026 18:54:48] "POST /v1/responses HTTP/1.1" 404 -

extent analysis

TL;DR

The issue can likely be resolved by selecting a different model using the /model command, as the currently selected model claude-gemma-8bit may not exist or is inaccessible.

Guidance

  • Verify the availability of the model claude-gemma-8bit and check if there are any access restrictions.
  • Run the /model command to pick a different model, as suggested in the error message.
  • Check the documentation or configuration of litellm and mlx_lm to see if there are any specific requirements or settings for model selection.
  • If the issue persists, try checking the API endpoints and parameters to ensure they are correct and properly formatted.

Notes

The exact cause of the issue is unclear, but it appears to be related to model selection or availability. The error messages suggest a NotFoundError, which implies that the model may not exist or is not accessible.

Recommendation

Apply workaround: Run the /model command to select a different model, as this is the most straightforward solution suggested by the error messages.

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