Originally created by @Hugobox on GitHub (May 22, 2024).
Bug Report
Description
Bug Summary:
We use model Llama 3 70B via litellm and it works well, but as soon as we upload any image file (png or jpg) the webui becomes unresponsive and has to be restarted, no error found in logs. PDFs do not crash webui, only images.
Normally with models that do not support image uploads like GPT3.5-turbo, we get the following error message:
"Uh-oh! There was an issue connecting to gpt-3.5-turbo.
External: Invalid content type. image_url is only supported by certain models."
But it seems like with Llama 3 70B via litellm this file type check is not done correctly.
Steps to Reproduce:
use model Llama 3 70B via litellm
open webui, set model to Llama 3 70B
test model with text prompt, notice it works
test model with image upload and text prompt, notice it becomes unresponsive.
Expected Behavior:
[Describe what you expected to happen.]
Actual Behavior:
[Describe what actually happened.]
Environment
Open WebUI Version: v0.1.125
Operating System: [Ubuntu 20.04]
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.
I have included the browser console logs.
I have included the Docker container logs.
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
Docker-compose file
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
Originally created by @Hugobox on GitHub (May 22, 2024).
# Bug Report
## Description
**Bug Summary:**
We use model Llama 3 70B via litellm and it works well, but as soon as we upload any image file (png or jpg) the webui becomes unresponsive and has to be restarted, no error found in logs. PDFs do not crash webui, only images.
Normally with models that do not support image uploads like GPT3.5-turbo, we get the following error message:
"Uh-oh! There was an issue connecting to gpt-3.5-turbo.
External: Invalid content type. image_url is only supported by certain models."
But it seems like with Llama 3 70B via litellm this file type check is not done correctly.
**Steps to Reproduce:**
use model Llama 3 70B via litellm
open webui, set model to Llama 3 70B
test model with text prompt, notice it works
test model with image upload and text prompt, notice it becomes unresponsive.
**Expected Behavior:**
[Describe what you expected to happen.]
**Actual Behavior:**
[Describe what actually happened.]
## Environment
- **Open WebUI Version:** v0.1.125
- **Operating System:** [Ubuntu 20.04]
## 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.
- [ ] I have included the browser console logs.
- [ ] I have included the Docker container logs.
## Logs and Screenshots
**Browser Console Logs:**
[Include relevant browser console logs, if applicable]
**Docker Container Logs:**
[Include relevant Docker container logs, if applicable]
**Screenshots (if applicable):**
[Attach any relevant screenshots to help illustrate the issue]
## Installation Method
Docker-compose file
## Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
## Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
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 @Hugobox on GitHub (May 22, 2024).
Bug Report
Description
Bug Summary:
We use model Llama 3 70B via litellm and it works well, but as soon as we upload any image file (png or jpg) the webui becomes unresponsive and has to be restarted, no error found in logs. PDFs do not crash webui, only images.
Normally with models that do not support image uploads like GPT3.5-turbo, we get the following error message:
"Uh-oh! There was an issue connecting to gpt-3.5-turbo.
External: Invalid content type. image_url is only supported by certain models."
But it seems like with Llama 3 70B via litellm this file type check is not done correctly.
Steps to Reproduce:
use model Llama 3 70B via litellm
open webui, set model to Llama 3 70B
test model with text prompt, notice it works
test model with image upload and text prompt, notice it becomes unresponsive.
Expected Behavior:
[Describe what you expected to happen.]
Actual Behavior:
[Describe what actually happened.]
Environment
Open WebUI Version: v0.1.125
Operating System: [Ubuntu 20.04]
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
Docker-compose file
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!