View your Frigate server on Tailscale

Confirm the address and port, then test the same address in your device’s browser. A local IP address is normally reachable only on the same network unless you have configured remote access. Allow Tailgate access to your local network in system settings if prompted.

If Frigate opens in a browser but Tailgate still fails, check that your server URL uses the correct protocol, its certificate is valid for the hostname, and your account can sign in. Include the error message when contacting support.

Choose Connect to Tailscale during server setup and sign in on Tailscale’s page. Approve the device if your tailnet requires it, then close the sign-in sheet with Done or Back after approval. Use a Frigate address reachable from that tailnet.

Confirm that the Frigate machine is online and your tailnet access rules allow the connection. Tailgate uses an app-only Tailscale connection; it does not configure a system-wide VPN. You can manage or revoke the Tailgate device from your Tailscale administration console.

A home-network address usually cannot be reached from mobile data. Configure remote access, such as the app’s optional Tailscale connection, and check that the chosen server address works through it. Return to the app after changing networks so it can check and recover the connection.

Check the camera’s live view in Frigate first. In Tailgate’s camera settings, confirm the selected go2rtc stream exists. Try another player under Player: WebRTC, MSE, JSMpeg, MJPEG, or Images. Availability depends on your Frigate configuration.

WebRTC and MSE support audio when provided by the stream. JSMpeg, MJPEG, and Images use the detection feed and do not carry audio. If a Play button appears, tap it to allow playback.

Check the camera’s mute preference and your device volume. Push-to-talk requires WebRTC, microphone permission, and a Frigate/go2rtc camera stream configured for two-way audio. If you denied microphone access, enable it for Tailgate in system settings and try again.

Snapshots are saved to Photos on iOS, Pictures/Tailgate in the Android gallery, or Pictures/Tailgate on desktop. Allow photo or storage access when requested. Browser previews download the snapshot.

Recording downloads open your device’s share or save controls. The destination depends on the option you choose, such as Photos, Files, or another app. Check that the save completed and that your device has enough storage.

Frigate controls recording retention. A recording may have expired, been deleted, or never been recorded for that camera. Confirm it is still available in Frigate, and check that your account has permission to view or download it.

Connect using Frigate’s authenticated address and sign in with a real account. For many installations this is HTTPS on port 8971. An anonymous or trusted/internal endpoint may let you watch cameras without letting Frigate save a notification registration.

Open Notifications, enable alerts on this device, allow the system permission, and connect the relay. Frigate notifications must also be enabled. A new registration may require a Frigate restart; restart and test actions may need administrator access.

A relay receipt confirms that Frigate reached the notification relay. It does not confirm delivery to your phone. Check Tailgate’s system notification permission, Focus or Do Not Disturb settings, paused alerts, quiet hours, and camera cooldown. On Android, also enable the Camera alerts notification channel.

Test with the app in the foreground and background. If the issue continues, send support the approximate test time and time zone, platform, and the non-sensitive status text shown in Notifications. A Frigate test can notify other devices registered with the same server.

Tailgate filters repeated generated detections for the same review for up to 24 hours. The per-camera cooldown defaults to 60 seconds and can be changed in notification settings; set it to zero to disable that cooldown. Pause and quiet hours can also suppress alerts. Tests and custom or AI warning messages bypass the generated-detection filter.

Use Settings → Notifications → Forget this device for that server to revoke its relay subscription. Keep the app online so the removal can finish; offline removals are retried when connected. You can also change notification permission in system settings.

Revoking a subscription stops delivery but does not automatically erase retained relay records. See the privacy and deletion information below to request deletion.