[Beta Support]: WebSocket connections not closed on camera group / single camera view navigation, leading to "Insufficient resources" error

[ibs0d]

Describe the problem you are having

Great project, thank you for your work.

When navigating between camera groups, or switching between a single camera view and a group view, WebSocket connections are not properly closed. Each navigation event leaves behind one or more orphaned WebSocket connections. Over time — and proportionally to the number of cameras — these accumulate until the browser throws:

WebSocket connection to 'wss://...' failed: Insufficient resources

Once this limit is hit, cameras in the grid can no longer switch to MSE playback, and single camera view becomes completely non-functional.

Reproduction rate depends heavily on camera count:

16 cameras — reproducible, but requires rapid repeated navigation over some time
32 cameras — reproduces quickly
62 cameras — 3–4 clicks is enough to trigger the error

Claude suggested a fix: ibs0d@43a2d01
This resolves the issue, though it introduces failed: WebSocket is closed before the connection is established errors in the console. In my case these have no practical impact, so I consider it an acceptable workaround for now.

Beta Version

current dev

Issue Category

WebUI / Frontend

Frigate config file

simple

Relevant Frigate log output

no errors

Relevant go2rtc log output (if applicable)

no errors

Install method

Docker Compose

docker-compose file or Docker CLI command

simple

Operating system

Other Linux

CPU / GPU / Hardware

No response

Screenshots

No response

Steps to reproduce

No response

Any other information that may be helpful

No response

[hawkeye217]

Thanks, there were actually a couple of factors causing the issue. I've improved it in #22762

[ibs0d]

Thank you, your fix worked.
One more thing while we're on the topic — no need to open a new thread: in the camera grid, if you open the context menu → Streaming Settings → then click Save, Cancel, or just close the dialog, the UI breaks and becomes unresponsive. Sometimes it happens on the first attempt, but I've also seen cases where it took two visits to Streaming Settings to reproduce.

[hawkeye217]

That's a well-known issue with Radix, the underlying UI library that Frigate uses - in certain conditions it adds pointer-events: none to the body element so it seems like the whole UI is frozen. I'll fix it in a future PR.

[hawkeye217]

Fixed in 911c54a