HomeLabFix

Frigate / Troubleshooting

Frigate Says “No Frames Have Been Received”

Use the exact Frigate 0.17.2 Stream Offline message and FFmpeg evidence to separate camera reachability, RTSP authentication/path, input preset, and decode failures without exposing camera credentials.

Frigate 0.17.2's tagged UI string makes this a precise frame-ingest diagnosis: the detect stream is not delivering frames and the next evidence source is the error log, not a generic camera reset.[5][1]

Frigate documents distinct FFmpeg input presets and camera stream roles. A stream can work in another player yet still fail in Frigate because of transport, input, authentication, container-network, or decode differences.[2][3][1]

Applicability

Products
Frigate
Scope
For Frigate 0.17.2 when the UI shows the Stream Offline state with the tagged 0.17.2 message “No frames have been received on the … detect stream, check error logs” for a configured camera. This page is not for Frigate itself being down, object-detection accuracy, Home Assistant integration, or playback problems after frames are already arriving.[4][5]
Last verified

Symptoms

  • The Frigate service is running and the camera is configured, but the camera tile is Stream Offline and reports that no frames have been received on the detect stream. The page continues only after that symptom is confirmed.[5]

Quick diagnosis

Prove the camera stream, then use Frigate and FFmpeg evidence to separate network, authentication, preset, and decode failures.

Read-only

Capture the exact camera and FFmpeg error without leaking credentials

Record the camera name, timestamp, Stream Offline message, and the corresponding Frigate/FFmpeg error. Redact RTSP usernames, passwords, tokens, and private hostnames before sharing logs.[5][1]

Read-only

Prove the configured camera stream independently

Test the same intended camera stream from a trusted host or tool without pasting a credential-bearing URL into public logs or examples. If the stream cannot be opened independently, stop before changing Frigate presets.[1][3]

Read-only

Read the input path, role, and preset

Inspect the camera's FFmpeg input, detect role, and selected preset. Do not rewrite the whole camera configuration or switch to host networking as a diagnostic shortcut.[2][3]

Interactive troubleshooter

Your answers stay in this browser tab. The tool does not connect to your systems or send diagnostic results.

Guided check / step 1

Safe diagnostic guidance

Does the camera show the Frigate Stream Offline no-frames message?

The tagged 0.17.2 UI string is the scope gate for this diagnosis.[5]

Read the complete diagnostic tree without using the controls
  1. Does the camera show the Frigate Stream Offline no-frames message?

    The tagged 0.17.2 UI string is the scope gate for this diagnosis.[5]

    • Yes — no frames on the detect stream → Can the intended camera stream be opened outside Frigate?
    • No — different Frigate symptom → Different Frigate diagnosis
  2. Can the intended camera stream be opened outside Frigate?

    Use a trusted local test without exposing credentials.[1][3]

    • Yes — stream opens elsewhere → What does the correlated Frigate/FFmpeg error show?
    • No — stream also fails elsewhere → The camera stream itself is unavailable
  3. What does the correlated Frigate/FFmpeg error show?

    Use the camera name and timestamp; do not guess from the UI message alone.[1]

    • Authentication or path failure → The configured camera authentication or path is rejected
    • Connection refused or timeout → Frigate cannot reach the camera stream path
    • Stream opens but decode fails → The stream opens but FFmpeg cannot decode usable frames
    • Input/transport issue or FFmpeg stays unstable → Does the configured input preset match the documented stream path?
    • Unclear → The frame-ingest failure is not yet isolated
  4. Does the configured input preset match the documented stream path?

    Keep direct RTSP and restream presets distinct.[2]

    • Yes — preset matches → The frame-ingest failure is not yet isolated
    • No — preset/path mismatch → The FFmpeg input preset does not match the stream path
  5. Different Frigate diagnosis

    Use the symptom-specific path for service, playback, detection, or integration problems.[5]

  6. The camera stream itself is unavailable

    Repair camera reachability, RTSP path, or authentication before changing Frigate presets.[1][3]

  7. The configured camera authentication or path is rejected

    Correct only the proven private input mismatch and protect credentials during testing.[3]

  8. Frigate cannot reach the camera stream path

    Keep authentication and preset changes out until the container/host network path is proven.[1]

  9. The stream opens but FFmpeg cannot decode usable frames

    Continue with codec/profile evidence instead of network or privilege changes.[3]

  10. The FFmpeg input preset does not match the stream path

    Change only the documented preset for the proven transport/input path and preserve the old configuration.[2]

  11. The frame-ingest failure is not yet isolated

    Capture the exact camera error, private configuration, stream test, and FFmpeg evidence before another change.[1][3]

Detailed diagnosis

Read-only

1. Verify the exact Stream Offline frame-ingest symptom

Confirm the tagged 0.17.2 Stream Offline message refers to the camera's detect stream. A disabled camera, service outage, or playback-only issue exits this page.[5]

Read-only

