I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.
Installation Method
Git Clone
Open WebUI Version
v0.6.29 - v0.6.34
Ollama Version (if applicable)
ollama version is 0.12.6
Operating System
Win11
Browser (if applicable)
FireFox,Edge
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
The results should look like that (its v0.6.27)
Actual Behavior
Currently broken, favicons does not show up, the UI is messy, attached screenshot below.
Steps to Reproduce
1.Install latest version through pip install
2.If the issue does not re-produce, can you share what can I do to try and fix the issue? or why it happens.
Logs & Screenshots
Left is FireFox right is Edge
Additional Information
When used v0.6.27 the favicons did show up, in the later updates it completely broken in all browsers, the favicons does not show.
I am using the pip install option, and the issue persists regardless of if using SearXNG or DuckDuckGo.
Originally created by @iChristGit on GitHub (Oct 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18414
### 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 am using the latest version of Open WebUI.
### Installation Method
Git Clone
### Open WebUI Version
v0.6.29 - v0.6.34
### Ollama Version (if applicable)
ollama version is 0.12.6
### Operating System
Win11
### Browser (if applicable)
FireFox,Edge
### 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
The results should look like that (its v0.6.27)
### Actual Behavior
Currently broken, favicons does not show up, the UI is messy, attached screenshot below.
### Steps to Reproduce
1.Install latest version through pip install
2.If the issue does not re-produce, can you share what can I do to try and fix the issue? or why it happens.
### Logs & Screenshots
<img width="2496" height="1168" alt="Image" src="https://github.com/user-attachments/assets/51321e32-a43c-481c-9b71-6cc24ebbfdcf" />
Left is FireFox right is Edge
### Additional Information
When used [v0.6.27](https://github.com/open-webui/open-webui/releases/tag/v0.6.27) the favicons did show up, in the later updates it completely broken in all browsers, the favicons does not show.
I am using the pip install option, and the issue persists regardless of if using SearXNG or DuckDuckGo.
GiteaMirror
added the bug label 2026-04-25 08:03:04 -05:00
Unable to reproduce, most likely has something to do with your network config.
<!-- gh-comment-id:3420419283 -->
@tjbck commented on GitHub (Oct 20, 2025):
Unable to reproduce, most likely has something to do with your network config.
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 @iChristGit on GitHub (Oct 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18414
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v0.6.29 - v0.6.34
Ollama Version (if applicable)
ollama version is 0.12.6
Operating System
Win11
Browser (if applicable)
FireFox,Edge
Confirmation
README.md.Expected Behavior
The results should look like that (its v0.6.27)
Actual Behavior
Currently broken, favicons does not show up, the UI is messy, attached screenshot below.
Steps to Reproduce
1.Install latest version through pip install
2.If the issue does not re-produce, can you share what can I do to try and fix the issue? or why it happens.
Logs & Screenshots
Additional Information
When used v0.6.27 the favicons did show up, in the later updates it completely broken in all browsers, the favicons does not show.
I am using the pip install option, and the issue persists regardless of if using SearXNG or DuckDuckGo.
@tjbck commented on GitHub (Oct 20, 2025):
Unable to reproduce, most likely has something to do with your network config.