When using open-webui for multi-replica deployment, configuration changes do not take effect across different replicas, possibly due to the settings being loaded into memory. For example, after enabling internet search, querying /api/v1/retrieval/config occasionally still shows web.search.enable as false. The issue is resolved after restarting all the Pods.
Reproduction Details
Steps to Reproduce:
Scale the open-webui deployment to 2 or more Pods.
Change some configuration settings and save them.
Use the API (e.g., /api/v1/retrieval/config) to check if the settings have been applied.
Refresh and repeat the API call multiple times to ensure requests are routed to different Pods.
Originally created by @OrenZhang on GitHub (Feb 19, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10365
Originally assigned to: @tjbck on GitHub.
# Bug Report
## Installation Method
Pod in K8S Cluster
## Environment
- **Open WebUI Version:** v0.5.14
- **Operating System:** MacOS 15
- **Browser:** Edge 133.0
## Description
**Bug Summary:**
When using open-webui for multi-replica deployment, configuration changes do not take effect across different replicas, possibly due to the settings being loaded into memory. For example, after enabling internet search, querying `/api/v1/retrieval/config` occasionally still shows `web.search.enable` as false. The issue is resolved after restarting all the Pods.
## Reproduction Details
**Steps to Reproduce:**
- Scale the open-webui deployment to 2 or more Pods.
- Change some configuration settings and save them.
- Use the API (e.g., /api/v1/retrieval/config) to check if the settings have been applied.
- Refresh and repeat the API call multiple times to ensure requests are routed to different Pods.
Has it been fixed? I also encountered this problem
Not yet, still have it in 5.18
<!-- gh-comment-id:2691527777 -->
@tkg61 commented on GitHub (Feb 28, 2025):
> Has it been fixed? I also encountered this problem
Not yet, still have it in 5.18
@tjbck Still having issues with this in 0.6.0 with redis configured. Settings are not synced between instances. i can just refresh the page and see different banners appear between the instances
<!-- gh-comment-id:2772901076 -->
@tkg61 commented on GitHub (Apr 2, 2025):
@tjbck Still having issues with this in 0.6.0 with redis configured. Settings are not synced between instances. i can just refresh the page and see different banners appear between the instances
@tjbck Still having issues in .6.2 with a fresh install via the helm chart. Not sure what else to try at the moment. Let me know if i should open up another ticket
<!-- gh-comment-id:2783943323 -->
@tkg61 commented on GitHub (Apr 7, 2025):
@tjbck Still having issues in .6.2 with a fresh install via the helm chart. Not sure what else to try at the moment. Let me know if i should open up another ticket
@tjbck Still having issues in .6.2 with a fresh install via the helm chart. Not sure what else to try at the moment. Let me know if i should open up another ticket
Can you share a minimal values file without exposing personals to check if you have websockets turned on in your ingress for example
<!-- gh-comment-id:2783966300 -->
@sFritsch09 commented on GitHub (Apr 7, 2025):
> @tjbck Still having issues in .6.2 with a fresh install via the helm chart. Not sure what else to try at the moment. Let me know if i should open up another ticket
>
> 
>
> 
Can you share a minimal values file without exposing personals to check if you have websockets turned on in your ingress for example
@tkg61 did you also set the REDIS_URL environment variable or only the WEBHOOK_REDIS_URL ?
make sure to configure both, then it should work afaik
<!-- gh-comment-id:2784003147 -->
@Classic298 commented on GitHub (Apr 7, 2025):
@tkg61 did you also set the REDIS_URL environment variable or only the WEBHOOK_REDIS_URL ?
make sure to configure both, then it should work afaik
@tkg61 did you also set the REDIS_URL environment variable or only the WEBHOOK_REDIS_URL ?
make sure to configure both, then it should work afaik
Ah, that might be it, i don't see that in the configured envs. Thanks for the clarification. Will make a ticket in the helm repo to update as well.
<!-- gh-comment-id:2784007422 -->
@tkg61 commented on GitHub (Apr 7, 2025):
> [@tkg61](https://github.com/tkg61) did you also set the REDIS_URL environment variable or only the WEBHOOK_REDIS_URL ?
>
> make sure to configure both, then it should work afaik
Ah, that might be it, i don't see that in the configured envs. Thanks for the clarification. Will make a ticket in the helm repo to update as well.
It works! Not sure why we have 2 URLs but it works!
Thanks for the help everyone
<!-- gh-comment-id:2784050405 -->
@tkg61 commented on GitHub (Apr 7, 2025):
It works! Not sure why we have 2 URLs but it works!
Thanks for the help everyone
<!-- gh-comment-id:2787164754 -->
@Classic298 commented on GitHub (Apr 8, 2025):
PR to improve docs to inform users that all these variables need to be set: https://github.com/open-webui/docs/pull/481
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 @OrenZhang on GitHub (Feb 19, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/10365
Originally assigned to: @tjbck on GitHub.
Bug Report
Installation Method
Pod in K8S Cluster
Environment
Description
Bug Summary:
When using open-webui for multi-replica deployment, configuration changes do not take effect across different replicas, possibly due to the settings being loaded into memory. For example, after enabling internet search, querying
/api/v1/retrieval/configoccasionally still showsweb.search.enableas false. The issue is resolved after restarting all the Pods.Reproduction Details
Steps to Reproduce:
@tjbck commented on GitHub (Feb 19, 2025):
Taking a look!
@a517363523 commented on GitHub (Feb 27, 2025):
Has it been fixed? I also encountered this problem
@tkg61 commented on GitHub (Feb 28, 2025):
Not yet, still have it in 5.18
@tjbck commented on GitHub (Mar 6, 2025):
Allocating more resources into resolving this issue, aiming for 0.5.21
@tjbck commented on GitHub (Mar 8, 2025):
Addressed with
d40e696468, Proper redis configuration is required.@tkg61 commented on GitHub (Apr 2, 2025):
@tjbck Still having issues with this in 0.6.0 with redis configured. Settings are not synced between instances. i can just refresh the page and see different banners appear between the instances
@tkg61 commented on GitHub (Apr 7, 2025):
@tjbck Still having issues in .6.2 with a fresh install via the helm chart. Not sure what else to try at the moment. Let me know if i should open up another ticket
@sFritsch09 commented on GitHub (Apr 7, 2025):
Can you share a minimal values file without exposing personals to check if you have websockets turned on in your ingress for example
@Classic298 commented on GitHub (Apr 7, 2025):
@tkg61 did you also set the REDIS_URL environment variable or only the WEBHOOK_REDIS_URL ?
make sure to configure both, then it should work afaik
@tkg61 commented on GitHub (Apr 7, 2025):
Ah, that might be it, i don't see that in the configured envs. Thanks for the clarification. Will make a ticket in the helm repo to update as well.
@tkg61 commented on GitHub (Apr 7, 2025):
It works! Not sure why we have 2 URLs but it works!
Thanks for the help everyone
@Classic298 commented on GitHub (Apr 7, 2025):
Wonderful! Enjoy
@Classic298 commented on GitHub (Apr 8, 2025):
PR to improve docs to inform users that all these variables need to be set: https://github.com/open-webui/docs/pull/481