Originally created by @taylorwilsdon on GitHub (Jun 17, 2025).
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.15
Ollama Version (if applicable)
No response
Operating System
Ubuntu
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
Configuring redis maintains state for application config and orchestrates tasks and websockets.
Actual Behavior
Steps to Reproduce
Configure Open WebUI with websockets enabled and point at a cluster mode or serverless Redis engine 8 compatible instance:
{
name = "ENABLE_WEBSOCKET_SUPPORT"
value = "true"
},
{
name = "REDIS_URL"
value = "rediss://myinstance.serverless.usw2.cache.amazonaws.com:6379/0"
},
{
name = "WEBSOCKET_REDIS_URL"
value = "rediss://myinstance.serverless.usw2.cache.amazonaws.com:6379/0"
},
{
name = "WEBSOCKET_MANAGER"
value = "redis"
}
Logs & Screenshots
Additional Information
There is a relatively simple fix that should just drop in without issue:
just adding {open-webui}: prefix to existing key patterns (ie {open-webui}:config:* instead of open-webui:config:* will allow multi-key operations work for config keys when operating in cluster mode.
ifisinstance(value,PersistentConfig):self._state[key]=valueelse:self._state[key].value=valueself._state[key].save()ifself._redis:redis_key=f"open-webui:config:{key}"self._redis.set(redis_key,json.dumps(self._state[key].value))def__getattr__(self,key):ifkeynotinself._state:raiseAttributeError(f"Config key '{key}' not found")#IfRedisisavailable,checkforanupdatedvalueifself._redis:redis_key=f"open-webui:config:{key}"redis_value=self._redis.get(redis_key)
Originally created by @taylorwilsdon on GitHub (Jun 17, 2025).
### 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.15
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu
### 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
Configuring redis maintains state for application config and orchestrates tasks and websockets.
### Actual Behavior
<img width="958" alt="Image" src="https://github.com/user-attachments/assets/98b86317-b597-4575-8a73-e6f649cc7114" />
### Steps to Reproduce
Configure Open WebUI with websockets enabled and point at a cluster mode or serverless Redis engine 8 compatible instance:
```
{
name = "ENABLE_WEBSOCKET_SUPPORT"
value = "true"
},
{
name = "REDIS_URL"
value = "rediss://myinstance.serverless.usw2.cache.amazonaws.com:6379/0"
},
{
name = "WEBSOCKET_REDIS_URL"
value = "rediss://myinstance.serverless.usw2.cache.amazonaws.com:6379/0"
},
{
name = "WEBSOCKET_MANAGER"
value = "redis"
}
```
### Logs & Screenshots
<img width="956" alt="Image" src="https://github.com/user-attachments/assets/9c08ea84-f882-4b70-a292-d5a99d74a72e" />
### Additional Information
There is a relatively simple fix that should just drop in without issue:
just adding `{open-webui}:` prefix to existing key patterns (ie `{open-webui}:config:*` instead of `open-webui:config:*` will allow multi-key operations work for config keys when operating in cluster mode.
``` def __setattr__(self, key, value):
if isinstance(value, PersistentConfig):
self._state[key] = value
else:
self._state[key].value = value
self._state[key].save()
if self._redis:
redis_key = f"open-webui:config:{key}"
self._redis.set(redis_key, json.dumps(self._state[key].value))
def __getattr__(self, key):
if key not in self._state:
raise AttributeError(f"Config key '{key}' not found")
# If Redis is available, check for an updated value
if self._redis:
redis_key = f"open-webui:config:{key}"
redis_value = self._redis.get(redis_key)
```
GiteaMirror
added the bug label 2025-11-11 16:24:43 -06:00
@taylorwilsdon commented on GitHub (Jun 17, 2025):
Hey @tjbck I can push up a fix but wanted to check with you first which approach you'd prefer:
Direct rename (ie just update the fstring in the code there)
Configurable as env var (ie REDIS_KEY_PREFIX) so that those who don't care can use as-is and those who need cluster mode can drop in {open-webui}:config:
@taylorwilsdon commented on GitHub (Jun 17, 2025):
Hey @tjbck I can push up a fix but wanted to check with you first which approach you'd prefer:
* Direct rename (ie just update the fstring in the code there)
* Configurable as env var (ie `REDIS_KEY_PREFIX`) so that those who don't care can use as-is and those who need cluster mode can drop in `{open-webui}:config:`
Similar error happens on a kubernetes with multiple instances of the docker image, the chats throws
Since version 6.1.4, i tracked the error to this code
backend/open_webui/tasks.py
at the beginnig of the file they define the prefix but they are hardcoded no readed from enviroment variables
@srdosramos commented on GitHub (Jun 26, 2025):
Similar error happens on a kubernetes with multiple instances of the docker image, the chats throws

Since version 6.1.4, i tracked the error to this code

backend/open_webui/tasks.py
at the beginnig of the file they define the prefix but they are hardcoded no readed from enviroment variables

@taylorwilsdon commented on GitHub (Jun 28, 2025):
ok - PR up @ https://github.com/open-webui/open-webui/pull/15380
@IgorFZ or @srdosramos let me know if this resolves your issues!
Hi, I upgraded to the latest Docker image v0.6.16, but I still got this error message. Do I need to change any configuration after the upgrade?
@davidshen84 commented on GitHub (Jul 18, 2025):
Hi, I upgraded to the latest Docker image v0.6.16, but I still got this error message. Do I need to change any configuration after the upgrade?
@taylorwilsdon commented on GitHub (Jul 18, 2025):
Hi, I upgraded to the latest Docker image v0.6.16, but I still got this error message. Do I need to change any configuration after the upgrade?
By default, the PR introduces the ability to change the key - it doesn't actually change it unless you set the env var
Setting env REDIS_KEY_PREFIX to {open-webui} should be your solve if the issue was the same as mine (cluster mode redis)
@taylorwilsdon commented on GitHub (Jul 18, 2025):
> Hi, I upgraded to the latest Docker image v0.6.16, but I still got this error message. Do I need to change any configuration after the upgrade?
By default, the PR introduces the ability to change the key - it doesn't actually change it unless you set the env var
Setting env REDIS_KEY_PREFIX to `{open-webui}` should be your solve if the issue was the same as mine (cluster mode redis)
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 @taylorwilsdon on GitHub (Jun 17, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.15
Ollama Version (if applicable)
No response
Operating System
Ubuntu
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Configuring redis maintains state for application config and orchestrates tasks and websockets.
Actual Behavior
Steps to Reproduce
Configure Open WebUI with websockets enabled and point at a cluster mode or serverless Redis engine 8 compatible instance:
Logs & Screenshots
Additional Information
There is a relatively simple fix that should just drop in without issue:
just adding
{open-webui}:prefix to existing key patterns (ie{open-webui}:config:*instead ofopen-webui:config:*will allow multi-key operations work for config keys when operating in cluster mode.@taylorwilsdon commented on GitHub (Jun 17, 2025):
Hey @tjbck I can push up a fix but wanted to check with you first which approach you'd prefer:
REDIS_KEY_PREFIX) so that those who don't care can use as-is and those who need cluster mode can drop in{open-webui}:config:@tjbck commented on GitHub (Jun 18, 2025):
REDIS_KEY_PREFIXsounds reasonable, PR welcome!@srdosramos commented on GitHub (Jun 26, 2025):
Similar error happens on a kubernetes with multiple instances of the docker image, the chats throws
Since version 6.1.4, i tracked the error to this code
backend/open_webui/tasks.py
at the beginnig of the file they define the prefix but they are hardcoded no readed from enviroment variables
@IgorFZ commented on GitHub (Jun 27, 2025):
Same error here, version 0.6.15:
@taylorwilsdon commented on GitHub (Jun 28, 2025):
ok - PR up @ https://github.com/open-webui/open-webui/pull/15380
@IgorFZ or @srdosramos let me know if this resolves your issues!
@davidshen84 commented on GitHub (Jul 18, 2025):
Hi, I upgraded to the latest Docker image v0.6.16, but I still got this error message. Do I need to change any configuration after the upgrade?
@taylorwilsdon commented on GitHub (Jul 18, 2025):
By default, the PR introduces the ability to change the key - it doesn't actually change it unless you set the env var
Setting env REDIS_KEY_PREFIX to
{open-webui}should be your solve if the issue was the same as mine (cluster mode redis)