Skip to main content

Diagnostic Commands

Common Issues

Check the logs:
Common causes:
  • APP_KEY not set → The entrypoint generates it automatically. If it persists, run:
  • Database not ready → Ensure PostgreSQL is healthy:
  • Permission issues → Fix storage permissions:
Solutions:
  1. Check outbound connectivity to license.verilock.com:
  2. Verify your license key in .env:
  3. If behind a corporate proxy, configure Docker proxy settings.
  4. Grace period is 7 days by default. If the server was unreachable for longer, restore connectivity.
Ensure PostgreSQL is running:
Check credentials match between .env and docker-compose.yml:
  • DB_HOST should be postgres (Docker service name)
  • DB_PASSWORD must match POSTGRES_PASSWORD
The default upload limit is 50MB. If you’re behind an additional reverse proxy, ensure it also allows large uploads:Nginx:
Caddy:
Horizon manages queue workers. Check its status:
If Horizon is paused:
Check failed jobs:
Retry failed jobs:
Check MinIO is healthy:
Verify the bucket exists:
If the bucket is missing, recreate it:
The AML engine needs time to download and index sanctions data on first start (~5-10 minutes).Check status:
Force a data refresh:
Quick wins:
  1. Ensure Redis is used for cache/session (not database):
  2. Check available memory:
  3. Increase PHP-FPM workers if CPU is available (edit docker/php-fpm.conf).
  4. Ensure OPcache is enabled (it is by default).

Logs

View any log:

Support

If you can’t resolve an issue:
  1. Collect diagnostics:
  2. Email support@verilock.com with the diagnostics file and a description of the issue.
  3. Enterprise customers can use their dedicated support channel.