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
Git Clone
Open WebUI Version
v0.6.43.2
Ollama Version (if applicable)
No response
Operating System
win11
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.
Expected Behavior
Users can create a new conversation by clicking the "New Chat" button, and by setting a default model, a new dialog box will be created upon clicking.
Actual Behavior
After clicking "New Chat," the page does not refresh to the new dialog interface but remains on the original conversation. Additionally, the model set via the sidebar cannot be used. When clicking the pre-configured model in the sidebar, the page URL changes, but the expected result is not achieved—the interface still stays on the original conversation page.
Steps to Reproduce
When logged in as a regular user, the functionality of selecting a model and pinning it to the sidebar remains operational. However, when using a model pinned in the sidebar or the preset default model, only the URL changes—the expected effect is not produced.
Logs & Screenshots
Bv06q6k0.js:146 [tiptap warn]: Duplicate extension names found: ['codeBlock', 'bulletList', 'listItem', 'listKeymap', 'orderedList']. This can lead to issues.
Additional Information
No response
Originally created by @ineffable-love on GitHub (Jan 7, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20448
### 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
Git Clone
### Open WebUI Version
v0.6.43.2
### Ollama Version (if applicable)
_No response_
### Operating System
win11
### 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
Users can create a new conversation by clicking the "New Chat" button, and by setting a default model, a new dialog box will be created upon clicking.
### Actual Behavior
After clicking "New Chat," the page does not refresh to the new dialog interface but remains on the original conversation. Additionally, the model set via the sidebar cannot be used. When clicking the pre-configured model in the sidebar, the page URL changes, but the expected result is not achieved—the interface still stays on the original conversation page.
### Steps to Reproduce
When logged in as a regular user, the functionality of selecting a model and pinning it to the sidebar remains operational. However, when using a model pinned in the sidebar or the preset default model, only the URL changes—the expected effect is not produced.
### Logs & Screenshots
Bv06q6k0.js:146 [tiptap warn]: Duplicate extension names found: ['codeBlock', 'bulletList', 'listItem', 'listKeymap', 'orderedList']. This can lead to issues.
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-15 14:56:48 -05:00
@owui-terminator[bot] commented on GitHub (Jan 7, 2026):
🔍Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#20414issue: Chats can't be archived by Ithanil • Jan 06, 2026 • bug
#20059issue: Chat response is not working by navilg • Dec 20, 2025 • bug
💡Tips:
If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
If you found a solution in any of these issues, please share it here to help others
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
<!-- gh-comment-id:3718804490 -->
@owui-terminator[bot] commented on GitHub (Jan 7, 2026):
🔍 **Similar Issues Found**
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
1. [#20414](https://github.com/open-webui/open-webui/issues/20414) **issue: Chats can't be archived**
*by Ithanil • Jan 06, 2026 • `bug`*
2. [#20059](https://github.com/open-webui/open-webui/issues/20059) **issue: Chat response is not working**
*by navilg • Dec 20, 2025 • `bug`*
---
💡 **Tips:**
- If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
- If you found a solution in any of these issues, please share it here to help others
*This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
Additionally, the model set via the sidebar cannot be used. When clicking the pre-configured model in the sidebar, the page URL changes, but the expected result is not achieved—the interface still stays on the original conversation page.
I think this is fixed in dev - please check
<!-- gh-comment-id:3719168012 -->
@Classic298 commented on GitHub (Jan 7, 2026):
> Additionally, the model set via the sidebar cannot be used. When clicking the pre-configured model in the sidebar, the page URL changes, but the expected result is not achieved—the interface still stays on the original conversation page.
I think this is fixed in dev - please check
I am unable to reproduce the described issue on the latest dev branch. I have tested using both Chrome and Firefox browsers. More information is warranted.
<!-- gh-comment-id:3719619326 -->
@silentoplayz commented on GitHub (Jan 7, 2026):
I am unable to reproduce the described issue on the latest `dev` branch. I have tested using both Chrome and Firefox browsers. More information is warranted.
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 @ineffable-love on GitHub (Jan 7, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20448
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v0.6.43.2
Ollama Version (if applicable)
No response
Operating System
win11
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Users can create a new conversation by clicking the "New Chat" button, and by setting a default model, a new dialog box will be created upon clicking.
Actual Behavior
After clicking "New Chat," the page does not refresh to the new dialog interface but remains on the original conversation. Additionally, the model set via the sidebar cannot be used. When clicking the pre-configured model in the sidebar, the page URL changes, but the expected result is not achieved—the interface still stays on the original conversation page.
Steps to Reproduce
When logged in as a regular user, the functionality of selecting a model and pinning it to the sidebar remains operational. However, when using a model pinned in the sidebar or the preset default model, only the URL changes—the expected effect is not produced.
Logs & Screenshots
Bv06q6k0.js:146 [tiptap warn]: Duplicate extension names found: ['codeBlock', 'bulletList', 'listItem', 'listKeymap', 'orderedList']. This can lead to issues.
Additional Information
No response
@owui-terminator[bot] commented on GitHub (Jan 7, 2026):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#20414 issue: Chats can't be archived
by Ithanil • Jan 06, 2026 •
bug#20059 issue: Chat response is not working
by navilg • Dec 20, 2025 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@Classic298 commented on GitHub (Jan 7, 2026):
I think this is fixed in dev - please check
@silentoplayz commented on GitHub (Jan 7, 2026):
I am unable to reproduce the described issue on the latest
devbranch. I have tested using both Chrome and Firefox browsers. More information is warranted.