[GH-ISSUE #12005] issue: Activated Memory feature leads to OpenWebUI crash 500: Internal Error (v0.5.20 and older versions) #31963

New Issue

GiteaMirror · 2026-04-25T05:51:09-05:00

GiteaMirror commented

2026-04-25 05:51:09 -05:00

Originally created by @deliciousbob on GitHub (Mar 24, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12005

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

v0.5.20

Ollama Version (if applicable)

LiteLLM as AI-Gateway

Operating System

Docker Container on Ubuntu 22.04

Browser (if applicable)

Chrome

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 listed steps to reproduce the bug in detail.

Expected Behavior

Just activated the Memory feature, and got a "Socket undefined disconnected due to ping timeout"
OpenWebUI is not reacting to any request after that, whole page goes down.

Actual Behavior

Just activated the Memory feature, and got a "Socket undefined disconnected due to ping timeout"
OpenWebUI is not reacting to any request after that, whole page goes down.

Steps to Reproduce

After several weeks of OpenWebUI got unresponsive for no reasons (no log entry for a timeout)
We now identified some users used the Memory feature causing the whole OpenWebUI to crash and not responding to any requests / site is not accesible anymore (500: Internal Error).

How to reproduce:

Goto User -> Settings -> Personalization -> Memory = ON (have not added any memory manually)
Open a new Chat -> ask anything
Chat is loading but not no respond is showing.
Checked the Console Logs -> Socket undefined disconnected due to ping timeout
Full container gets unresponsive -> OpenWebUI is not accessable anymore.
Reloading the page leads to long loading followed by 500 ERROR

Restart the Docker container, everything works again

Disbale the Memory feature = everything works fine as expected
Enable the Memory feature = instant crash of OpenWebUI

Is there an option to disable Memory-Feature globally for all users?
This would be a quick temporary fix, but i did not find any Environment Variable or Admin setting for that.

Thank you for your help!

Logs & Screenshots

The Docker container logs only show the last connections before the timeout.

Additional Information

We have theses issues since several weeks / months. We always updated to the latest version when available.
But it did not help, we first thought it was caused by LiteLLM getting too many requests.

Originally created by @deliciousbob on GitHub (Mar 24, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/12005 ### 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 v0.5.20 ### Ollama Version (if applicable) LiteLLM as AI-Gateway ### Operating System Docker Container on Ubuntu 22.04 ### Browser (if applicable) Chrome ### 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 Just activated the Memory feature, and got a "Socket undefined disconnected due to ping timeout" OpenWebUI is not reacting to any request after that, whole page goes down. ### Actual Behavior Just activated the Memory feature, and got a "Socket undefined disconnected due to ping timeout" OpenWebUI is not reacting to any request after that, whole page goes down. ### Steps to Reproduce After **several weeks of OpenWebUI** got unresponsive for no reasons (no log entry for a timeout) We now identified some users used the Memory feature causing the whole OpenWebUI to crash and not responding to any requests / site is not accesible anymore (500: Internal Error). How to reproduce: 1. Goto User -> **Settings** -> **Personalization** -> **Memory** = ON (have not added any memory manually) 3. Open a new Chat -> ask anything 4. Chat is loading but not no respond is showing. 5. Checked the Console Logs -> _Socket undefined disconnected due to ping timeout_ 6. Full container gets unresponsive -> OpenWebUI is not accessable anymore. 7. Reloading the page leads to long loading followed by 500 ERROR ### **Restart the Docker container, everything works again** Disbale the Memory feature = everything works fine as expected Enable the Memory feature = instant crash of OpenWebUI Is there an option to disable Memory-Feature globally for all users? This would be a quick temporary fix, but i did not find any Environment Variable or Admin setting for that. Thank you for your help! ### Logs & Screenshots The Docker container logs only show the last connections before the timeout. ### Additional Information We have theses issues since several weeks / months. We always updated to the latest version when available. But it did not help, we first thought it was caused by LiteLLM getting too many requests.

GiteaMirror added the bug label 2026-04-25 05:51:09 -05:00

GiteaMirror closed this issue

2026-04-25 05:51:11 -05:00

GiteaMirror commented

2026-04-25 05:51:12 -05:00

@tjbck commented on GitHub (Mar 24, 2025):

Could you confirm you can reproduce this issue without LiteLLM as well?

@tjbck commented on GitHub (Mar 24, 2025): Could you confirm you can reproduce this issue without LiteLLM as well?

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#31963