The website fails before setup
Confirm the domain points only at the release's public/ directory. Check 64-bit PHP, extensions and writable private config/ and storage/. Run php bin/install.php --check as the PHP user if terminal access is available. A private diagnostic-storage error usually needs an ownership or permission fix, not public error display.
Database or interrupted setup fails
Use a dedicated empty database, full hosting-prefixed names and the required TRIGGER privilege. Do not import schema first. If setup was interrupted, retain config/install-state.json and config/accounts.php.pending where present. Rerun the exact release using the same database, URL, administrator and business inputs as directed by its recovery instructions.
The installer validates existing table definitions and original keys for a supported retry. Never delete pending state or keys to force setup into nonempty data. Use a genuinely new empty database or restore a matching full backup instead.
The setup key expires
Reload the uninstalled setup page to generate a fresh one-hour private key, then read storage/setup/setup-key.txt in File Manager. An unlocked browser has a twenty-minute window. Existing installations stay locked; deleting a lock is not account recovery.
Product licence cannot activate
Check the canonical domain, entitled version, server clock and verified outbound HTTPS to the licensing API. For a first installation, follow the preparation-kit flow before downloading the product ZIP. Check CLI extensions, the same Unix user for CLI/web PHP, and the ORBIT_LICENSE_CONFIG path in both runtimes. Preserve the prepared private directory; do not generate another identity because the web process cannot read its configuration. Existing browser-prepared installations should retain their original external path and matching recovery process.
After a temporary outage, restore a genuine healthy permission and sign in freshly. Permanent revocation requires issuer resolution. An integrity 503 requires the exact signed release bytes, not editing checks.
Email or payment outcome is uncertain
Review Email centre, private logs and the provider's actual result before retrying. Check the separately scheduled workers. Share only a sanitised reference, version and reproduction steps with support; never share setup codes, identity keys, merchant credentials or database dumps.