Troubleshooting

Start with the error time, requested URL, and request ID. Do not enable detailed exception output on a public production site.

HTTP 500

Check internal_data/logs and the web server error log for the same timestamp. Common causes include incorrect permissions, an unavailable database, a missing PHP extension, stale cache, or an interrupted update.

HTTP 422 during settings upload

Check that the SaaS panel can reach the client domain, the HTTPS certificate is valid, the installation is enrolled, and the connection check succeeds. If the installation identity was lost, revoke it and enroll again.

Blank page or missing template

Clear cache in the local client admin. After an update, wait for the data rebuild to finish and confirm the update was not interrupted. Do not create missing production templates manually.

Installer reports file permissions

Check the PHP process owner and permissions on src, data, and internal_data. Assign the correct owner and minimum required access instead of using chmod 777.

Update cannot be downloaded

Check runtime requirements, free disk space, and outbound HTTPS access to the update server. If the installation is reported as not enrolled, generate a new one-time code in the project card.

Information for support

Provide the domain, project ID, error time, action, current version, request ID, and a sanitized log fragment without passwords, PINs, tokens, or payment details.