[GH-ISSUE #8134] Fresh 0.5.2 install websocket issues #30542

New Issue

GiteaMirror · 2026-04-25T04:47:12-05:00

GiteaMirror commented

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

Originally created by @TemperedGithub on GitHub (Dec 27, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8134

Bug Report

Installation Method

Docker on Unraid using the standard Docker installation method from documentation:

docker run -d -p 3000:8080 -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main```

Expected Behavior:

WebSocket connections should establish properly
Model responses should stream smoothly
Chat UI should remain stable and visible

Actual Behavior:

Initial symptoms: Slow text streaming
After any model generation gets interrupted/corrupted:

Complete failure of model responses
Chat UI flickers and eventually disappears
Persistent WebSocket connection errors


Hard refresh temporarily fixes some issues but problems return
Even with fresh install, getting persistent WebSocket errors

Description
Bug Summary:
WebSocket connection failures and UI instability in v0.5.x when using Cloudflared as reverse proxy, leading to complete system failure after any interrupted model generation.
Reproduction Details
Steps to Reproduce:

Install v0.5.2 using standard Docker installation
Configure Cloudflared as reverse proxy
Try to use any model for chat
Observe slow text streaming
If any model generation gets interrupted, system enters failed state
Fresh install shows same WebSocket errors from start

Logs and Screenshots
Docker Container Logs:
Invalid transport (further occurrences of this error will be logged with level INFO)
ERROR [engineio.server] Invalid transport
INFO:     69.84.52.229:0 - "GET /ws/socket.io/?EIO=4&transport=polling&t=PG7JV4I HTTP/1.1" 400 Bad Request

Additional error during usage:
File "/app/backend/open_webui/main.py", line 723, in inspect_websocket
    return await call_next(request)
RuntimeError: No response returned.

Additional Information

Issue persists across multiple versions (0.5.1, 0.5.2)
Problems occur even with fresh install and no user data
Using Cloudflared for reverse proxy, but issues occur even with direct local access
Different from the Ollama connection issues described in troubleshooting docs

Originally created by @TemperedGithub on GitHub (Dec 27, 2024). Original GitHub issue: https://github.com/open-webui/open-webui/issues/8134 # Bug Report ## Installation Method Docker on Unraid using the standard Docker installation method from documentation: ```bash docker run -d -p 3000:8080 -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main``` Expected Behavior: WebSocket connections should establish properly Model responses should stream smoothly Chat UI should remain stable and visible Actual Behavior: Initial symptoms: Slow text streaming After any model generation gets interrupted/corrupted: Complete failure of model responses Chat UI flickers and eventually disappears Persistent WebSocket connection errors Hard refresh temporarily fixes some issues but problems return Even with fresh install, getting persistent WebSocket errors Description Bug Summary: WebSocket connection failures and UI instability in v0.5.x when using Cloudflared as reverse proxy, leading to complete system failure after any interrupted model generation. Reproduction Details Steps to Reproduce: Install v0.5.2 using standard Docker installation Configure Cloudflared as reverse proxy Try to use any model for chat Observe slow text streaming If any model generation gets interrupted, system enters failed state Fresh install shows same WebSocket errors from start Logs and Screenshots Docker Container Logs: Invalid transport (further occurrences of this error will be logged with level INFO) ERROR [engineio.server] Invalid transport INFO: 69.84.52.229:0 - "GET /ws/socket.io/?EIO=4&transport=polling&t=PG7JV4I HTTP/1.1" 400 Bad Request Additional error during usage: File "/app/backend/open_webui/main.py", line 723, in inspect_websocket return await call_next(request) RuntimeError: No response returned. Additional Information Issue persists across multiple versions (0.5.1, 0.5.2) Problems occur even with fresh install and no user data Using Cloudflared for reverse proxy, but issues occur even with direct local access Different from the Ollama connection issues described in troubleshooting docs

GiteaMirror closed this issue

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

GiteaMirror commented

2026-04-25 04:47:14 -05:00

@tjbck commented on GitHub (Dec 27, 2024):

#8074

@tjbck commented on GitHub (Dec 27, 2024): #8074

Sign in to join this conversation.