mirror of
https://github.com/open-webui/open-webui.git
synced 2026-11-14 05:02:01 -06:00
[GH-ISSUE #4902] Image recognition is broken when uploading the image, works fine when providing the path #29307
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#29307
Reference in New Issue
Block a user
Originally created by @AxelFooley on GitHub (Aug 25, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/4902
Bug Report
I've been trying a few vision models in the past couple of days and all of them don't work properly in open-webui.
When uploading the image the prediction is completely broken, and it seems like the LLM is rather "thinking" about a random image and providing the description of that, instead of the uploaded one.
The same model works just fine when using ollama cli.
Weirdly, if instead of uploading the image i provide the full path, then the prediction is correct.
In the screenshot below you will see the LLM going wild at the end of the message, this is not related to open-webui, using other models works just in the same way (ie. good when providing path, wrong when uploading image).
Installation Method
Docker on Linux
Environment
Open WebUI Version: "main" docker image
Ollama (if applicable): latest windows standalone
Operating System: Ollama: Windows, open-webui: Linux
Browser (if applicable): Brave
Confirmation:
Expected Behavior:
Prediction is the same whether i provide the path or upload the image.
Actual Behavior:
Described above
Description
Bug Summary:
[Provide a brief but clear summary of the bug]
Reproduction Details
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots/Screen Recordings (if applicable):
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!