Getting Help

There are two ways to get help — pick the one that fits your question.

GitHub Discussions

Post in GitHub Discussions for:

• Troubleshooting — the team and community both monitor this. You’ll often get a response quickly.
• Feature requests — describe what you’d like to see and why.
• Setup questions — anything not covered in the docs.

Answers here are public and searchable. If your issue has come up before, the answer is likely already there. If it hasn’t, your thread will help the next person who hits it.

Email

Reply directly to your license email for:

• Private questions — account matters, billing, logs or config you’d rather not share publicly.
• Anything one-on-one — if you’d prefer to work through an issue directly with the team.

We read and reply to every email.

Create a diagnostic bundle

Whichever channel you use, the fastest way to get a useful answer is to attach a diagnostic bundle. It’s a one-click action that gathers everything the team would otherwise ask you for — logs, your config, live stats, and system state — into a single upload, and hands you a short ID to share.

To create one: in the menu-bar tray, go to Settings → Troubleshooting → Create Diagnostic Bundle…. A dialog explains what’s collected; click Create Bundle. Fregata assembles the bundle, uploads it, and shows an ID like FDB-7Q2K9F3M1XZ4W8N6VJ0P. Click Copy ID.

Then paste that ID into your GitHub Discussion or support email. The ID is safe to post publicly — it contains no data and grants no access. Only the Fregata developers can open the bundle it points to, so you can drop it straight into a public thread without exposing anything.

What the bundle contains

• Your configuration — config.yml and the generated go2rtc.yaml.
• Recent logs — the tail of the Frigate, go2rtc, and nginx logs, plus any recent crash reports.
• Live stats — Frigate’s /api/stats and /api/config and go2rtc’s stream status, when Fregata is running.
• System & storage state — macOS version and hardware, memory and thermal state, mounted volumes and free space (which matters a lot for recording issues), listening ports, the bundled ffmpeg’s version and hardware encoders, and short samples of the running Fregata processes.
• A database summary — table row counts and the most recent recording/event rows (not the database itself).

It does not include your recordings or camera video, your full database, or your saved license token.

Privacy and what the ID can do

Fregata does not scrub the bundle, so your config.yml and logs may contain sensitive values such as camera passwords. That’s a deliberate trade-off for useful diagnostics, and the app tells you so before it collects anything. In exchange:

• The bundle is uploaded to a private store that only the Fregata developers can read — there is no public link to it.
• It is auto-deleted after your issue is resolved (and in all cases expires automatically).
• The FDB-… ID grants no remote access to, or viewing of, your cameras or recordings — it’s only a reference the support team resolves on their end.

If you’d still rather not include credentials, share files manually instead (see below) after removing them.

If Fregata isn’t activated

The bundle uploads automatically only when your Mac holds a valid license or trial. On an unactivated or badly broken install, Fregata still builds and saves the bundle locally and offers Reveal in Finder — attach that .zip to an email to the team instead.

Sharing files manually

If you’d prefer to send individual files rather than a bundle, attaching the following makes it much easier to reproduce the problem on our end:

• Log file — ~/Fregata/logs/frigate/current (or the relevant chunk of it). Open it from the tray with Settings → Open Frigate Logs, or grab the folder with Reveal Logs in Finder.
• Config file — ~/Fregata/config/config.yml (remove camera credentials before sharing).