make sure you somehow get connected to a different replica
see the new group exists, but the user is not added to the group there
Restarting all containers directly after the change seems to make the change persistent.
Logs & Screenshots
I don't see related error messages in the log.
Additional Information
While recent code changes have fixed similar issues for other settings, this one appears to remain.
Originally created by @Ithanil on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12306
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Other
### Open WebUI Version
0.6.0
### Ollama Version (if applicable)
_No response_
### Operating System
Debian 12, Docker, Patroni-PostgreSQL+Redis Sentinel
### 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 listed steps to reproduce the bug in detail.
### Expected Behavior
All setting changes should be synced between all replicas, without requiring container restarts.
### Actual Behavior
Similar to the fixed https://github.com/open-webui/open-webui/issues/10365 and https://github.com/open-webui/open-webui/issues/10278, I still see an equivalent issue with just a particular setting change, namely adding user to groups manually. After adding a user to a group and not restarting all replicas, you may later hit a different replica where the user is not added to the group.
### Steps to Reproduce
1. Create a group
2. add a user to the group via UI and *save*
3. make sure you somehow get connected to a different replica
4. see the new group exists, but the user is not added to the group there
Restarting all containers directly after the change seems to make the change persistent.
### Logs & Screenshots
I don't see related error messages in the log.
### Additional Information
While recent code changes have fixed similar issues for other settings, this one appears to remain.
GiteaMirror
added the bug label 2026-04-25 05:57:50 -05:00
<!-- gh-comment-id:2774142556 -->
@tjbck commented on GitHub (Apr 3, 2025):
This seems very unlikely to be caused by multi-replica setup.
This is the endpoint used to retrieve group information: https://github.com/open-webui/open-webui/blob/04799f1f95f958674d35ba4854ef62754a4d332e/backend/open_webui/routers/groups.py#L33
All group data is stored in the database unlike app.state variables from the previous issue https://github.com/open-webui/open-webui/issues/10365
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 @Ithanil on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12306
Check Existing Issues
Installation Method
Other
Open WebUI Version
0.6.0
Ollama Version (if applicable)
No response
Operating System
Debian 12, Docker, Patroni-PostgreSQL+Redis Sentinel
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
All setting changes should be synced between all replicas, without requiring container restarts.
Actual Behavior
Similar to the fixed https://github.com/open-webui/open-webui/issues/10365 and https://github.com/open-webui/open-webui/issues/10278, I still see an equivalent issue with just a particular setting change, namely adding user to groups manually. After adding a user to a group and not restarting all replicas, you may later hit a different replica where the user is not added to the group.
Steps to Reproduce
Restarting all containers directly after the change seems to make the change persistent.
Logs & Screenshots
I don't see related error messages in the log.
Additional Information
While recent code changes have fixed similar issues for other settings, this one appears to remain.
@tjbck commented on GitHub (Apr 3, 2025):
This seems very unlikely to be caused by multi-replica setup.
This is the endpoint used to retrieve group information: https://github.com/open-webui/open-webui/blob/04799f1f95f958674d35ba4854ef62754a4d332e/backend/open_webui/routers/groups.py#L33
All group data is stored in the database unlike app.state variables from the previous issue https://github.com/open-webui/open-webui/issues/10365