Common issues when loading the PRO image or running compliance reports, and how to fix them.

Not finding your issue here?

Ping us on Discord or email [email protected] with the error message — we'll fix it same day.

Telemetry

PRO includes anonymous usage telemetry — what commands ran, duration, whether the report generated. Nothing from your target environment (no domains, IPs, usernames, findings). This is what lets us fix your issues same day.

To disable: run telemetry off inside ADscan, or set ADSCAN_TELEMETRY=0 in your environment.

Sending us a bug report

If none of the above fixes it, run with --debug and send us the output:

ADSCAN_DOCKER_IMAGE=adscan/adscan-pro:latest adscan ci \
  --domain <domain> \
  --dc <dc_ip> \
  --username <user> \
  --password <pass> \
  --generate-report \
  --frameworks iso27001 \
  --debug \
  --keep-workspace 2>&1 | tee adscan-debug.log

Send adscan-debug.log to [email protected] or paste it in Discord. We'll respond same day.

Troubleshooting

Sending us a bug report

On this page

Troubleshooting

docker load fails: 'no space left on device'

docker load succeeds but the image isn't visible

adscan still uses LITE after loading the PRO image

'Cannot connect to the Docker daemon'

Report generation fails: 'Report License not found'

Permission denied on output directory

Scan completes but no report.pdf in the workspace

BloodHound CE won't start (OOM / exit code 137)

Kerberos clock skew error

Re-generating the deliverable kit

Sending us a bug report

On this page