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.26
Ollama Version (if applicable)
No response
Operating System
Linux Container
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
Setup Steps:
Create a user group "Support"
Assign User A and User B to the user group
Grant "Write" access to the user group "Support" for a knowledge base A
Upload 10 files to the knowledge base A using User A
Expected Result:
Both User A and User B should be able to view all the 10 files
Actual Behavior
Actual Result:
User A can see all the files while user B can see around 8 out of 10 files under the knowledge section and throw 404 for the remaining 2 files
The files cannot be accessed are random and sometimes more and sometimes less
Steps to Reproduce
Setup Steps:
Create a user group "Support"
Assign User A and User B to the user group
Grant "Write" access to the user group "Support" for a knowledge base A
Upload 10 files to the know base A using User A
Change to user B and access the knowledge base A
Click the files uploaded (There are some files throw 404 errors)
Logs & Screenshots
Additional Information
Is it a bug or if there is any workaround for this issue
Originally created by @mkwforaus on GitHub (Oct 24, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18571
### 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.26
### Ollama Version (if applicable)
_No response_
### Operating System
Linux Container
### 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
Setup Steps:
1. Create a user group "Support"
2. Assign User A and User B to the user group
3. Grant "Write" access to the user group "Support" for a knowledge base A
4. Upload 10 files to the knowledge base A using User A
Expected Result:
1. Both User A and User B should be able to view all the 10 files
### Actual Behavior
Actual Result:
1. User A can see all the files while user B can see around 8 out of 10 files under the knowledge section and throw 404 for the remaining 2 files
2. The files cannot be accessed are random and sometimes more and sometimes less
### Steps to Reproduce
Setup Steps:
1. Create a user group "Support"
2. Assign User A and User B to the user group
3. Grant "Write" access to the user group "Support" for a knowledge base A
4. Upload 10 files to the know base A using User A
5. Change to user B and access the knowledge base A
6. Click the files uploaded (There are some files throw 404 errors)
### Logs & Screenshots
<img width="1918" height="242" alt="Image" src="https://github.com/user-attachments/assets/9e541ed9-e22c-4dff-9a25-93ae589c6e48" />
### Additional Information
Is it a bug or if there is any workaround for this issue
GiteaMirror
added the bug label 2026-05-18 03:40:35 -05:00
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 @mkwforaus on GitHub (Oct 24, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18571
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v0.6.26
Ollama Version (if applicable)
No response
Operating System
Linux Container
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Setup Steps:
Expected Result:
Actual Behavior
Actual Result:
Steps to Reproduce
Setup Steps:
Logs & Screenshots
Additional Information
Is it a bug or if there is any workaround for this issue
@tjbck commented on GitHub (Oct 26, 2025):
@silentoplayz confirmation wanted here!