From 095e88f79603340ed93454e432a87871b3286393 Mon Sep 17 00:00:00 2001 From: silentoplayz Date: Sat, 8 Nov 2025 16:12:10 -0500 Subject: [PATCH] docs: Mention CORS_ALLOW_ORIGIN in Redis documentation Adds a tip to the Redis integration documentation to mention the necessity of `CORS_ALLOW_ORIGIN` for WebSocket connections. This is a common issue that can be difficult to debug. --- docs/tutorials/integrations/redis.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/tutorials/integrations/redis.md b/docs/tutorials/integrations/redis.md index 5e0a191de..53a51eccd 100644 --- a/docs/tutorials/integrations/redis.md +++ b/docs/tutorials/integrations/redis.md @@ -142,6 +142,20 @@ WEBSOCKET_MANAGER="redis" WEBSOCKET_REDIS_URL="redis://redis-valkey:6379/1" ``` +:::tip + +For WebSocket connections to work correctly, especially when your Open WebUI instance is accessed from a different domain, you must also configure the `CORS_ALLOW_ORIGIN` environment variable. This variable tells the server which origins are permitted to access its resources. + +For example, if you access Open WebUI from `https://my-open-webui.com`, you should set: + +```bash +CORS_ALLOW_ORIGIN="https://my-open-webui.com" +``` + +Forgetting to set this variable is a common cause of WebSocket connection issues. You can also provide a semicolon-separated list of origins. + +::: + :::info **Redis Database Numbers**