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
Other
Open WebUI Version
0.8.8
Ollama Version (if applicable)
No response
Operating System
Proxmox LXC
Browser (if applicable)
No response
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.
root@openwebui:~# uv tool install open-webui==0.8.10 --force --no-cache
× No solution found when resolving dependencies:
╰─▶ Because there is no version of ddgs==9.11.2 and open-webui==0.8.10 depends on ddgs==9.11.2, we can conclude that open-webui==0.8.10 cannot be
used.
And because you require open-webui==0.8.10, we can conclude that your requirements are unsatisfiable.
Steps to Reproduce
Run uv tool upgrade open-webui --no-cache with 0.8.8 installed
Logs & Screenshots
root@openwebui:~# uv tool install open-webui==0.8.10 --force --no-cache
× No solution found when resolving dependencies:
╰─▶ Because there is no version of ddgs==9.11.2 and open-webui==0.8.10 depends on ddgs==9.11.2, we can conclude that open-webui==0.8.10 cannot be
used.
And because you require open-webui==0.8.10, we can conclude that your requirements are unsatisfiable.
Originally created by @adix992 on GitHub (Mar 23, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22944
### 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!).
- [ ] I am using the latest version of Open WebUI.
### Installation Method
Other
### Open WebUI Version
0.8.8
### Ollama Version (if applicable)
_No response_
### Operating System
Proxmox LXC
### Browser (if applicable)
_No response_
### 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
Update with:
uv tool upgrade open-webui --no-cache
### Actual Behavior
root@openwebui:~# uv tool install open-webui==0.8.10 --force --no-cache
× No solution found when resolving dependencies:
╰─▶ Because there is no version of ddgs==9.11.2 and open-webui==0.8.10 depends on ddgs==9.11.2, we can conclude that open-webui==0.8.10 cannot be
used.
And because you require open-webui==0.8.10, we can conclude that your requirements are unsatisfiable.
### Steps to Reproduce
Run uv tool upgrade open-webui --no-cache with 0.8.8 installed
### Logs & Screenshots
root@openwebui:~# uv tool install open-webui==0.8.10 --force --no-cache
× No solution found when resolving dependencies:
╰─▶ Because there is no version of ddgs==9.11.2 and open-webui==0.8.10 depends on ddgs==9.11.2, we can conclude that open-webui==0.8.10 cannot be
used.
And because you require open-webui==0.8.10, we can conclude that your requirements are unsatisfiable.
https://pypi.org/project/ddgs/#history - 9.11.2 no longer exists
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-18 05:19:19 -05:00
I closed it because I saw there were other closed topics with this issue, didn't want to create duplicated. I used Gemini 3.1 Pro to come up with this solution that worked for me:
Thought (21s)
Considering the Override
I'm currently focused on the implications of using the --override flag in uv to resolve the dependency conflict for the Open WebUI update. Specifically, it involves the unavailable ddgs==9.11.2. I'm evaluating if this force installation is the best path forward given the potential risks.
Clarifying Dependency Override
I'm now investigating the specific command needed to accept ddgs==9.11.3 instead of the problematic 9.11.2 version. I've been diving into uv's documentation, focusing on how --with might offer a direct command-line override, as the standard --override isn't directly supported. Although --with seems promising, there's a concern that uv's strict dependency management might still raise a conflict error because open-webui rigidly demands 9.11.2, so I'm evaluating how to handle this with uv tool install.
Confirming uv Override Behavior
I'm now focusing on directly using --override with uv. It seems I need to create an overrides file for uv pip install, which I will then provide to uv tool install. I'm evaluating the exact command structure for uv pip install --override overrides.txt open-webui==0.8.10 and if there's a fileless approach, but I haven't found a direct string implementation within uv. The documentation indicates that a file is likely necessary for the override to be effective.
Verifying Tool Override
I've confirmed that uv tool installdoes accept --override in newer versions, resolving my previous uncertainty. Now, I'm verifying the command uv tool install --override overrides.txt open-webui==0.8.10 directly. I am confident that is the correct syntax.
Refining Install Commands
I'm now refining the install commands to ensure the override works correctly and the service restarts smoothly. I'll execute echo "ddgs==9.11.3" > /root/overrides.txt followed by uv tool install open-webui==0.8.10 --override /root/overrides.txt --force --no-cache to force the desired dependency version. Then, I plan to run systemctl restart open-webui. I'm double-checking the flags for robustness. However, I have a backup command if needed.
Formulating a Response
I'm now formulating a precise response, acknowledging a promising solution. My focus is on providing exact terminal commands to bypass the dependency conflict. I'll outline the steps: creating the override file with ddgs==9.11.3, running the uv tool install command using the file, cleaning up the file, and restarting the service. I'm ensuring clarity and correctness in the commands, reflecting the standard practice for uv.
Finalizing Update Instructions
I'm now integrating potential fallback commands to handle different uv versions. I'm focusing on ensuring compatibility. My plan includes offering direct instructions. First, if uv tool install works, then I'll use uv tool install open-webui==0.8.10 --override /root/override.txt --force --no-cache. Otherwise, I'll recommend uv pip install open-webui==0.8.10 --override /root/override.txt --system --target .... I'm also including --with ddgs==9.11.3 as an alternative to the override.
Evaluating Command Precision
I'm now refining the fallback strategy. Considering that --with adds constraints and doesn't override, I'm sticking with the --override approach, which is the official uv method. The current focus is on building a robust and reliable command structure, including the core commands: echo "ddgs==9.11.3" > /root/override.txt, and uv tool install open-webui==0.8.10 --override /root/override.txt --force --no-cache. I'm evaluating a backup using uv pip install if the tool version is older.
That is an excellent find! You likely saw that on the official GitHub issues page.
In modern Python package managers like uv, the --override command is a powerful tool. It intercepts the strict version checker and says, "I know the developer hard-coded version 9.11.2, but I am forcing you to use 9.11.3 instead."
Because the --override flag requires a text file to read from, you just need to create a tiny temporary file with that rule, run the update, and restart.
Here are the exact commands to copy and paste into your terminal:
1. Create the override file
This command creates a temporary text file containing the forced version:
echo"ddgs==9.11.3" > /root/override.txt
2. Force the installation
Now run the uv tool, telling it to read your override file to bypass the broken dependency:
Give it 10–15 seconds to spin up, refresh your browser, and you will officially be on version 0.8.10
<!-- gh-comment-id:4118605028 -->
@adix992 commented on GitHub (Mar 24, 2026):
I closed it because I saw there were other closed topics with this issue, didn't want to create duplicated. I used Gemini 3.1 Pro to come up with this solution that worked for me:
<details>
<summary>Thought (21s)</summary>
> **Considering the Override**
>
> I'm currently focused on the implications of using the `--override` flag in `uv` to resolve the dependency conflict for the Open WebUI update. Specifically, it involves the unavailable `ddgs==9.11.2`. I'm evaluating if this force installation is the best path forward given the potential risks.
>
>
> **Clarifying Dependency Override**
>
> I'm now investigating the specific command needed to accept `ddgs==9.11.3` instead of the problematic 9.11.2 version. I've been diving into `uv`'s documentation, focusing on how `--with` might offer a direct command-line override, as the standard `--override` isn't directly supported. Although `--with` seems promising, there's a concern that `uv`'s strict dependency management might still raise a conflict error because `open-webui` rigidly demands 9.11.2, so I'm evaluating how to handle this with `uv tool install`.
>
>
> **Confirming `uv` Override Behavior**
>
> I'm now focusing on directly using `--override` with `uv`. It seems I need to create an overrides file for `uv pip install`, which I will then provide to `uv tool install`. I'm evaluating the exact command structure for `uv pip install --override overrides.txt open-webui==0.8.10` and if there's a fileless approach, but I haven't found a direct string implementation within `uv`. The documentation indicates that a file is likely necessary for the override to be effective.
>
>
> **Verifying Tool Override**
>
> I've confirmed that `uv tool install` *does* accept `--override` in newer versions, resolving my previous uncertainty. Now, I'm verifying the command `uv tool install --override overrides.txt open-webui==0.8.10` directly. I am confident that is the correct syntax.
>
>
> **Refining Install Commands**
>
> I'm now refining the install commands to ensure the override works correctly and the service restarts smoothly. I'll execute `echo "ddgs==9.11.3" > /root/overrides.txt` followed by `uv tool install open-webui==0.8.10 --override /root/overrides.txt --force --no-cache` to force the desired dependency version. Then, I plan to run `systemctl restart open-webui`. I'm double-checking the flags for robustness. However, I have a backup command if needed.
>
>
> **Formulating a Response**
>
> I'm now formulating a precise response, acknowledging a promising solution. My focus is on providing exact terminal commands to bypass the dependency conflict. I'll outline the steps: creating the override file with `ddgs==9.11.3`, running the `uv tool install` command using the file, cleaning up the file, and restarting the service. I'm ensuring clarity and correctness in the commands, reflecting the standard practice for `uv`.
>
>
> **Finalizing Update Instructions**
>
> I'm now integrating potential fallback commands to handle different `uv` versions. I'm focusing on ensuring compatibility. My plan includes offering direct instructions. First, if `uv tool install` works, then I'll use `uv tool install open-webui==0.8.10 --override /root/override.txt --force --no-cache`. Otherwise, I'll recommend `uv pip install open-webui==0.8.10 --override /root/override.txt --system --target ...`. I'm also including `--with ddgs==9.11.3` as an alternative to the override.
>
>
> **Evaluating Command Precision**
>
> I'm now refining the fallback strategy. Considering that `--with` adds constraints and doesn't override, I'm sticking with the `--override` approach, which is the official `uv` method. The current focus is on building a robust and reliable command structure, including the core commands: `echo "ddgs==9.11.3" > /root/override.txt`, and `uv tool install open-webui==0.8.10 --override /root/override.txt --force --no-cache`. I'm evaluating a backup using `uv pip install` if the tool version is older.
</details>That is an excellent find! You likely saw that on the official GitHub issues page.
In modern Python package managers like `uv`, the `--override` command is a powerful tool. It intercepts the strict version checker and says, *"I know the developer hard-coded version 9.11.2, but I am forcing you to use 9.11.3 instead."*
Because the `--override` flag requires a text file to read from, you just need to create a tiny temporary file with that rule, run the update, and restart.
Here are the exact commands to copy and paste into your terminal:
### 1. Create the override file
This command creates a temporary text file containing the forced version:
```bash
echo "ddgs==9.11.3" > /root/override.txt
```
### 2. Force the installation
Now run the `uv` tool, telling it to read your override file to bypass the broken dependency:
```bash
uv tool install open-webui==0.8.10 --override /root/override.txt --force --no-cache
```
### 3. Clean up and Restart
Once the installation finishes successfully, delete the temporary file and restart the Open WebUI service to load version 0.8.10 into RAM:
```bash
rm /root/override.txt
systemctl restart open-webui
```
Give it 10–15 seconds to spin up, refresh your browser, and you will officially be on version 0.8.10
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 @adix992 on GitHub (Mar 23, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22944
Check Existing Issues
Installation Method
Other
Open WebUI Version
0.8.8
Ollama Version (if applicable)
No response
Operating System
Proxmox LXC
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Update with:
uv tool upgrade open-webui --no-cache
Actual Behavior
root@openwebui:~# uv tool install open-webui==0.8.10 --force --no-cache
× No solution found when resolving dependencies:
╰─▶ Because there is no version of ddgs==9.11.2 and open-webui==0.8.10 depends on ddgs==9.11.2, we can conclude that open-webui==0.8.10 cannot be
used.
And because you require open-webui==0.8.10, we can conclude that your requirements are unsatisfiable.
Steps to Reproduce
Run uv tool upgrade open-webui --no-cache with 0.8.8 installed
Logs & Screenshots
root@openwebui:~# uv tool install open-webui==0.8.10 --force --no-cache
× No solution found when resolving dependencies:
╰─▶ Because there is no version of ddgs==9.11.2 and open-webui==0.8.10 depends on ddgs==9.11.2, we can conclude that open-webui==0.8.10 cannot be
used.
And because you require open-webui==0.8.10, we can conclude that your requirements are unsatisfiable.
https://pypi.org/project/ddgs/#history - 9.11.2 no longer exists
Additional Information
No response
@Aadamcor commented on GitHub (Mar 24, 2026):
hi im having the same issue were you able to fix this
@montvid commented on GitHub (Mar 24, 2026):
How to fix this? why is it closed?
@adix992 commented on GitHub (Mar 24, 2026):
I closed it because I saw there were other closed topics with this issue, didn't want to create duplicated. I used Gemini 3.1 Pro to come up with this solution that worked for me:
Thought (21s)
In modern Python package managers like
uv, the--overridecommand is a powerful tool. It intercepts the strict version checker and says, "I know the developer hard-coded version 9.11.2, but I am forcing you to use 9.11.3 instead."Because the
--overrideflag requires a text file to read from, you just need to create a tiny temporary file with that rule, run the update, and restart.Here are the exact commands to copy and paste into your terminal:
1. Create the override file
This command creates a temporary text file containing the forced version:
2. Force the installation
Now run the
uvtool, telling it to read your override file to bypass the broken dependency:3. Clean up and Restart
Once the installation finishes successfully, delete the temporary file and restart the Open WebUI service to load version 0.8.10 into RAM:
Give it 10–15 seconds to spin up, refresh your browser, and you will officially be on version 0.8.10