I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.8.10
Ollama Version (if applicable)
No response
Operating System
Ubuntu
Browser (if applicable)
Chrome Latest
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
It works
Actual Behavior
Got "Provider returned error" message. I tried several providers (openrouter, fireworks). It worked on the previous version.
Steps to Reproduce
Basic usage.
Logs & Screenshots
I don't see any errors in logs.
Additional Information
No response
Originally created by @bibendi on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22603
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.8.10
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu
### Browser (if applicable)
Chrome Latest
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using 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.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
It works
### Actual Behavior
Got "Provider returned error" message. I tried several providers (openrouter, fireworks). It worked on the previous version.
### Steps to Reproduce
Basic usage.
### Logs & Screenshots
I don't see any errors in logs.
<img width="1920" height="781" alt="Image" src="https://github.com/user-attachments/assets/a7685022-f713-4638-989c-d5a577f85913" />
<img width="1087" height="316" alt="Image" src="https://github.com/user-attachments/assets/e4414a26-b44b-467a-988b-d24d9579f820" />
<img width="1260" height="393" alt="Image" src="https://github.com/user-attachments/assets/fa5990f3-82bf-4c99-9f92-9aa04dd90f74" />
<img width="1258" height="253" alt="Image" src="https://github.com/user-attachments/assets/90e667e5-4559-4082-b41e-0667caef89fd" />
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-04-20 02:16:10 -05:00
@HammondDynamics commented on GitHub (Mar 13, 2026):
I'm experiencing the same issue on v0.8.10 (Docker, OpenRouter, Claude Sonnet 4.6). I did some investigation and found the root cause.
The issue: Images work in short conversations but fail with "Provider returned error" in long conversations (~80+ messages).
What's happening: Open WebUI sends the image as an internal file UUID reference instead of resolving it to base64 before forwarding to the API provider.
In the browser DevTools (Network tab → Payload), the image in the API request looks like this:
The provider receives the UUID string as the image URL, can't resolve it, and returns an error.
Proof it's not a provider issue: I made a direct API call from inside the container to OpenRouter with 82 messages + the same image as base64, and it returned 200 successfully. The provider handles long conversations with images fine.
Reproduction:
Start a conversation and build up ~80+ messages
Upload and send an image
Observe "Provider returned error"
Start a new conversation, send the same image → works
<!-- gh-comment-id:4053637222 -->
@HammondDynamics commented on GitHub (Mar 13, 2026):
I'm experiencing the same issue on v0.8.10 (Docker, OpenRouter, Claude Sonnet 4.6). I did some investigation and found the root cause.
**The issue:** Images work in short conversations but fail with "Provider returned error" in long conversations (~80+ messages).
**What's happening:** Open WebUI sends the image as an internal file UUID reference instead of resolving it to base64 before forwarding to the API provider.
In the browser DevTools (Network tab → Payload), the image in the API request looks like this:
```json
{"type": "image_url", "image_url": {"url": "7b08d235-3b36-468b-b4f3-39be829f23a4"}}
```
Instead of the expected:
```json
{"type": "image_url", "image_url": {"url": "data:image/png;base64,iVBORw0KGgo..."}}
```
The provider receives the UUID string as the image URL, can't resolve it, and returns an error.
**Proof it's not a provider issue:** I made a direct API call from inside the container to OpenRouter with 82 messages + the same image as base64, and it returned 200 successfully. The provider handles long conversations with images fine.
**Reproduction:**
1. Start a conversation and build up ~80+ messages
2. Upload and send an image
3. Observe "Provider returned error"
4. Start a new conversation, send the same image → works
**Environment:** v0.8.10, Docker (`ghcr.io/open-webui/open-webui:main`), OpenRouter, anthropic/claude-sonnet-4.6
@HammondDynamics the request in the browser is not telling here.
The backend takes the request of the frontend and resolves the file UUID and inserts the base64 before sending it to the provider.
If you only get "provider returned error" on long conversations you might just be facing a context length issue.
<!-- gh-comment-id:4053660757 -->
@Classic298 commented on GitHub (Mar 13, 2026):
@HammondDynamics the request in the browser is not telling here.
The backend takes the request of the frontend and resolves the file UUID and inserts the base64 before sending it to the provider.
If you only get "provider returned error" on long conversations you might just be facing a context length issue.
Proof it's not a provider issue: I made a direct API call from inside the container to OpenRouter with 82 messages + the same image as base64, and it returned 200 successfully. The provider handles long conversations with images fine.
This doesn't proof anything
Open WebUI doesn't store the base64 of the image on the frontend. That would be too expensive and slow to handle.
Instead the backend detects it and inserts the base64
Try sending the WHOLE chat history to the provider, not just the message you think "failed".
<!-- gh-comment-id:4053666427 -->
@Classic298 commented on GitHub (Mar 13, 2026):
> Proof it's not a provider issue: I made a direct API call from inside the container to OpenRouter with 82 messages + the same image as base64, and it returned 200 successfully. The provider handles long conversations with images fine.
This doesn't proof anything
Open WebUI doesn't store the base64 of the image on the frontend. That would be too expensive and slow to handle.
Instead the backend detects it and inserts the base64
Try sending the WHOLE chat history to the provider, not just the message you think "failed".
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 @bibendi on GitHub (Mar 12, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22603
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.8.10
Ollama Version (if applicable)
No response
Operating System
Ubuntu
Browser (if applicable)
Chrome Latest
Confirmation
README.md.Expected Behavior
It works
Actual Behavior
Got "Provider returned error" message. I tried several providers (openrouter, fireworks). It worked on the previous version.
Steps to Reproduce
Basic usage.
Logs & Screenshots
I don't see any errors in logs.
Additional Information
No response
@HammondDynamics commented on GitHub (Mar 13, 2026):
I'm experiencing the same issue on v0.8.10 (Docker, OpenRouter, Claude Sonnet 4.6). I did some investigation and found the root cause.
The issue: Images work in short conversations but fail with "Provider returned error" in long conversations (~80+ messages).
What's happening: Open WebUI sends the image as an internal file UUID reference instead of resolving it to base64 before forwarding to the API provider.
In the browser DevTools (Network tab → Payload), the image in the API request looks like this:
Instead of the expected:
The provider receives the UUID string as the image URL, can't resolve it, and returns an error.
Proof it's not a provider issue: I made a direct API call from inside the container to OpenRouter with 82 messages + the same image as base64, and it returned 200 successfully. The provider handles long conversations with images fine.
Reproduction:
Environment: v0.8.10, Docker (
ghcr.io/open-webui/open-webui:main), OpenRouter, anthropic/claude-sonnet-4.6@Classic298 commented on GitHub (Mar 13, 2026):
@HammondDynamics the request in the browser is not telling here.
The backend takes the request of the frontend and resolves the file UUID and inserts the base64 before sending it to the provider.
If you only get "provider returned error" on long conversations you might just be facing a context length issue.
@Classic298 commented on GitHub (Mar 13, 2026):
This doesn't proof anything
Open WebUI doesn't store the base64 of the image on the frontend. That would be too expensive and slow to handle.
Instead the backend detects it and inserts the base64
Try sending the WHOLE chat history to the provider, not just the message you think "failed".