Troubleshooting

Pre-flight checks fail

Run pre-flight checks standalone to see what’s missing:

sudo detectify-scanner preflight

Each failed check includes a suggested fix command. Common issues:

Pods not starting

Check pod status:

sudo detectify-scanner status

If a pod shows a status other than Running, check its logs:

sudo detectify-scanner logs scan-scheduler

ImagePullBackOff

This means the host can’t pull container images. Verify:

1. Registry credentials are correct — run sudo detectify-scanner reconfigure to re-enter them
2. Outbound HTTPS to registry.detectify.com is allowed

CrashLoopBackOff

A component is crashing on startup. Check its logs for the error message:

sudo detectify-scanner logs -f <component>

API not reachable

If status shows API reachability as failed:

1. Check that the scan-scheduler pod is running
2. Try restarting: sudo detectify-scanner restart
3. Verify no firewall is blocking port 30000 on localhost

sudo -E breaks post-install commands

# Correct
sudo detectify-scanner status
 
# Incorrect — may cause issues
sudo -E detectify-scanner status

Credential issues

Invalid license key

The license key must be at least 8 alphanumeric characters (hyphens allowed). If validation fails during install, double-check the key from your Detectify account.

Registry authentication failed

The installer validates registry credentials before proceeding. If validation fails:

1. Confirm you’re using the correct username and password from your Detectify account team
2. Verify outbound HTTPS to registry.detectify.com is allowed
3. Try again — the installer retries up to 3 times

Changing credentials after install

Use reconfigure to update any credential without reinstalling:

sudo detectify-scanner reconfigure

Reinstalling

To start fresh, uninstall first and then install again:

sudo detectify-scanner uninstall
sudo ./detectify-scanner install