github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 19:38:46 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #18073] issue: Redis ReadOnlyError with new Open WebUI Version #18481

New Issue
Closed
opened 2026-04-20 00:43:01 -05:00 by GiteaMirror · 12 comments
GiteaMirror commented 2026-04-20 00:43:01 -05:00
Owner
Copy Link

Originally created by @koflerm on GitHub (Oct 6, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18073

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.32

Ollama Version (if applicable)

No response

Operating System

Red Hat CoreOS

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

The Open WebUI instance should automatically be able to decide with redis node is the master using the configured redis sentinel information.

Actual Behavior

When logging in via SSO / OAuth login, an Internal Server Error is returned. The log of the Open WebUI container shows the following error:

[32m2025-10-06 07:40:54.503 | INFO     | uvicorn.protocols.http.httptools_impl:send:476 - 10.161.6.196:0 - "GET /oauth/oidc/login HTTP/1.1" 500
Exception in ASGI application
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/uvicorn/protocols/http/httptools_impl.py", line 409, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 60, in __call__
    return await self.app(scope, receive, send)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/applications.py", line 112, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 187, in __call__
    raise exc
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/lib/python3.11/site-packages/starsessions/middleware.py", line 148, in __call__
    await self.app(scope, receive, send_wrapper)
  File "/usr/local/lib/python3.11/site-packages/starsessions/middleware.py", line 169, in __call__
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/cors.py", line 85, in __call__
    await self.app(scope, receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 177, in __call__
    with recv_stream, send_stream, collapse_excgroups():
  File "/usr/local/lib/python3.11/contextlib.py", line 158, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/usr/local/lib/python3.11/site-packages/starlette/_utils.py", line 82, in collapse_excgroups
    raise exc
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 180, in __call__
    await response(scope, wrapped_receive, send)
  File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 207, in __call__
    await send(
  File "/usr/local/lib/python3.11/site-packages/starsessions/middleware.py", line 128, in send_wrapper
    session_id = await handler.save(remaining_time)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/starsessions/session.py", line 136, in save
    self.session_id = await self.store.write(
                      ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/starsessions/stores/redis.py", line 67, in write
    await self._connection.set(self.prefix(session_id), data, ex=ttl)
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/client.py", line 677, in execute_command
    return await conn.retry.call_with_retry(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/retry.py", line 50, in call_with_retry
    return await do()
           ^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/client.py", line 652, in _send_command_parse_response
    return await self.parse_response(conn, command_name, **options)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/client.py", line 698, in parse_response
    response = await connection.read_response()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 627, in read_response
    raise response from None
redis.exceptions.ReadOnlyError: You can't write against a read only replica.

As background information, we are using the bitnami Redis helm chart to setup a 5 node redis cluster with Sentinel configured. The following environment variables are set in the Open WebUI Instance accordingly:

- name: WEBSOCKET_MANAGER
  value: redis
- name: WEBSOCKET_REDIS_URL
  value: 'redis://open-webui-redis:6379/0'
- name: REDIS_URL
  value: 'redis://open-webui-redis:6379/0'
- name: REDIS_SENTINEL_HOSTS
  value: 'open-webui-redis-node-0.open-webui-redis-headless,open-webui-redis-node-1.open-webui-redis-headless,open-webui-redis-node-2.open-webui-redis-headless,open-webui-redis-node-3.open-webui-redis-headless,open-webui-redis-node-4.open-webui-redis-headless'
- name: WEBSOCKET_SENTINEL_HOSTS
  value: 'open-webui-redis-node-0.open-webui-redis-headless,open-webui-redis-node-1.open-webui-redis-headless,open-webui-redis-node-2.open-webui-redis-headless,open-webui-redis-node-3.open-webui-redis-headless,open-webui-redis-node-4.open-webui-redis-headless'

Here is some additional information to the redis setup:

  • 2 services in Kubernetes exist: open-webui-redis and open-webui-redis-headless, both with the ports 6379 and 26379 configured

For the SSO login, we have configured the following environment variables:

- name: ENABLE_LOGIN_FORM
  value: 'false'
- name: ENABLE_OAUTH_SIGNUP
  value: 'True'
- name: OAUTH_MERGE_ACCOUNTS_BY_EMAIL
  value: 'True'
- name: OAUTH_CLIENT_ID
  value: <our-client-id>
- name: OAUTH_CLIENT_SECRET
  value: <our-secret>
- name: OPENID_PROVIDER_URL
  value: 'https://sso.example.com/.well-known/openid-configuration'
- name: OAUTH_PROVIDER_NAME
  value: SSO
- name: OAUTH_SCOPES
  value: openid email profile
- name: OAUTH_SESSION_TOKEN_ENCRYPTION_KEY
  value: <encryption-key>
- name: OAUTH_USERNAME_CLAIM
  value: given_name

Important to mention is with the old versions, so basically before the OAuth has been reworked we never got those errors so would be interesting if something changed in the Redis config, or if there is a bug in the redis handling in the new oauth code.

Steps to Reproduce

  1. Setup Bitnami Redis Helm Chart with 5 nodes and Sentinel configured
  2. Setup Open WebUI with all other requirements
  3. Configure Redis with Sentinel in the Open WebUI config
  4. Configure OAuth SSO Login in the Open WebUI config
  5. Navigate to the running Open WebUI instance and login to the instance using the "Continue with SSO" login button
  6. "Internal Server Error" is returned

Logs & Screenshots

Relevant logs provided as part of the actual behavior description.

Additional Information

No response

Originally created by @koflerm on GitHub (Oct 6, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18073 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.32 ### Ollama Version (if applicable) _No response_ ### Operating System Red Hat CoreOS ### 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 The Open WebUI instance should automatically be able to decide with redis node is the master using the configured redis sentinel information. ### Actual Behavior When logging in via SSO / OAuth login, an Internal Server Error is returned. The log of the Open WebUI container shows the following error: ``` [32m2025-10-06 07:40:54.503 | INFO  | uvicorn.protocols.http.httptools_impl:send:476 - 10.161.6.196:0 - "GET /oauth/oidc/login HTTP/1.1" 500 Exception in ASGI application Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/uvicorn/protocols/http/httptools_impl.py", line 409, in run_asgi result = await app( # type: ignore[func-returns-value] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 60, in __call__ return await self.app(scope, receive, send) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in __call__ await super().__call__(scope, receive, send) File "/usr/local/lib/python3.11/site-packages/starlette/applications.py", line 112, in __call__ await self.middleware_stack(scope, receive, send) File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 187, in __call__ raise exc File "/usr/local/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in __call__ await self.app(scope, receive, _send) File "/usr/local/lib/python3.11/site-packages/starsessions/middleware.py", line 148, in __call__ await self.app(scope, receive, send_wrapper) File "/usr/local/lib/python3.11/site-packages/starsessions/middleware.py", line 169, in __call__ await self.app(scope, receive, send) File "/usr/local/lib/python3.11/site-packages/starlette/middleware/cors.py", line 85, in __call__ await self.app(scope, receive, send) File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 177, in __call__ with recv_stream, send_stream, collapse_excgroups(): File "/usr/local/lib/python3.11/contextlib.py", line 158, in __exit__ self.gen.throw(typ, value, traceback) File "/usr/local/lib/python3.11/site-packages/starlette/_utils.py", line 82, in collapse_excgroups raise exc File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 180, in __call__ await response(scope, wrapped_receive, send) File "/usr/local/lib/python3.11/site-packages/starlette/middleware/base.py", line 207, in __call__ await send( File "/usr/local/lib/python3.11/site-packages/starsessions/middleware.py", line 128, in send_wrapper session_id = await handler.save(remaining_time) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/starsessions/session.py", line 136, in save self.session_id = await self.store.write( ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/starsessions/stores/redis.py", line 67, in write await self._connection.set(self.prefix(session_id), data, ex=ttl) File "/usr/local/lib/python3.11/site-packages/redis/asyncio/client.py", line 677, in execute_command return await conn.retry.call_with_retry( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/redis/asyncio/retry.py", line 50, in call_with_retry return await do() ^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/redis/asyncio/client.py", line 652, in _send_command_parse_response return await self.parse_response(conn, command_name, **options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/redis/asyncio/client.py", line 698, in parse_response response = await connection.read_response() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 627, in read_response raise response from None redis.exceptions.ReadOnlyError: You can't write against a read only replica. ``` As background information, we are using the bitnami Redis helm chart to setup a 5 node redis cluster with Sentinel configured. The following environment variables are set in the Open WebUI Instance accordingly: ``` - name: WEBSOCKET_MANAGER value: redis - name: WEBSOCKET_REDIS_URL value: 'redis://open-webui-redis:6379/0' - name: REDIS_URL value: 'redis://open-webui-redis:6379/0' - name: REDIS_SENTINEL_HOSTS value: 'open-webui-redis-node-0.open-webui-redis-headless,open-webui-redis-node-1.open-webui-redis-headless,open-webui-redis-node-2.open-webui-redis-headless,open-webui-redis-node-3.open-webui-redis-headless,open-webui-redis-node-4.open-webui-redis-headless' - name: WEBSOCKET_SENTINEL_HOSTS value: 'open-webui-redis-node-0.open-webui-redis-headless,open-webui-redis-node-1.open-webui-redis-headless,open-webui-redis-node-2.open-webui-redis-headless,open-webui-redis-node-3.open-webui-redis-headless,open-webui-redis-node-4.open-webui-redis-headless' ``` Here is some additional information to the redis setup: - 2 services in Kubernetes exist: open-webui-redis and open-webui-redis-headless, both with the ports 6379 and 26379 configured For the SSO login, we have configured the following environment variables: ``` - name: ENABLE_LOGIN_FORM value: 'false' - name: ENABLE_OAUTH_SIGNUP value: 'True' - name: OAUTH_MERGE_ACCOUNTS_BY_EMAIL value: 'True' - name: OAUTH_CLIENT_ID value: <our-client-id> - name: OAUTH_CLIENT_SECRET value: <our-secret> - name: OPENID_PROVIDER_URL value: 'https://sso.example.com/.well-known/openid-configuration' - name: OAUTH_PROVIDER_NAME value: SSO - name: OAUTH_SCOPES value: openid email profile - name: OAUTH_SESSION_TOKEN_ENCRYPTION_KEY value: <encryption-key> - name: OAUTH_USERNAME_CLAIM value: given_name ``` Important to mention is with the old versions, so basically before the OAuth has been reworked we never got those errors so would be interesting if something changed in the Redis config, or if there is a bug in the redis handling in the new oauth code. ### Steps to Reproduce 1. Setup Bitnami Redis Helm Chart with 5 nodes and Sentinel configured 2. Setup Open WebUI with all other requirements 3. Configure Redis with Sentinel in the Open WebUI config 4. Configure OAuth SSO Login in the Open WebUI config 5. Navigate to the running Open WebUI instance and login to the instance using the "Continue with SSO" login button 6. "Internal Server Error" is returned ### Logs & Screenshots Relevant logs provided as part of the actual behavior description. ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-20 00:43:01 -05:00
GiteaMirror commented 2026-04-20 00:43:03 -05:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (Oct 6, 2025):

The error occurs in the starsessions middleware when it attempts to save session data.
The session middleware is using a direct Redis connection that doesn't have Sentinel failover support, so when it connects to a read-only replica, write operations fail.

Suggested changes:
Modify backend/open_webui/main.py to pass a Sentinel-aware Redis connection to the RedisStore instead of just the URL,
change
3f71fa641f/backend/open_webui/main.py (L1941-L1946)
by

from open_webui.utils.redis import get_redis_connection, get_sentinels_from_env
...
try:
    if REDIS_URL:
        # Get Sentinel-aware Redis connection
        redis_connection = get_redis_connection(
            redis_url=REDIS_URL,
            redis_sentinels=get_sentinels_from_env(
                REDIS_SENTINEL_HOSTS, REDIS_SENTINEL_PORT
            ),
            redis_cluster=REDIS_CLUSTER,
            async_mode=True,
            decode_responses=True,
        )
          
        # Pass the connection object instead of URL
        redis_session_store = RedisStore(
            client=redis_connection,
            prefix=(f"{REDIS_KEY_PREFIX}:session:" if REDIS_KEY_PREFIX else "session:"),
        )

By passing the client parameter with a connection from get_redis_connection(), we ensure the session store uses the SentinelRedisProxy wrapper that catches ReadOnlyError and retries operations after Sentinel discovers the new master.

(I can't test it as I'm not using sentinel hosts)

<!-- gh-comment-id:3370659836 --> @rgaricano commented on GitHub (Oct 6, 2025): The error occurs in the starsessions middleware when it attempts to save session data. The session middleware is using a direct Redis connection that doesn't have Sentinel failover support, so when it connects to a read-only replica, write operations fail. Suggested changes: Modify backend/open_webui/main.py to pass a Sentinel-aware Redis connection to the RedisStore instead of just the URL, change https://github.com/open-webui/open-webui/blob/3f71fa641ffd3851999cdb3f3a7ea2793f437f45/backend/open_webui/main.py#L1941-L1946 by ``` from open_webui.utils.redis import get_redis_connection, get_sentinels_from_env ... try: if REDIS_URL: # Get Sentinel-aware Redis connection redis_connection = get_redis_connection( redis_url=REDIS_URL, redis_sentinels=get_sentinels_from_env( REDIS_SENTINEL_HOSTS, REDIS_SENTINEL_PORT ), redis_cluster=REDIS_CLUSTER, async_mode=True, decode_responses=True, ) # Pass the connection object instead of URL redis_session_store = RedisStore( client=redis_connection, prefix=(f"{REDIS_KEY_PREFIX}:session:" if REDIS_KEY_PREFIX else "session:"), ) ``` By passing the client parameter with a connection from get_redis_connection(), we ensure the session store uses the SentinelRedisProxy wrapper that catches ReadOnlyError and retries operations after Sentinel discovers the new master. (I can't test it as I'm not using sentinel hosts)
GiteaMirror commented 2026-04-20 00:43:03 -05:00
Author
Owner
Copy Link

@Ithanil commented on GitHub (Oct 6, 2025):

Sorry for not opening an issue already, but this is discussed herem including a fix: https://github.com/open-webui/open-webui/pull/17223#issuecomment-3355502421

Nevertheless, I can't verify that Starsessions is actually using Redis at all.

<!-- gh-comment-id:3370779236 --> @Ithanil commented on GitHub (Oct 6, 2025): Sorry for not opening an issue already, but this is discussed herem including a fix: https://github.com/open-webui/open-webui/pull/17223#issuecomment-3355502421 Nevertheless, I can't verify that Starsessions is actually using Redis at all.
GiteaMirror commented 2026-04-20 00:43:03 -05:00
Author
Owner
Copy Link

@koflerm commented on GitHub (Oct 7, 2025):

Thanks guys for the quick response! If I read the discussion correctly @rgaricano you are still working on trying to get the proposed code running which includes the Redis Sentinel Handling?

<!-- gh-comment-id:3375661461 --> @koflerm commented on GitHub (Oct 7, 2025): Thanks guys for the quick response! If I read the discussion correctly @rgaricano you are still working on trying to get the proposed code running which includes the Redis Sentinel Handling?
GiteaMirror commented 2026-04-20 00:43:04 -05:00
Author
Owner
Copy Link

@Ithanil commented on GitHub (Oct 7, 2025):

@koflerm If you want a quick fix, just change 4d7fddaf7e/backend/open_webui/main.py (L1912) to if False: to avoid using Starsessions.

The proposed code does run per se, the remaining question is how to get Starsessions to actually behave as expected.

<!-- gh-comment-id:3375673894 --> @Ithanil commented on GitHub (Oct 7, 2025): @koflerm If you want a quick fix, just change https://github.com/open-webui/open-webui/blob/4d7fddaf7e434bf59fdd879ef11d712a503b7863/backend/open_webui/main.py#L1912 to `if False:` to avoid using Starsessions. The proposed code does run per se, the remaining question is how to get Starsessions to actually behave as expected.
GiteaMirror commented 2026-04-20 00:43:04 -05:00
Author
Owner
Copy Link

@koflerm commented on GitHub (Oct 7, 2025):

@Ithanil this essentially means same as not setting REDIS_URL so with this redis is not used at all for session management, correct?

<!-- gh-comment-id:3375692623 --> @koflerm commented on GitHub (Oct 7, 2025): @Ithanil this essentially means same as not setting REDIS_URL so with this redis is not used at all for session management, correct?
GiteaMirror commented 2026-04-20 00:43:05 -05:00
Author
Owner
Copy Link

@Ithanil commented on GitHub (Oct 7, 2025):

@Ithanil this essentially means same as not setting REDIS_URL so with this redis is not used at all for session management, correct?

No, not setting REDIS_URL at all would have far more effects. This here is just about whether session data is stored in cookie or in Redis. If Open WebUI worked fine for you before this change, just revert to the old system as proposed.

<!-- gh-comment-id:3375707777 --> @Ithanil commented on GitHub (Oct 7, 2025): > [@Ithanil](https://github.com/Ithanil) this essentially means same as not setting REDIS_URL so with this redis is not used at all for session management, correct? No, not setting REDIS_URL at all would have far more effects. This here is just about whether session data is stored in cookie or in Redis. If Open WebUI worked fine for you before this change, just revert to the old system as proposed.
GiteaMirror commented 2026-04-20 00:43:05 -05:00
Author
Owner
Copy Link

@koflerm commented on GitHub (Oct 7, 2025):

@Ithanil All right thanks for the clarification then I guess we have to wait for this issue to be fixed before upgrading our prod instance. Appreciate the help!

<!-- gh-comment-id:3375791078 --> @koflerm commented on GitHub (Oct 7, 2025): @Ithanil All right thanks for the clarification then I guess we have to wait for this issue to be fixed before upgrading our prod instance. Appreciate the help!
GiteaMirror commented 2026-04-20 00:43:06 -05:00
Author
Owner
Copy Link

@Alwinator commented on GitHub (Oct 7, 2025):

@Ithanil @rgaricano Could you kindly share if there’s an estimated timeframe for resolving this issue? We seem to be encountering the same challenge and truly appreciate all the hard work being put into this project.

<!-- gh-comment-id:3375809937 --> @Alwinator commented on GitHub (Oct 7, 2025): @Ithanil @rgaricano Could you kindly share if there’s an estimated timeframe for resolving this issue? We seem to be encountering the same challenge and truly appreciate all the hard work being put into this project.
GiteaMirror commented 2026-04-20 00:43:06 -05:00
Author
Owner
Copy Link

@Ithanil commented on GitHub (Oct 7, 2025):

Just for clarification, I'm just a regular contributor, so I can't comment on this.

But regardless I would always recommend deploying your own image builds of open source projects, so you can actually take advantage of the openness by applying hotfixes yourself. It's a one-line fix.

<!-- gh-comment-id:3375822466 --> @Ithanil commented on GitHub (Oct 7, 2025): Just for clarification, I'm just a regular contributor, so I can't comment on this. But regardless I would *always* recommend deploying your own image builds of open source projects, so you can actually take advantage of the openness by applying hotfixes yourself. It's a one-line fix.
GiteaMirror commented 2026-04-20 00:43:07 -05:00
Author
Owner
Copy Link

@rgaricano commented on GitHub (Oct 7, 2025):

same as Ithanil,
by the way, yesterday I was the whole day trying to debug the recent added startsessions with redis, without success. As it is It seems like it could cause more problems than benefits. I think that right now the best solution is revert PR https://github.com/open-webui/open-webui/pull/17223 until it is verified to work correctly in all redis configurations.

<!-- gh-comment-id:3375933406 --> @rgaricano commented on GitHub (Oct 7, 2025): same as Ithanil, by the way, yesterday I was the whole day trying to debug the recent added startsessions with redis, without success. As it is It seems like it could cause more problems than benefits. I think that right now the best solution is revert PR https://github.com/open-webui/open-webui/pull/17223 until it is verified to work correctly in all redis configurations.
GiteaMirror commented 2026-04-20 00:43:07 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 7, 2025):

Should be addressed in dev with 861953fd2d.

<!-- gh-comment-id:3377530448 --> @tjbck commented on GitHub (Oct 7, 2025): Should be addressed in dev with 861953fd2d48f73f9187b58afa0164e9ad3aad75.
GiteaMirror commented 2026-04-20 00:43:07 -05:00
Author
Owner
Copy Link

@koflerm commented on GitHub (Oct 7, 2025):

Great then with this we should be able to move on as soon as a new release is available. Thanks guys for the quick support!

<!-- gh-comment-id:3377756296 --> @koflerm commented on GitHub (Oct 7, 2025): Great then with this we should be able to move on as soon as a new release is available. Thanks guys for the quick support!
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#18481
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?