Troubleshooting

Logs

Primary logs live under /var/log/vistralio/:

• connect.log — main API (vistralio-connect)
• media.log — stream proxy and edge WebSocket (vistralio-media)
• worker.log — detection, recording, retention (vistralio-worker)
• mqtt.log
• license.log

tail -F /var/log/vistralio/connect.log
tail -F /var/log/vistralio/media.log
tail -F /var/log/vistralio/worker.log

Useful service checks

systemctl status vistralio-connect vistralio-media vistralio-core vistralio-worker vistralio-ls vistralio-mqtt

Common checks

UI loads but streams fail

• check vistralio-media (systemctl status vistralio-media)
• check /api/streams/... and media token/auth
• if bridge-connected, check the remote vistralio-edge service on the bridge device

Events stop appearing

• check vistralio-worker (tail -f /var/log/vistralio/worker.log)
• check device detection settings
• check object list / zones / masks / schedules

Bridge router shows offline

• check vistralio-edge on the remote host
• confirm the bridge is connecting to wss://connect.vistralio.co.uk/api/edge/ws
• check token/fingerprint mismatch (token re-use on a different device is refused until an admin rotates it)
• check Admin → Setup → Edge Routers for the current status and enrollment command

Storage is filling up

• check vistralio-watchdog / vistralio-watchdog.timer
• review configured storage paths in Admin -> Advanced -> System
• du -sh /var/lib/vistralio/recordings/*/ 2>/dev/null | sort -h

Login issues on mobile/PWA

• clear the installed web app/browser cache if the shell is stale
• confirm /manifest.webmanifest and app shell are loading fresh
• check 2FA flow if enabled