Setup or database checks fail
Run the browser requirement checks or php bin/install.php --check as the PHP user. Confirm all required extensions, full hosting-prefixed database names and database privileges. Use a new empty database, not a manually imported schema. Check file ownership and writable config/ and storage/; do not make them world-writable.
If the setup key expired before installation, follow the limited key renewal procedure in installation. Never remove installed configuration or locks to rerun setup. For an interrupted install, follow the exact release guide and preserve any original keys.
Preparation or the existing identity cannot be read
Use the installation preparation guide before the first product download. Check CLI PHP extensions, the same Unix user for CLI/web PHP, the private directory's ownership and the actual ORBIT_LICENSE_CONFIG value in each runtime. A shell-only setting does not reach the web process.
Preserve an already activated identity. If the product offers to prepare another key, restore access to the intended configuration first. For an existing browser-prepared installation, retain its original external directory and follow that release's owner-password recovery flow. Do not put private identity files under the web root.
Activation or refresh fails
Check the configured canonical HTTPS domain, exact product/version entitlement, server clock, certificate trust and outbound access to https://license.emailaorbit.com/api/licensing/v1. Use the setup code for this installation's public key. Preserve the key after a failed activation.
For a temporary outage, restore connectivity and use Check existing licence, then sign in freshly after genuine permission is healthy. Expired signed permission is not extended by an outage. Permanent revocation needs the issuer's resolution and cannot be undone by replaying an old setup code.
A 503 integrity error appears
Restore the exact complete signed release. Do not repair the inventory or alter guard files. Keep configuration, data and identity backups intact. Share only the version, relevant non-secret reference and reproduction steps with support; exclude setup codes, keys, passwords and customer records.