How to Fix Frigate No Frames Received With go2rtc
- go2rtc can't pull the source stream
- Wrong stream URL in go2rtc config
- Codec/transport mismatch in go2rtc
Problem Description
Frigate shows No frames received for one or more cameras while go2rtc is enabled. Recording and live view may fail intermittently. This is often caused by incorrect stream role mapping, unstable camera RTSP paths, keyframe settings, or go2rtc stream definition issues.
Why This Happens in Real Homes
"No frames received" in Frigate with go2rtc means the go2rtc restreaming layer connected to your camera but isn't getting decodable video frames through to Frigate — the pipe opened, but no frames flow. It usually traces to a wrong stream URL in the go2rtc config, a codec or transport mismatch, or an unstable camera stream (a too-long keyframe interval leaves Frigate waiting for the first keyframe).
Test the source stream directly with VLC or ffprobe from the host to confirm it's alive and note its codec, then verify the go2rtc source URL and that Frigate's inputs point at the go2rtc restream correctly. Set a shorter keyframe (GOP/i-frame) interval on the camera, since a long one delays frames. Reduce simultaneous connections to the camera (each viewer and detector is a load), and align the codec and transport between go2rtc and Frigate.
Symptoms
- 'No frames received' error
- go2rtc stream not delivering frames
- Camera shows no frames
- Stream connects but no video
- No frames in the log
- go2rtc restream failing
- Blank camera via go2rtc
- Frames stop arriving
Recognize these? Here's what usually causes it.
Common Causes
- go2rtc can't pull the source stream
- Wrong stream URL in go2rtc config
- Codec/transport mismatch in go2rtc
- Camera stream unstable / long keyframe interval
- Network issue to the camera
- go2rtc/ffmpeg source misconfigured
- Restream not matching Frigate's expectation
- Camera overloaded (too many connections)
Most fixes happen in the first 3 steps.
Do not copy-paste stream blocks across cameras without checking channel/substream paths; many models use unique endpoint naming.
Tools & Requirements
Step-by-Step Solution
Validate stream definitions first
Check go2rtc configuration names, source URLs, and referenced stream keys in Frigate camera entries. A typo or wrong mapping can make Frigate request a non-existent stream while camera is actually healthy. Fix config consistency before testing live view.
Test camera RTSP directly
Use an independent RTSP test method to confirm camera stream path and credentials are valid. If direct RTSP fails, resolve camera-side stream settings first. Frigate cannot recover from invalid camera endpoint definitions.
Tune keyframe and codec settings
Set keyframe interval and codecs compatible with your chosen live view and recording roles. Very long keyframe intervals or unsupported codec combinations can cause slow/blank live load and intermittent no-frames errors under load.
Align Frigate role usage
Make sure detect, record, and live roles point to intended streams with correct quality/performance balance. Misusing one heavy stream for all roles can overload low-power camera/NVR setups and increase frame loss events.
Restart and monitor stability
After config correction, restart go2rtc/Frigate and monitor logs through several stream cycles. Confirm no recurring no-frames alerts. If errors persist on only one camera, isolate network path or camera firmware stability issues.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Keep a small camera-config registry with verified RTSP URLs and role mappings to avoid introducing typo regressions during edits.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- go2rtc can't pull the source stream
- Wrong stream URL in go2rtc config
- Codec/transport mismatch in go2rtc
- Camera stream unstable / long keyframe interval
- Network issue to the camera
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Frigate provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Frigate Stream Ingestion.
Source: docs.frigate.video
Need More Help? Frigate Support
Note: The contact information below connects you directly to Frigate's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
Accessories owners commonly pair with Frigate Stream Ingestion.
SANDISK 64GB Extreme microSDXC UHS-I Memory Card with Ada...
SANDISK 128GB Ultra microSDXC UHS-I Memory Card with Adap...
SANDISK 64GB Ultra microSDXC UHS-I Memory Card with Adapt...
As an Amazon Associate we earn from qualifying purchases.