github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #17009] issue: Previous Public Knowledge does not display to new users after update to 0.6.25 #33666

New Issue
Closed
opened 2026-04-25 07:33:46 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-25 07:33:46 -05:00
Owner
Copy Link

Originally created by @btbean1980 on GitHub (Aug 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17009

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

0.6.25

Ollama Version (if applicable)

0.11.6

Operating System

RHEL 9

Browser (if applicable)

Chrome 139.0.7258.155

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

When a new user logs in for the first time and navigates to Workspaces/Knowledge, they should be presented with all Publicly available Knowledge repositories.

Actual Behavior

New users are not provided with any public marked knowledge repositories and have a blank Knowledge repo.

Steps to Reproduce

  1. Install OWUI version prior to 0.6.25
  2. Create a user
  3. Create multiple public Knowledge repos
  4. Upgrade to OWUI 0.6.25
  5. Create a new user
  6. Attempt to access Knowledge to view public Knowledge repos.

Logs & Screenshots

New User after Update
Image

Old User after Update
Image

Additional Information

No response

Originally created by @btbean1980 on GitHub (Aug 28, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17009 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version 0.6.25 ### Ollama Version (if applicable) 0.11.6 ### Operating System RHEL 9 ### Browser (if applicable) Chrome 139.0.7258.155 ### 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 When a new user logs in for the first time and navigates to Workspaces/Knowledge, they should be presented with all Publicly available Knowledge repositories. ### Actual Behavior New users are not provided with any public marked knowledge repositories and have a blank Knowledge repo. ### Steps to Reproduce 1. Install OWUI version prior to 0.6.25 2. Create a user 3. Create multiple public Knowledge repos 4. Upgrade to OWUI 0.6.25 5. Create a new user 6. Attempt to access Knowledge to view public Knowledge repos. ### Logs & Screenshots New User after Update <img width="1129" height="631" alt="Image" src="https://github.com/user-attachments/assets/107d26f6-bc93-4bc0-a583-11ca91308a54" /> Old User after Update <img width="1708" height="1066" alt="Image" src="https://github.com/user-attachments/assets/89c6d551-7248-476f-9189-ede355406280" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-25 07:33:46 -05:00
GiteaMirror commented 2026-04-25 07:33:48 -05:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (Aug 28, 2025):

are you checked permissions?

<!-- gh-comment-id:3234218851 --> @rgaricano commented on GitHub (Aug 28, 2025): are you checked permissions?
GiteaMirror commented 2026-04-25 07:33:48 -05:00
Author
Owner
Copy Link

@btbean1980 commented on GitHub (Aug 28, 2025):

Yes. Permissions are checked. We are using Microsoft Entra for access, so everyone has the same access from an AD perspective. Other users that joined prior to the 0.6.25 update can see the Public Knowledge that has been shared.

<!-- gh-comment-id:3234243040 --> @btbean1980 commented on GitHub (Aug 28, 2025): Yes. Permissions are checked. We are using Microsoft Entra for access, so everyone has the same access from an AD perspective. Other users that joined prior to the 0.6.25 update can see the Public Knowledge that has been shared.
GiteaMirror commented 2026-04-25 07:33:49 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Aug 28, 2025):

We're unable to reproduce, as @rgaricano points out, you may want to check knowledge permissions.

<!-- gh-comment-id:3234243075 --> @tjbck commented on GitHub (Aug 28, 2025): We're unable to reproduce, as @rgaricano points out, you may want to check knowledge permissions.
GiteaMirror commented 2026-04-25 07:33:49 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Aug 28, 2025):

@btbean1980 can you share your access control settings for the knowledge as well as your group settings in the admin panel?

your issue post is not enough for us to correctly diagnose anything here.

<!-- gh-comment-id:3234246260 --> @tjbck commented on GitHub (Aug 28, 2025): @btbean1980 can you share your access control settings for the knowledge as well as your group settings in the admin panel? your issue post is not enough for us to correctly diagnose anything here.
GiteaMirror commented 2026-04-25 07:33:50 -05:00
Author
Owner
Copy Link

@btbean1980 commented on GitHub (Aug 28, 2025):

@tjbck would user have to even be in a group to see Public knowledge? Groups should only be required for Private knowledge access. The user in question is a "user". The knowledge is set to Public.

Default User/Group permissions are below:

Image
<!-- gh-comment-id:3234255608 --> @btbean1980 commented on GitHub (Aug 28, 2025): @tjbck would user have to even be in a group to see Public knowledge? Groups should only be required for Private knowledge access. The user in question is a "user". The knowledge is set to Public. Default User/Group permissions are below: <img width="697" height="492" alt="Image" src="https://github.com/user-attachments/assets/6a6c1570-1158-4489-a612-adc24751dd6a" />
GiteaMirror commented 2026-04-25 07:33:51 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Aug 28, 2025):

@btbean1980 Above only shows workspace "access" and "sharing" permissions, they're different to access controls which can be configured per knowledge, could you confirm those are set as public as well?

<!-- gh-comment-id:3234261249 --> @tjbck commented on GitHub (Aug 28, 2025): @btbean1980 Above only shows workspace "access" and "sharing" permissions, they're different to access controls which can be configured per knowledge, could you confirm those are set as public as well?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
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#33666
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?