github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-10 15:54:15 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

issue: Knowledge file returns 404 for users with WRITE access #6751

New Issue
Closed
opened 2025-11-11 17:05:04 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-11 17:05:04 -06:00
Owner
Copy Link

Originally created by @mkwforaus on GitHub (Oct 24, 2025).

Check Existing Issues

  • 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:

  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

Image

Additional Information

Is it a bug or if there is any workaround for this issue

Originally created by @mkwforaus on GitHub (Oct 24, 2025). ### 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 2025-11-11 17:05:04 -06:00
GiteaMirror commented 2025-11-11 17:05:05 -06:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 26, 2025):

@silentoplayz confirmation wanted here!

@tjbck commented on GitHub (Oct 26, 2025): @silentoplayz confirmation wanted here!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#6751
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?