Troubleshooting

Resolve setup and licence errors

Check the installation boundary, HTTPS identity and signed package without resetting business data.

Platform
Laravel / PHP
Laravel
13
PHP
8.4
Database
Dedicated MySQL-compatible production database

Setup does not start

Confirm the web root points only to public_html/ and that the private sibling is present. Check the web and CLI PHP 8.4 executables, required extensions, HTTPS/proxy handling and private storage permissions. Use the setup key generated for this installation.

An existing .env or nonempty database deliberately prevents fresh setup. Do not delete the environment, setup state or business database to make the installer start again. Investigate the interrupted operation using its matching recovery instructions.

Staff are signed out or ordinary pages are locked

Check the canonical URL/domain, entitlement product and purchased version, installation public key, actual signed expiry and verified outbound TLS. Correct the cause through the licence recovery page after normal staff authentication/MFA.

The licence status command reads local signed status without contacting the authority:

php artisan emailabiller:licence status

Use the private application directory and matching PHP executable. Do not share raw private licence configuration, setup codes or keys. Avoid changing the server clock to extend a permission; clock rollback is detected.

Integrity fails before sign-in

A changed signed file can fail before sessions boot. Restore the verified matching release through its approved recovery process. Editing the inventory, disabling verification or regenerating keys is not a repair.

← All EmailaBiller guidesGet help →

Need help with EmailaBiller?

Tell us the product version and what you are trying to do. Keep passwords and private keys out of your message.

Contact Emaila