Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question]: Mistral Endpoint error 422 status code (no body) #1540

Closed
1 task done
euggen0106 opened this issue Jan 13, 2024 · 1 comment · Fixed by #1541
Closed
1 task done

[Question]: Mistral Endpoint error 422 status code (no body) #1540

euggen0106 opened this issue Jan 13, 2024 · 1 comment · Fixed by #1541
Labels
question Further information is requested

Comments

@euggen0106
Copy link

What is your question?

I have deployed Mistral endpoint as per LibreChat instructions but, when I try to use any mistral model I get this response:
Something went wrong. Here's the specific error message we encountered: Error: 422 status code (no body).

More Details

This is my librechat.yaml:
version: "3.4"
cache: true

endpoints:
custom:
# Example using Mistral AI API
- name: "Mistral"
apiKey: "my_api_key"
baseURL: "https://api.mistral.ai/v1"
models:
default: ["mistral-tiny", "mistral-small", "mistral-medium"]
titleConvo: true
titleModel: "mistral-tiny"
summarize: false
summaryModel: "mistral-tiny"
forcePrompt: false
modelDisplayLabel: "Mistral"
addParams:
safe_mode: true
# NOTE: For Mistral, it is necessary to drop the following parameters or you will encounter a 422 Error:
dropParams: ["stop", "user", "frequency_penalty", "presence_penalty"]

What is the main subject of your question?

Endpoints

Screenshots

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@danny-avila
Copy link
Owner

Updated the example to make Mistral AI API work::

We made the API stricter. We did not expect that change to break anything other than incorrect requests, but unfortunately we had not properly documented the safe_prompt flag, which was incorrectly named safe_mode in the documentation (fixed now) and implemented as such by some people. That’s on us - sorry about that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants