Repository navigation
Troubleshooting
Start with Settings → Release and record the installed version and source revision. Keep exact error text and support logs privately; sanitize anything posted publicly.
Choose Windows-x64-Setup.exe under Assets in the latest stable release. The source-code archive and Windows Update.zip are not the graphical Setup. See download and install for the four Setup choices.
No. Normal updates preserve the password, ingestion API key, data and settings. Use Settings → Software Updates, complete the listed checks and select Accept update. Older native Windows installations without the updater service need the latest graphical Setup once, using its existing-installation update option. See Windows updates.
Fresh installations and activated migration targets from v0.1.53 set it up automatically on systemd Linux hosts. Existing matching helpers are kept. For an older installation without a helper or a setup warning, run ./alpr-community agent install as the normal installation owner; it also enables startup after reboot and verifies readiness. It may request sudo permission once. Hosts without systemd can keep the terminal updater or use their existing service supervisor. See Linux browser update recovery.
localhost refers to the computer running the browser. Another device needs the ALPR computer's LAN address, application port and enabled local-network access. Follow Windows network access; keep the database port local.
From v0.1.55, use Settings → General → Windows connection ports → Local PostgreSQL port. Select an unused port different from the application port, then choose Change PostgreSQL port and restart. Finish pending software updates first. Browser and Blue Iris URLs stay the same; PostgreSQL stays local. A conflict leaves ALPR running, and a failed or interrupted restart restores the previous database configuration. See Windows port guidance.
The shared layout adapts to browser width and zoom. A narrow view uses a horizontally scrolling Settings navigation bar. Maximize the browser or adjust zoom to reveal the wider sidebar layout.
Verify Settings → Release on the target computer after Setup completes. Preserve the installed data, recovery folders and indicated support log. Follow interrupted-update recovery or row-count validation guidance. Keep antivirus enabled and retain the exact filename and threat name if a file was blocked.
ReID needs a usable whole-vehicle image. Save the camera's direction profile, then configure and save the recorded LPR or overview source and its timing for each direction. Use the frame diagnostics. Plate-only, clipped, ambiguous or monochrome frames may be unsuitable. See vehicle identity. Similarity is a review aid, not identity proof.
Use Discussions for setup help and the bug form for reproducible failures. Include the version and sanitized steps. Keep credentials, real plates, imagery, private addresses and database contents out of public reports. Use private vulnerability reporting for security concerns.
Detailed guides are versioned in the Community repository. For the exact installed version, use its release tag. Public reports must exclude credentials, private plate data and imagery.