VAO PUSH / GUIDES
Self-hosting
Choose how to connect, then follow the installer.
01 · Prepare a Linux server
The server targets Linux amd64 / arm64 with systemd, Python 3, and Docker Engine. Choose a server you can administer and make the selected API and Web ports reachable from your devices.
02 · Choose a connection method
| Method | What you need | When to use it |
|---|---|---|
| IP + HTTP | A public IP and selected ports | No domain needed; unencrypted transport requires a suitable network |
| Domain + automatic HTTPS | DNS and port 80 for certificate validation | Caddy obtains and renews certificates; check for existing port use first |
| Existing HTTPS reverse proxy | Access to your proxy configuration | Services bind to loopback; the Web origin must also proxy /v1/ |
| Your own certificate | A valid certificate and securely stored private key | You manage the certificate and its renewal |
The App uses the API address; your browser uses the Web address. These can differ when separate ports are used. A unified HTTPS proxy can expose both under one domain.
03 · Run the installer
When the public release is available, download the prebuilt bundle for your CPU architecture, extract it, and run this command from its directory:
sudo bash install.sh| Installer choice | Default |
|---|---|
| Language | Chinese, with English available |
| API port | 8188 |
| Web port | 18188 |
| Initial admin password | Random 24-character password; store it securely |
| Connection mode | IP + HTTP |
The installer displays the App address, Web address, and initial admin details. Upgrades preserve existing passwords and data. The installer does not disable your firewall; allow the selected ports in both the server firewall and provider security group.
04 · Connect the App and open the Web console
- Add the server address and a device name in the App to connect.
- Open the Web address and sign in with your admin details. Connecting the App does not require the Web admin password.
- Choose message recipients and send a message, or create a data source and card.
Ordinary users do not enter Apple push private keys in the Web console. The official installer will provision the push identity that matches the official client; this remains part of release preparation.
Operations and public documentation
The operator is responsible for system updates, access control, business credentials, and backups. Backups may contain secrets and should be stored separately with encryption. Back up before upgrading; reverting a program is different from reversing a database migration.
Source and installation documentation are available on GitHub. The official installation bundle is still being prepared; refer to this page for current availability.
Read full installation documentation