How to Fix Frigate No Frames Received With go2rtc
- Incorrect go2rtc stream mapping
- Camera RTSP URL/path invalid
- Keyframe interval too high
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.
Symptoms
- No frames received errors in Frigate
- Camera feed drops after restart
- Live view blank while camera is online
- Recordings have gaps
- Only certain cameras fail
- Issue appears after config edits
Recognize these? Here's what usually causes it.
Common Causes
- Incorrect go2rtc stream mapping
- Camera RTSP URL/path invalid
- Keyframe interval too high
- Codec mismatch for selected live method
- Camera session limits exceeded
- Network instability between NVR and camera
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
Ensure 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.
- Incorrect go2rtc stream mapping
- Camera RTSP URL/path invalid
- Keyframe interval too high
- Codec mismatch for selected live method
- Camera session limits exceeded
Before you go — try one of these (they fix most cases).
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.