Originally created by @seandearnaley on GitHub (May 30, 2024).
Bug Report
Description
Bug Summary:
New issues connecting to certain LiteLLM models
Steps to Reproduce:
I use the litellm/config.yaml file to integrate multiple LLM models into my UI. Everything worked smoothly until recently when I encountered issues connecting to the Mistral and Perplexity models.
To diagnose the issue, I tested the litellm proxy independently using CURL commands, ensuring the correct "user" role and the same config.yaml configuration I use in open-webui. While other models function correctly in open-webui, the Mistral and Perplexity models remain inaccessible. This leads me to suspect that the litellm proxy might need an update or there is some other bug. The latest version of litellm is 1.39.4, whereas openwebui is on version 1.35.28. Below are the logs and the CURL commands that work when testing litellm on its own:
MistralException - Error code: 400 - {'object': 'error', 'message': 'Expected last role to be one of: [user, tool] but got assistant', 'type': 'invalid_request_error', 'param': None, 'code': None}
External: PerplexityException - Error code: 400 - {'error': {'message': 'Last message must have role `user`.', 'type': 'invalid_message', 'code': 400}}
Environment
Open WebUI Version: [e.g., 0.1.125]
Reproduction Details
Confirmation:
I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
Originally created by @seandearnaley on GitHub (May 30, 2024).
# Bug Report
## Description
**Bug Summary:**
New issues connecting to certain LiteLLM models
**Steps to Reproduce:**
I use the `litellm/config.yaml` file to integrate multiple LLM models into my UI. Everything worked smoothly until recently when I encountered issues connecting to the Mistral and Perplexity models.
To diagnose the issue, I tested the `litellm` proxy independently using CURL commands, ensuring the correct "user" role and the same `config.yaml` configuration I use in open-webui. While other models function correctly in open-webui, the Mistral and Perplexity models remain inaccessible. This leads me to suspect that the `litellm` proxy might need an update or there is some other bug. The latest version of `litellm` is 1.39.4, whereas `openwebui` is on version 1.35.28. Below are the logs and the CURL commands that work when testing `litellm` on its own:
```sh
curl --location 'http://0.0.0.0:4000/chat/completions' \
--header 'Content-Type: application/json' \
--data-raw '{
"model": "perplexity/llama-3-70b-instruct",
"messages": [
{
"role": "user",
"content": "what llm are you"
}
]
}'
```
```sh
curl --location 'http://0.0.0.0:4000/chat/completions' \
--header 'Content-Type: application/json' \
--data-raw '{
"model": "mistral/mistral-large-latest",
"messages": [
{
"role": "user",
"content": "what llm are you"
}
]
}'
```
## Logs and Screenshots
```
MistralException - Error code: 400 - {'object': 'error', 'message': 'Expected last role to be one of: [user, tool] but got assistant', 'type': 'invalid_request_error', 'param': None, 'code': None}
```
```
External: PerplexityException - Error code: 400 - {'error': {'message': 'Last message must have role `user`.', 'type': 'invalid_message', 'code': 400}}
```
## Environment
- **Open WebUI Version:** [e.g., 0.1.125]
## Reproduction Details
**Confirmation:**
- [x] I have read and followed all the instructions provided in the README.md.
- [x] I am on the latest version of both Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
Our latest dev has removed bundled LiteLLM support, I'd recommend you start migrating your LiteLLM config.yaml to a self-hosted LiteLLM instance. You'd still be able to add them to our webui via OpenAI Connections. Thanks for your understanding!
@tjbck commented on GitHub (May 30, 2024):
Our latest dev has removed bundled LiteLLM support, I'd recommend you start migrating your LiteLLM config.yaml to a self-hosted LiteLLM instance. You'd still be able to add them to our webui via OpenAI Connections. Thanks for your understanding!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @seandearnaley on GitHub (May 30, 2024).
Bug Report
Description
Bug Summary:
New issues connecting to certain LiteLLM models
Steps to Reproduce:
I use the
litellm/config.yamlfile to integrate multiple LLM models into my UI. Everything worked smoothly until recently when I encountered issues connecting to the Mistral and Perplexity models.To diagnose the issue, I tested the
litellmproxy independently using CURL commands, ensuring the correct "user" role and the sameconfig.yamlconfiguration I use in open-webui. While other models function correctly in open-webui, the Mistral and Perplexity models remain inaccessible. This leads me to suspect that thelitellmproxy might need an update or there is some other bug. The latest version oflitellmis 1.39.4, whereasopenwebuiis on version 1.35.28. Below are the logs and the CURL commands that work when testinglitellmon its own:Logs and Screenshots
Environment
Reproduction Details
Confirmation:
@tjbck commented on GitHub (May 30, 2024):
Our latest dev has removed bundled LiteLLM support, I'd recommend you start migrating your LiteLLM config.yaml to a self-hosted LiteLLM instance. You'd still be able to add them to our webui via OpenAI Connections. Thanks for your understanding!