Diagnosing Security Lockdowns & Error Codes

To protect your application from unauthorized access and code manipulation, our software features an automated, multi-layered verification engine. If the system detects missing files, invalid environments, or configuration anomalies, it will initiate a protective lockdown.

If you encounter a lockdown screen, reference the error codes below to resolve the issue:

Standard Action Required Screen

• Cause: The system detected an expired license, a suspended account, or a Domain Mismatch (the software is running on a different URL than the one registered to the license).

• Resolution: Enter a valid license key into the provided interface. If you recently migrated your application to a new server or domain, you must log into your Client Dashboard and click "Reset Lock" on your license to free the domain bind before entering the key again.

Error Code: SEC_TAMPER_0x1

• Cause: The system is missing critical core SDK components required to connect to the licensing servers.

• Resolution: Ensure your installation is complete. Verify that the AppClient.php file exists in your core application directory and that your server permissions allow PHP to read it.

Error Code: SEC_TAMPER_0x2

• Cause: The application's routing sequence was interrupted, or there is a severe synchronization mismatch between your server's system clock and the application's localized timezone.

• Resolution: Ensure your server time is correctly synchronized. Additionally, verify that your core configuration files are loading in the correct sequence as outlined in your installation manual.

Error Code: SEC_TAMPER_0x3

• Cause: The secure database wrapper was unable to authenticate. This usually occurs if core security files (such as the verification checklist) have been deleted or manually altered.

• Resolution: Restore your installation from a clean backup. Ensure that no core framework files have been modified or removed from the root or public directories.

If you cannot resolve a lockdown using these steps, please log a support ticket immediately so our engineers can assist you.