Skip to main content

Troubleshooting

Toposync is in Alpha Early Access. That means troubleshooting is part of the product work right now: there are many operating systems, cameras, protocols, Home Assistant setups, Docker hosts, GPUs, browsers, networks, and installation paths to validate.

This page is the starting point. More focused troubleshooting docs will be added over time.

First checks

Start with the basics:

  1. Confirm which installation path you are using: Python, Docker, Home Assistant OS add-on, or processing server.
  2. Confirm the Toposync process is running.
  3. Open the health endpoint when available, usually /api/health.
  4. Check the browser console or server logs.
  5. Confirm the active data directory and file locations.
  6. Restart after changing environment variables or command-line flags.

If the issue involves cameras, note the protocol and camera model. If it involves Home Assistant OS, note the add-on version, host architecture, and whether the problem happens through ingress, direct port, or both.

Find the focused guide

AreaUse this guide
Choosing the right install pathChoose your installation
Python on Linux/macOSPython on Linux and macOS
Python on WindowsPython on Windows
Docker CPUDocker CPU
Docker CUDADocker CUDA
Home Assistant OS add-on installHome Assistant OS add-on
Home Assistant OS operationHome Assistant add-on troubleshooting
Processing server on Linux/macOSProcessing server on Linux and macOS
Processing server on WindowsWindows processing service
Processing server with DockerProcessing server with Docker
Live viewing and streamingCamera live viewing
Ports and connection refusedPorts
Environment variablesEnvironment variables
Data directory and disk usageFile locations
Broken settings or config recoveryConfiguration

Common symptoms

SymptomFirst place to check
Browser cannot open ToposyncProcess logs, port binding, Ports.
connection refusedWrong host, wrong port, service stopped, container port not published, or Home Assistant add-on direct port not enabled.
UI loads but cameras do notCamera URL, RTSP/ONVIF credentials, stream source, Camera live viewing.
Home Assistant sidebar works but direct URL does notAdd-on network settings, ingress versus direct-port mode, Home Assistant add-on troubleshooting.
Pipelines do not produce eventsPipeline enabled state, operator diagnostics, camera mapping, processing server assignment.
Processing server is unreachableBasic auth, host URL, firewall, service status, and the relevant processing server install guide.
Disk usage growsData directory, generated files, pipeline snapshots, streaming runtime files, File locations.

Open a GitHub issue

For ordinary bugs, use GitHub Issues.

Good issues help the project validate the real world faster. Include:

  • Toposync version;
  • installation path;
  • operating system and architecture;
  • browser or app surface;
  • Home Assistant OS/add-on version when relevant;
  • camera model and protocol when relevant;
  • Docker, GPU, DirectML, CUDA, or processing server details when relevant;
  • expected behavior;
  • actual behavior;
  • sanitized logs and screenshots;
  • exact steps to reproduce.

Do not include passwords, tokens, private URLs, camera credentials, private camera images, personal data, or vulnerability details in a public issue.

Contribute fixes or docs

Contributions are welcome. Start with CONTRIBUTING.md for setup, development workflow, tests, documentation rules, and pull request expectations.

Small focused contributions are especially useful during Alpha Early Access:

  • improving installation docs;
  • adding troubleshooting notes from real devices;
  • reporting camera compatibility details;
  • fixing broken links or unclear steps;
  • adding focused tests around distribution or Home Assistant behavior.

Security issues

Do not report vulnerabilities in public issues.

Use private GitHub vulnerability reporting or a private GitHub Security Advisory when available. See SECURITY.md.