2. Test whether the intended camera stream can be opened outside Frigate

Use a trusted local test that preserves credentials. Failure outside Frigate points to camera reachability, RTSP path, or authentication before Frigate-specific preset changes.[1][3]

Read-only

3. Correlate the Frigate and FFmpeg log with the failing camera

Use the timestamp and camera name to distinguish connection refusal or timeout, authentication/path errors, and decode/codec failures. Do not infer the cause from the UI message alone.[1][3]

Read-only

4. Compare the configured FFmpeg input preset with the stream path

If the stream is reachable and the log points to transport/input handling, compare the configured preset with Frigate's documented RTSP and restream presets. Keep direct RTSP and go2rtc restream paths distinct.[2]

Read-only

5. Separate an opened stream from a decode failure

When FFmpeg opens the stream but cannot decode usable frames, inspect the camera codec/profile and Frigate camera guidance before changing networking or authentication.[3][1]

Supported scenarios

These observations narrow the next investigation; they do not establish a unique cause.

The camera stream is not reachable or the RTSP path is wrong

If the intended stream cannot be opened independently, Frigate cannot ingest frames from it. This branch stays at camera/network/path evidence rather than changing FFmpeg presets first.[1][3]

How to check: Verify the camera address and intended stream path from a trusted local test while keeping credentials private.[3]

The camera rejects the configured authentication

An authentication failure in the correlated FFmpeg log can prevent the input from opening even though the camera host itself is reachable.[1][3]

How to check: Confirm the credentials and path in the private Frigate configuration without exposing them in shared logs or shell history.[3]

The configured FFmpeg input preset does not match the stream path

Frigate documents separate input presets for generic RTSP, UDP RTSP, and restream paths. A reachable stream can still fail when the selected input behavior is wrong for that path.[2]

How to check: Compare the exact configured path with the documented preset purpose before changing one preset value.[2]

FFmpeg opens the stream but cannot decode usable frames

A stream can be reachable while its codec/profile or decode path does not produce frames Frigate can use for the configured role.[3][1]

How to check: Use the correlated FFmpeg error and camera stream metadata to distinguish decode failure from network or authentication failure.[3]

Next actions and procedure boundaries

Potentially disruptive

Correct only a proven camera URL, path, or authentication mismatch

If the evidence proves the configured input is wrong, correct only that camera's private input value and retest. Keep credentials out of article output, screenshots, public logs, shell history, and process-list-visible examples.[3][1]

Before changing anything

Risk
Changing a camera input can interrupt live view, detection, recording, and downstream automations for that camera.[3]
Safer check
Record the current camera input, role, relevant preset, and the exact correlated error before editing.[3][2]
Expected result
The same camera begins delivering frames on the detect stream and the correlated FFmpeg input error disappears.[5][3]
Backup / recovery access
Preserve a restorable copy of the current Frigate camera configuration with secrets protected.[3]
Rollback
Restore the previous input configuration if frame ingest does not recover or another camera function breaks.[3]
Potentially disruptive

Change one FFmpeg input preset only when the stream evidence supports it

If the camera stream works and the log plus configuration prove a transport/input mismatch, select the documented preset for that path. Do not add random FFmpeg flags, privileged mode, or host networking as universal fixes.[2][1]

Before changing anything

Risk
An incorrect input preset can make the camera stream fail completely or change transport behavior.[2]
Safer check
Record the current preset, input path, stream behavior outside Frigate, and FFmpeg error before changing it.[2][1]
Expected result
Frigate's FFmpeg process remains running and the camera starts reporting frames on the detect stream.[5][2]
Backup / recovery access
Preserve the previous camera FFmpeg configuration so the exact preset can be restored.[2]
Rollback
Restore the previous preset if frame ingest does not recover or the stream becomes less stable.[2]
Read-only

If the stream opens but decode fails, keep networking unchanged

Preserve the working network and authentication path and continue with codec/profile evidence. Do not solve a decode error by disabling camera authentication, exposing the camera publicly, or broadening container privileges.[3][1]

Warnings and boundaries

RTSP URLs commonly contain usernames and passwords. Use redacted placeholders in examples and warn operators that command-line URLs can remain in shell history or be visible in process listings.[3]
Do not disable camera authentication, expose cameras publicly, run Frigate privileged, or switch to host networking merely because frames are missing.[3][2]

Sources

Links were reviewed on 2026-09-08. Reachability and automated validation do not replace editorial verification of each claim.

  1. Frigate FAQs
    Frigate project · Tier A · accessed 2026-09-08
  2. Frigate FFmpeg presets
    Frigate project · Tier A · accessed 2026-09-08
  3. Frigate camera setup
    Frigate project · Tier A · accessed 2026-09-08
  4. Frigate releases
    Frigate project · Tier B · accessed 2026-09-08
  5. Frigate v0.17.2 Stream Offline UI string
    Frigate project · Tier B · accessed 2026-09-08