Diagnostic Commands
Common Issues
Container keeps restarting
Container keeps restarting
Check the logs:Common causes:
APP_KEYnot set → The entrypoint generates it automatically. If it persists, run:- Database not ready → Ensure PostgreSQL is healthy:
- Permission issues → Fix storage permissions:
License validation failed
License validation failed
- Check outbound connectivity to
license.verilock.com: - Verify your license key in
.env: - If behind a corporate proxy, configure Docker proxy settings.
- Grace period is 7 days by default. If the server was unreachable for longer, restore connectivity.
Database connection refused
Database connection refused
.env and docker-compose.yml:DB_HOSTshould bepostgres(Docker service name)DB_PASSWORDmust matchPOSTGRES_PASSWORD
File upload fails (413 error)
File upload fails (413 error)
The default upload limit is 50MB. If you’re behind an additional reverse proxy, ensure it also allows large uploads:Nginx:Caddy:
Queue jobs not processing
Queue jobs not processing
Horizon manages queue workers. Check its status:If Horizon is paused:Check failed jobs:Retry failed jobs:
MinIO / Storage errors
MinIO / Storage errors
Check MinIO is healthy:Verify the bucket exists:If the bucket is missing, recreate it:
AML screening returns no results
AML screening returns no results
The AML engine needs time to download and index sanctions data on first start (~5-10 minutes).Check status:Force a data refresh:
Slow performance
Slow performance
Quick wins:
- Ensure Redis is used for cache/session (not
database): - Check available memory:
- Increase PHP-FPM workers if CPU is available (edit
docker/php-fpm.conf). - Ensure OPcache is enabled (it is by default).
Logs
| Log | Location | Description |
|---|---|---|
| Application | storage/logs/laravel.log | Main application log |
| Horizon | storage/logs/horizon.log | Queue worker log |
| Scheduler | storage/logs/scheduler.log | Cron scheduler log |
| Nginx | Docker stdout | Web server access/error log |
| PostgreSQL | Docker stdout | Database log |
Support
If you can’t resolve an issue:- Collect diagnostics:
- Email
support@verilock.comwith the diagnostics file and a description of the issue. - Enterprise customers can use their dedicated support channel.

