Continous/Repeated Reconnecting & Reconnected toast messages on v0.28.2
- Dominant language
- Python
- Stars
- 133k
- Forks
- 15.7k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 158
Description
### Custom Node Testing
- [ ] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)
### Expected Behavior
No reconnection issue.
### Actual Behavior
WebSocket `/ws` seems to be completed with status 101 within less than 1 second from the time it got connected instead of staying alive/connected, thus causing ComfyUI to repeatedly keeps trying to reconnects.
### Steps to Reproduce
This happened on cloud GPU (modal.com) deployed with https://github.com/caru-ini/modal-comfyui using the example models.py and plugins.py
Which install and launch ComfyUI using comfy-cli.
### Debug Logs
```powershell
CONNECT /ws -> 101 Switching Protocols (duration: 323.1 ms, execution: 194.8 ms)
```
### Other
As seen in the screenshot, ComfyUI Logs can't show any logs because there is no active websocket connection.
While the logs on the container only shows:
```
CONNECT /ws -> 101 Switching Protocols (duration: 323.1 ms, execution: 194.8 ms)
```
Contributor guide
Research direction
Reproduce the short-lived /ws connection with comfy-cli using the referenced modal-comfyui models.py and plugins.py setup, then inspect the /ws connection handling and the reconnect behavior. Done means the WebSocket remains connected and ComfyUI no longer repeatedly shows Reconnecting and Reconnected toasts in this deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100