Skip to content
Fregata MobileDocs

Server status, logs and restart

Settings › Server Status is your server’s health on one screen: whether it’s running, how fast it’s detecting, what each camera is doing, and anything that needs attention, with its logs and a safe restart a tap away. With a named server, the row is called after it, such as Cabin Status. Its subtitle answers is it up? without opening it: Running for 3 days, 4 hr, One problem needs attention, or Not responding.

  1. The server: whether it’s running, how long it’s been up, its version, detections a second, and who you’re signed in as. If a newer Frigate is out, it says so under the version.
  2. Object detection: how long each detection takes, over the last 20 minutes.
  3. Detection by camera: each camera’s detect stream.
  4. Logs: Frigate’s own logs, live.
  5. Controls: restart the server.

The screen keeps itself up to date while it’s open; pull down to refresh at once.

Problems

Section titled “Problems”

When something’s wrong, a list under the server card says what, in plain words, and the subtitle in Settings counts them. For example:

  • Driveway is offline: no frames from the camera. Check the camera and its connection.
  • Driveway’s connection is poor: it has been reconnecting or stalling.
  • The coral detector is slow: 120 ms per detection.
  • Garage is skipping 3 frames a second because detection cannot keep up.
  • Shared memory is 128 MB; Frigate needs at least 256 MB for these cameras. Raise shm_size for Frigate’s container.
  • Garage uses a lot of CPU decoding video (85%). Hardware acceleration may help.

Reading the numbers

Section titled “Reading the numbers”

Object detection shows each detector’s time per detection. Under 50 ms keeps up comfortably; past 100 ms, detection falls behind and frames get skipped.

Detection by camera shows each camera’s detect stream: the frames a second Frigate decodes for detection, how many go through object detection, and any skipped because the detector couldn’t keep up. Recording and live view use their own streams and aren’t counted here.

Enrichments shows the AI features your server runs, such as face recognition, license plate recognition, semantic search and GenAI descriptions: how long each takes, and how often it runs. They’re judged against the same thresholds Frigate’s own System page uses.

Hardware shows CPU, memory and, where there is one, the GPU, for the whole machine and for Frigate’s own processes. Storage shows the space for recordings, the cache, and shared memory, and whether each is Sized for your cameras.

On Fregata NVR Fregata NVR only, the screen also shows which part of the Mac runs detection, such as the Neural Engine, and suggests switching to it when detection runs on the GPU or falls back to the CPU.

Live logs

Section titled “Live logs”

Open live logs shows Frigate’s logs as they’re written, one service at a time. Needs an administrator

  • Service switches between frigate, go2rtc and nginx.
  • The level filter shows Everything, Info and above, Warnings and errors or Errors only. Tap a level badge on any line to show only that level.
  • Search the log finds a word.
  • Pause live log holds the view still while you read; Jump to latest catches up.
  • Touch and hold a line to Copy line, or share what’s showing with Share these lines.

Reading the logs needs an administrator account, unless your server lets viewers read them too.

Restart

Section titled “Restart”

Restart Frigate, under Controls, restarts your server. Needs an administrator It asks first: Frigate stops and starts again, which usually takes under a minute. Until it’s back, nothing is recorded, live view and alerts pause, and everyone using it is disconnected.

After you confirm, a sheet follows the restart step by step: Restart requested, Frigate stopped, Frigate answering again, then Cameras streaming as each camera comes back, until Everything is back up and how long it took. If some cameras don’t come back, it says which. You can hide the sheet; the Settings row keeps saying Restarting… until it’s done.

If the restart did not restart, Frigate kept running: it may have been restarted by something else, or the request was ignored.

Open Frigate in Safari

Section titled “Open Frigate in Safari”

Open Frigate in Safari, at the bottom, opens your server’s own web interface, at the address the app is using now, for everything the app doesn’t change. You sign in there separately. If your server needs custom headers, Safari can’t send them, so it shows the proxy’s own sign-in instead.