Choose an installation method
Choose the official package that matches the server OS and CPU architecture. Installation is not complete merely because the script had no error; the service must be healthy and the initial setup page must open.
Confirm the system and architecture first
| Server | Package identifier | Installation method |
|---|---|---|
| Linux Intel/AMD | linux-x64 |
Native systemd service |
| Linux ARM | linux-arm64 |
Native systemd service |
| Windows Intel/AMD | win-x64 |
Windows system service |
| Windows ARM | win-arm64 |
Windows system service |
| macOS Intel | osx-x64 |
launchd LaunchDaemon |
| macOS Apple Silicon | osx-arm64 |
launchd LaunchDaemon |
| Docker x64/ARM64 | docker-linux-* |
Docker Compose |
When the architecture is wrong, do not keep changing permissions or installing runtimes. Download the correct package.
Installation route
flowchart LR
A["Download the official package"] --> B["Verify version and SHA-256"]
B --> C["Extract to a temporary directory"]
C --> D["Run the packaged installer"]
D --> E["Run status"]
E --> F["Open initial setup in a browser"]
| Your environment | Continue with |
|---|---|
| Linux | Linux from extraction to first sign-in |
| Windows | Windows from extraction to first sign-in |
| macOS | macOS from extraction to first sign-in |
| Docker | Docker installation and daily management |
Prepare before installation
- A fixed installation directory; do not run long-term from Downloads.
- Persistent Config/Data directories that upgrades do not overwrite.
- A database. The Docker package can create an independent MySQL through Compose.
- A recording disk and directory plan, even if the first trial only uses live video.
- Permission to change the firewall and a network path from the browser to server port 5800.
What to do during installation
- Verify
VERSION, target architecture, and SHA-256. - Run the packaged
Deploy/<platform>installer with system administrator privileges. - For a first use, choose single-node All-in-One instead of starting with multiple nodes.
- Select the bundled media service or an existing external MediaServer.
- After installation, run
statusand check the main service, NodeAgent, database, and health URL. - Open the address printed by the script and continue to Initial setup.
The installer manages system services, directories, and containers. Initial setup configures the business database, modules, ports, recording storage, and administrator. Both stages are required before sign-in.
Success criteria
- The management script reports the main service and NodeAgent as healthy.
http://server-address:5800/healthresponds.- The browser opens initial setup and requests the current setup code.
- Config and Data are in fixed persistent directories.
- The service starts automatically after restart.
Common problems
| Symptom | Check first |
|---|---|
| Program cannot execute | Whether package architecture matches and files are complete |
| Port 5800 cannot be opened | Service status, listen address, host firewall, and cloud security group |
| Service runs but page is blank | Whether WebUI files came from the complete package and whether static assets return 404 |
| Docker keeps waiting for MySQL | MySQL container health, data-directory permissions, and free disk space |
| No initial setup page after install | Whether an old Config or installed lock was reused |
Do not use uninstall --purge for ordinary troubleshooting. It may remove persistent data. Check status and logs first.
Next step
When the page opens, continue to Follow the initial setup wizard.