[GH-ISSUE #23449] issue: SOS - I'm completely stuck and desperately need help! I've been trying to fix this for hours with no success. Please help me! #58652

Closed
opened 2026-05-05 23:38:05 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @teddy911405 on GitHub (Apr 6, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23449

https://ibb.co/0VBc2hrz
https://ibb.co/dsHL6dcH

Check Existing

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.16

Ollama Version (if applicable)

No response

Operating System

Ubuntu 22.04.5 LTS

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

Running docker stop open-webui && docker rm open-webui should completely stop and remove the Open WebUI container, freeing port 8080.

Actual Behavior

After docker rm, the container disappears from docker ps -a, but port 8080 remains occupied by a Python/uvicorn process. The process is a ghost container running at the containerd level (containerd-shim-runc-v2) that auto-restarts every time it is killed.

Steps to Reproduce

  1. Install Open WebUI using Docker with --restart always flag on WSL2 (Ubuntu 22.04)
  2. Run: sudo docker stop open-webui && sudo docker rm open-webui
  3. Check docker ps -a — container is gone
  4. Check sudo ss -tlnp | grep 8080 — port still occupied by python3/uvicorn
  5. Check ps -ef — shows containerd-shim-runc-v2 still running with old container ID
  6. Attempt sudo kill -9 — process auto-restarts immediately

Logs & Screenshots

$ sudo ss -tlnp | grep 8080
LISTEN 0 2048 0.0.0.0:8080 0.0.0.0:* users=(("python3",pid=5404,fd=20))

$ ps -ef | grep containerd-shim
root 5382 1 0 17:27 ? /usr/bin/containerd-shim-runc-v2 -namespace moby -id 60c5708762c65d740ca25e5a5339398aca9617c5180f0808d1f1c0ce2f872682 -address /run/containerd/containerd.sock

$ sudo ctr -n moby containers rm 60c5708762c6...
Error: cannot delete a non stopped container

Additional Information

  • Running on WSL2 (Windows 11)
  • The original container was started with --gpus all --restart always
  • sudo pip3 show open-webui returns "not installed" but the process is clearly running
  • wsl --shutdown and restarting WSL did not resolve the issue
  • sudo systemctl restart docker did not resolve the issue

🆘 SOS - I'm completely stuck and desperately need help! I've been trying to fix this for hours with no success. Please help me!


[HELP] Open WebUI ghost container stuck in containerd - docker ps -a shows nothing but service still running

Environment

  • OS: Ubuntu 22.04.5 LTS (WSL2)
  • Docker CE: 5:28.3.2
  • Host: Windows 11

Problem Description

I originally installed Open WebUI using Docker with the following command:

sudo docker run -d --network=host --gpus all \
  -v open-webui:/app/backend/data \
  -e OLLAMA_BASE_URL=http://127.0.0.1:11434 \
  -e WEBUI_SECRET_KEY=mysecretkey123 \
  --name open-webui --restart always \
  ghcr.io/open-webui/open-webui:cuda

I later tried to update by running docker stop open-webui && docker rm open-webui. After that, docker ps -a shows no open-webui container, but http://127.0.0.1:8080 is still accessible and working!

Investigation

Checking port 8080:

$ sudo ss -tlnp | grep 8080
LISTEN 0  2048  0.0.0.0:8080  0.0.0.0:*  users=(("python3",pid=5404,fd=20))

Tracing the parent process:

$ ps -ef | grep 5382
root  5382  1  0  17:27  ?  /usr/bin/containerd-shim-runc-v2 \
  -namespace moby \
  -id 60c5708762c65d740ca25e5a5339398aca9617c5180f0808d1f1c0ce2f872682 \
  -address /run/containerd/containerd.sock

I found a ghost container at the containerd level (container ID: 60c5708762c6). Docker no longer recognizes it, but containerd keeps it running and auto-restarts it every time I kill the process.

What I've Already Tried (All Failed)

  • sudo kill -9 <pid> → process auto-restarts immediately
  • sudo systemctl restart docker → process reappears after restart
  • sudo ctr -n moby tasks kill <id> → process still revives
  • sudo ctr -n moby containers rm <id> → Error: cannot delete a non stopped container
  • sudo ctr -n moby tasks delete --force <id> → Error: cannot delete a deleted process: not found
  • sudo pkill -9 -f open_webui → process auto-restarts
  • wsl --shutdown then reopen WSL → process still appears
  • sudo pip3 uninstall open-webui → WARNING: open-webui is not installed
  • sudo pip3 show open-webui → Package not found (but process is clearly still running as root via uvicorn!)

Questions

  1. How can I completely remove this ghost container from the containerd layer?
  2. Why does containerd keep restarting the container even after docker rm?
  3. Is there a way to locate and delete the Open WebUI Python installation files? (pip3 show says not installed but the process is clearly running as root via uvicorn)

Any help is appreciated. Thank you so much! 🙏

Originally created by @teddy911405 on GitHub (Apr 6, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23449 [https://ibb.co/0VBc2hrz](url) [https://ibb.co/dsHL6dcH](url) ### Check Existing - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.16 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 22.04.5 LTS ### 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 Running `docker stop open-webui && docker rm open-webui` should completely stop and remove the Open WebUI container, freeing port 8080. ### Actual Behavior After `docker rm`, the container disappears from `docker ps -a`, but port 8080 remains occupied by a Python/uvicorn process. The process is a ghost container running at the containerd level (containerd-shim-runc-v2) that auto-restarts every time it is killed. ### Steps to Reproduce 1. Install Open WebUI using Docker with --restart always flag on WSL2 (Ubuntu 22.04) 2. Run: sudo docker stop open-webui && sudo docker rm open-webui 3. Check docker ps -a — container is gone 4. Check sudo ss -tlnp | grep 8080 — port still occupied by python3/uvicorn 5. Check ps -ef — shows containerd-shim-runc-v2 still running with old container ID 6. Attempt sudo kill -9 <pid> — process auto-restarts immediately ### Logs & Screenshots $ sudo ss -tlnp | grep 8080 LISTEN 0 2048 0.0.0.0:8080 0.0.0.0:* users=(("python3",pid=5404,fd=20)) $ ps -ef | grep containerd-shim root 5382 1 0 17:27 ? /usr/bin/containerd-shim-runc-v2 -namespace moby -id 60c5708762c65d740ca25e5a5339398aca9617c5180f0808d1f1c0ce2f872682 -address /run/containerd/containerd.sock $ sudo ctr -n moby containers rm 60c5708762c6... Error: cannot delete a non stopped container ### Additional Information - Running on WSL2 (Windows 11) - The original container was started with --gpus all --restart always - sudo pip3 show open-webui returns "not installed" but the process is clearly running - wsl --shutdown and restarting WSL did not resolve the issue - sudo systemctl restart docker did not resolve the issue 🆘 SOS - I'm completely stuck and desperately need help! I've been trying to fix this for hours with no success. Please help me! --- [HELP] Open WebUI ghost container stuck in containerd - docker ps -a shows nothing but service still running ## Environment - OS: Ubuntu 22.04.5 LTS (WSL2) - Docker CE: 5:28.3.2 - Host: Windows 11 ## Problem Description I originally installed Open WebUI using Docker with the following command: ``` sudo docker run -d --network=host --gpus all \ -v open-webui:/app/backend/data \ -e OLLAMA_BASE_URL=http://127.0.0.1:11434 \ -e WEBUI_SECRET_KEY=mysecretkey123 \ --name open-webui --restart always \ ghcr.io/open-webui/open-webui:cuda ``` I later tried to update by running `docker stop open-webui && docker rm open-webui`. After that, `docker ps -a` shows no open-webui container, but http://127.0.0.1:8080 is still accessible and working! ## Investigation Checking port 8080: ``` $ sudo ss -tlnp | grep 8080 LISTEN 0 2048 0.0.0.0:8080 0.0.0.0:* users=(("python3",pid=5404,fd=20)) ``` Tracing the parent process: ``` $ ps -ef | grep 5382 root 5382 1 0 17:27 ? /usr/bin/containerd-shim-runc-v2 \ -namespace moby \ -id 60c5708762c65d740ca25e5a5339398aca9617c5180f0808d1f1c0ce2f872682 \ -address /run/containerd/containerd.sock ``` I found a **ghost container at the containerd level** (container ID: `60c5708762c6`). Docker no longer recognizes it, but containerd keeps it running and auto-restarts it every time I kill the process. ## What I've Already Tried (All Failed) - `sudo kill -9 <pid>` → process auto-restarts immediately - `sudo systemctl restart docker` → process reappears after restart - `sudo ctr -n moby tasks kill <id>` → process still revives - `sudo ctr -n moby containers rm <id>` → Error: cannot delete a non stopped container - `sudo ctr -n moby tasks delete --force <id>` → Error: cannot delete a deleted process: not found - `sudo pkill -9 -f open_webui` → process auto-restarts - `wsl --shutdown` then reopen WSL → process still appears - `sudo pip3 uninstall open-webui` → WARNING: open-webui is not installed - `sudo pip3 show open-webui` → Package not found (but process is clearly still running as root via uvicorn!) ## Questions 1. How can I completely remove this ghost container from the containerd layer? 2. Why does containerd keep restarting the container even after `docker rm`? 3. Is there a way to locate and delete the Open WebUI Python installation files? (`pip3 show` says not installed but the process is clearly running as root via uvicorn) Any help is appreciated. Thank you so much! 🙏
GiteaMirror added the bug label 2026-05-05 23:38:06 -05:00
Author
Owner

@dlingerfelt22 commented on GitHub (Apr 6, 2026):

This looks like a Docker/containerd desynchronization issue rather than a bug with Open WebUI. WSL isn't the best at keeping daemons synchronized. Because you started the docker image with the --restart always flag, the containerd daemon only knows that state and will attempt to restart the process any time the container goes down, even though dockerd has lost track of it.

I would kill the container daemon and docker first:
sudo systemctl stop docker
sudo systemctl stop containerd

Then kill the shim and the uvicorn processes so they don't auto-restart:
sudo pkill -9 -f containerd-shim
sudo pkill -9 -f uvicorn

Then remove the specific container state you showed in your log:
sudo rm -rf /run/containerd/io.containerd.runtime.v2.task/moby/60c5708762c65d740ca25e5a5339398aca9617c5180f0808d1f1c0ce2f872682

Finally, restart the daemons:
sudo systemctl start containerd
sudo systemctl start docker

<!-- gh-comment-id:4194131858 --> @dlingerfelt22 commented on GitHub (Apr 6, 2026): This looks like a Docker/containerd desynchronization issue rather than a bug with Open WebUI. WSL isn't the best at keeping daemons synchronized. Because you started the docker image with the `--restart always` flag, the `containerd` daemon only knows that state and will attempt to restart the process any time the container goes down, even though `dockerd` has lost track of it. I would kill the container daemon and docker first: `sudo systemctl stop docker` `sudo systemctl stop containerd` Then kill the shim and the uvicorn processes so they don't auto-restart: `sudo pkill -9 -f containerd-shim` `sudo pkill -9 -f uvicorn` Then remove the specific container state you showed in your log: `sudo rm -rf /run/containerd/io.containerd.runtime.v2.task/moby/60c5708762c65d740ca25e5a5339398aca9617c5180f0808d1f1c0ce2f872682` Finally, restart the daemons: `sudo systemctl start containerd` `sudo systemctl start docker`
Author
Owner

@teddy911405 commented on GitHub (Apr 7, 2026):

The ghost container is gone from docker ps -a, and I was able to launch a new Open WebUI container on port 3000.

However, http://127.0.0.1:8080/ is still accessible and running!

Checking the process:

$ sudo ss -tlnp | grep 8080
LISTEN 0  2048  0.0.0.0:8080  0.0.0.0:*  users=(("python3",pid=XXXX,fd=20))

Something is still serving Open WebUI on port 8080, but I cannot find where it is installed.

<!-- gh-comment-id:4196152861 --> @teddy911405 commented on GitHub (Apr 7, 2026): The ghost container is gone from `docker ps -a`, and I was able to launch a new Open WebUI container on port 3000. However, **http://127.0.0.1:8080/ is still accessible and running!** Checking the process: ``` $ sudo ss -tlnp | grep 8080 LISTEN 0 2048 0.0.0.0:8080 0.0.0.0:* users=(("python3",pid=XXXX,fd=20)) ``` Something is still serving Open WebUI on port 8080, but I cannot find where it is installed.
Author
Owner

@teddy911405 commented on GitHub (Apr 7, 2026):

Thank you for the suggestion!

I actually have screenshot records confirming that Open WebUI was
originally installed via Docker.

I also already checked with pip and it returns not found:

***@***.***:~$ sudo ss -tlnp | grep 8080
LISTEN 0      2048          0.0.0.0:8080       0.0.0.0:*
 users:(("python3",pid=721,fd=20))
***@***.***:~$ ps -f -p 721
UID          PID    PPID  C STIME TTY          TIME CMD
root         721     694 18 20:17 ?        00:00:20 /usr/local/bin/python3
-m uvicorn open_webui.main:app --host 0.0.0.0
***@***.***:~$ sudo pip3 show open-webui
WARNING: Package(s) not found: open-webui
```[image: 螢幕擷取畫面 2026-04-06 200137.png][image: 螢幕擷取畫面 2026-04-06
200219.png]

David Lingerfelt ***@***.***> 於 2026年4月7日週二 下午6:48寫道:

> *dlingerfelt22* left a comment (open-webui/open-webui#23449)
> <https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198418267>
>
> Is there any chance you installed open-webui without docker previously?
> From your ss command it says python3 meaning its running outside a
> container.
>
> You can check what command started a process with this command but you
> need to populate the pid, the XXXX.
> ps -f -p XXXX
>
> That will likely list a directory to a venv that contains the install,
> that is why your pip3 command returned a not found when you tried to show
> it.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198418267>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AE5KZAN4GEKCAVUMZZ32C5L4UTMI7AVCNFSM6AAAAACXOCIQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJYGQYTQMRWG4>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
<!-- gh-comment-id:4198897013 --> @teddy911405 commented on GitHub (Apr 7, 2026): Thank you for the suggestion! I actually have screenshot records confirming that Open WebUI was originally installed via Docker. I also already checked with pip and it returns not found: ``` ***@***.***:~$ sudo ss -tlnp | grep 8080 LISTEN 0 2048 0.0.0.0:8080 0.0.0.0:* users:(("python3",pid=721,fd=20)) ***@***.***:~$ ps -f -p 721 UID PID PPID C STIME TTY TIME CMD root 721 694 18 20:17 ? 00:00:20 /usr/local/bin/python3 -m uvicorn open_webui.main:app --host 0.0.0.0 ***@***.***:~$ sudo pip3 show open-webui WARNING: Package(s) not found: open-webui ```[image: 螢幕擷取畫面 2026-04-06 200137.png][image: 螢幕擷取畫面 2026-04-06 200219.png] David Lingerfelt ***@***.***> 於 2026年4月7日週二 下午6:48寫道: > *dlingerfelt22* left a comment (open-webui/open-webui#23449) > <https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198418267> > > Is there any chance you installed open-webui without docker previously? > From your ss command it says python3 meaning its running outside a > container. > > You can check what command started a process with this command but you > need to populate the pid, the XXXX. > ps -f -p XXXX > > That will likely list a directory to a venv that contains the install, > that is why your pip3 command returned a not found when you tried to show > it. > > — > Reply to this email directly, view it on GitHub > <https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198418267>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AE5KZAN4GEKCAVUMZZ32C5L4UTMI7AVCNFSM6AAAAACXOCIQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJYGQYTQMRWG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@dylanmorris1231ho-spec commented on GitHub (Apr 7, 2026):

Thanks for providing the additional details and command outputs.

On Tue, Apr 7, 2026, 7:21 AM teddy911405 @.***> wrote:

teddy911405 left a comment (open-webui/open-webui#23449)
https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198897013
Thank you for the suggestion!

I actually have screenshot records confirming that Open WebUI was
originally installed via Docker.

I also already checked with pip and it returns not found:

***@***.***:~$ sudo ss -tlnp | grep 8080
LISTEN 0 2048 0.0.0.0:8080 0.0.0.0:*
users:(("python3",pid=721,fd=20))
***@***.***:~$ ps -f -p 721
UID PID PPID C STIME TTY TIME CMD
root 721 694 18 20:17 ? 00:00:20 /usr/local/bin/python3
-m uvicorn open_webui.main:app --host 0.0.0.0
***@***.***:~$ sudo pip3 show open-webui
WARNING: Package(s) not found: open-webui
```[image: 螢幕擷取畫面 2026-04-06 200137.png][image: 螢幕擷取畫面 2026-04-06
200219.png]

David Lingerfelt ***@***.***> 於 2026年4月7日週二 下午6:48寫道:

> *dlingerfelt22* left a comment (open-webui/open-webui#23449)
> <
https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198418267>

>
> Is there any chance you installed open-webui without docker previously?
> From your ss command it says python3 meaning its running outside a
> container.
>
> You can check what command started a process with this command but you
> need to populate the pid, the XXXX.
> ps -f -p XXXX
>
> That will likely list a directory to a venv that contains the install,
> that is why your pip3 command returned a not found when you tried to
show
> it.
>
> —
> Reply to this email directly, view it on GitHub
> <
https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198418267>,

> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AE5KZAN4GEKCAVUMZZ32C5L4UTMI7AVCNFSM6AAAAACXOCIQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJYGQYTQMRWG4>

> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>

—
Reply to this email directly, view it on GitHub
<https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198897013>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B7VFZECEKAQ37NMZR3LHX6L4UTXDVAVCNFSM6AAAAACXOCIQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJYHA4TOMBRGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>

<!-- gh-comment-id:4199475896 --> @dylanmorris1231ho-spec commented on GitHub (Apr 7, 2026): Thanks for providing the additional details and command outputs. On Tue, Apr 7, 2026, 7:21 AM teddy911405 ***@***.***> wrote: > *teddy911405* left a comment (open-webui/open-webui#23449) > <https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198897013> > Thank you for the suggestion! > > I actually have screenshot records confirming that Open WebUI was > originally installed via Docker. > > I also already checked with pip and it returns not found: > ``` > ***@***.***:~$ sudo ss -tlnp | grep 8080 > LISTEN 0 2048 0.0.0.0:8080 0.0.0.0:* > users:(("python3",pid=721,fd=20)) > ***@***.***:~$ ps -f -p 721 > UID PID PPID C STIME TTY TIME CMD > root 721 694 18 20:17 ? 00:00:20 /usr/local/bin/python3 > -m uvicorn open_webui.main:app --host 0.0.0.0 > ***@***.***:~$ sudo pip3 show open-webui > WARNING: Package(s) not found: open-webui > ```[image: 螢幕擷取畫面 2026-04-06 200137.png][image: 螢幕擷取畫面 2026-04-06 > 200219.png] > > David Lingerfelt ***@***.***> 於 2026年4月7日週二 下午6:48寫道: > > > *dlingerfelt22* left a comment (open-webui/open-webui#23449) > > < > https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198418267> > > > > > Is there any chance you installed open-webui without docker previously? > > From your ss command it says python3 meaning its running outside a > > container. > > > > You can check what command started a process with this command but you > > need to populate the pid, the XXXX. > > ps -f -p XXXX > > > > That will likely list a directory to a venv that contains the install, > > that is why your pip3 command returned a not found when you tried to > show > > it. > > > > — > > Reply to this email directly, view it on GitHub > > < > https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198418267>, > > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AE5KZAN4GEKCAVUMZZ32C5L4UTMI7AVCNFSM6AAAAACXOCIQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJYGQYTQMRWG4> > > > . > > You are receiving this because you authored the thread.Message ID: > > ***@***.***> > > > > — > Reply to this email directly, view it on GitHub > <https://github.com/open-webui/open-webui/issues/23449#issuecomment-4198897013>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/B7VFZECEKAQ37NMZR3LHX6L4UTXDVAVCNFSM6AAAAACXOCIQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJYHA4TOMBRGM> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#58652