mirror of
https://github.com/open-webui/open-webui.git
synced 2026-07-16 14:39:31 -05:00
[GH-ISSUE #20816] issue: Cancel event sent for long-running tasks, no output retrieved #73900
Reference in New Issue
Block a user
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?
Originally created by @moooV252 on GitHub (Jan 20, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20816
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.7.2
Ollama Version (if applicable)
llama.cpp b7779 #6df686b, Ollama latest
Operating System
WSL2 Docker
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Long running tasks on local external llamacpp with big context window finish and retrieve results.
UPD: tested with ollama, same issue.
UPD2: I've narrowed it down to a port proxy timeout issue in docker -> wsl2 -> windows. Looks like it's not quite related to openwebui, but it would be nice if OW sent keepalive pings to an external endpoint so the connection stays intact. When openwebui is launched in a python venv in windows itself the problem disappears.
Actual Behavior
... long time passes (30min to 2 hours)
I notice this behavior only on long-running tasks, short-running (fast llms, small context windows) work as expected. If the first token gets generated within 1-2 minutes it's ok.
I'm running the latest openwebui image inside WSL2 docker, timeouts are increased both in openwebui using AIOHTTP_CLIENT_TIMEOUT=600000 environment variable as well as --timeout set to the same value in llamacpp launch string.
Made sure to pull the latest image before launching.
Steps to Reproduce
Launch WSL2 under windows.
Run docker openwebui like this:
docker run -d -p 1414:8080 -v $(pwd)/ow_data:/app/backend/data -e "AIOHTTP_CLIENT_TIMEOUT=600000" --name open-webui ghcr.io/open-webui/open-webui:mainRun llamacpp on another machine, just in plain windows (no wsl, no port forwarding):
llama-server.exe -m D:\llamacpp_models\Qwen3-VL-235B-A22B-Thinking-UD-Q4_K_XL-00001-of-00003.gguf --port 11434 --host 0.0.0.0 --ctx-size 98304 --temp 1.0 --min-p 0.0 --top-p 0.95 --top-k 20 --presence-penalty 0.0 --repeat-penalty 1.05 --jinja --threads 32 -ctk q8_0 -ctv q8_0 -ngl 99 --parallel 1 --timeout 600000 -cram -1 --n-cpu-moe 90 --mmproj d:\llamacpp_models\Qwen3-VL-235B-A22B-mmproj-BF16.ggufhttp://10.0.0.5:11434/v1Logs & Screenshots
Docker logs:
Llamacpp logs:
Additional Information
No response
@owui-terminator[bot] commented on GitHub (Jan 20, 2026):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
by shentong0722 • Jan 04, 2026 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@tjbck commented on GitHub (Jan 22, 2026):
Open to reviewing PRs.