Troubleshooting Avistio Edge

Confirm you are using http://<edge-host-ip>:3000 from the same network and that port 3000 is available on the Edge host. Check the service status and logs below. If you are on the Edge host itself, try http://localhost:3000.

Run docker compose ps and inspect the logs for both avistio and database. Wait for PostgreSQL to become healthy. Confirm Docker Compose is current enough to support the service_completed_successfully dependency condition.

Check that the Frigate URL is reachable from inside the Edge container, the host and port are correct, and Frigate is running. If the containers run on different machines, verify routing and firewall rules between them. Port 8971 is a typical authenticated Frigate URL; use the URL appropriate to your setup.

Check the Frigate username and password in Edge's integration settings. Sign in to Frigate with that account in a browser to confirm it works, then save the correct credentials in Edge. Do not disable Frigate authentication as a workaround.

The Frigate camera name must also exist as a go2rtc stream name for Avistio's current readiness check. For example, camera frontdoor needs stream frontdoor; frontdoor_main alone will not pass. See the stream naming guide.

A successful connection test checks server-side camera/stream readiness, not browser ICE connectivity. First try Live locally. Check browser developer tools for WebRTC errors, verify go2rtc's WebRTC listener and Frigate host candidate, and confirm the browser can reach the listener. For Cloud Live, Cloud/Edge signaling must work and ICE must find a direct or TURN-relayed media path.

Try one camera at a time, then try a lower-resolution substream. Check camera signal, Wi-Fi or LAN quality, browser/device decoding capacity, and supported codecs. H.264 is broadly compatible; H.265/HEVC support varies. Long keyframe intervals can also make playback slow to start.

Confirm the camera is enabled and Frigate is producing events. Object detection must be configured and enabled for object-detection events; the example on the Frigate page explicitly disables it. Cloud event summaries are limited and are not a copy of the site's full event history.

Confirm Frigate recording is enabled, the camera has a record input role, and its retention policy keeps footage for the time you are checking. New installations cannot show historical footage from before recording was enabled.

Generate a fresh pairing code in Cloud and enter it in the Edge Cloud page promptly. Codes expire. Confirm Edge has outbound internet access and the site is still awaiting pairing. Do not share a pairing code publicly.

Confirm the Edge container is healthy and the Edge host has outbound internet access. Check that the device clock is correct and inspect the Avistio logs for Cloud connection errors. Local Frigate monitoring can continue even when Cloud is unavailable.

Local playback proves the camera stream is usable on the local path; remote Live also needs Cloud signaling and a browser-to-Frigate/go2rtc ICE media path. Confirm the Frigate candidate advertises an address appropriate for the viewer, check TCP/UDP network restrictions, and verify Cloud TURN connectivity if TURN is configured for your deployment. Do not expose Frigate's web/API or go2rtc admin ports publicly.