Setup will not open or cannot write files
Confirm the domain points to the extracted Desk directory and PHP meets the requirements. Include hidden denial rules, but keep /install/ publicly reachable during fresh setup. Check that uploaded files and web PHP use the same Unix owner and PHP can write app/ and storage/. Do not solve ownership issues with 777 permissions.
The key expired or the browser was lost
The setup key lasts one hour. An unlocked browser has a twenty-minute window. Wait for that window to expire, reload setup and read the new private storage/setup/setup-key.txt. Never publish that file or paste its key in a support post.
Database rejected or installation interrupted
Use the full hosting-prefixed database and username and check the database host and privileges. Desk refuses every nonempty database, even a manually imported empty schema. MySQL schema changes are not transactional. For a failed fresh setup, recreate only that new, disposable installation database before retrying. Never reset a database with real records.
Staff cannot sign in
Use the local /admin/master/login.php, not the Orbit password. Check that the account is active and has the expected permissions. A password change invalidates older sessions; sign in again. Do not remove installation locks as a password recovery technique.
Forms are empty or emails are missing
Check active country/business/service routing and create a vacancy before testing jobs. Review SMTP enablement, sender credentials, Email Logs and the recipient's spam folder. Consult System Health and private storage/logs/ diagnostics. Share only the relevant error/reference, product version and steps; remove credentials and customer information.