Troubleshooting
Common issues when pulling the PRO image from the registry 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
The PRO command-line tool sends usage telemetry: which commands ran, how long they took, whether the report generated, and a pseudonymized recording of the terminal session. Domains, IPs, hostnames, usernames, SIDs and hash material are replaced with deterministic pseudonyms before anything leaves your machine, and the upload is aborted if that step fails. This is what lets us fix your issues same day. Full detail, including the endpoints: Telemetry.
To disable: run set telemetry off inside ADscan for the current workspace (add global for the operator-wide default), or set ADSCAN_TELEMETRY=0 in your environment. For an engagement where nothing may leave the client network, use --offline. The Enterprise appliance is a separate deployment and is air-gapped by default; none of this applies to it.
Sending us a bug report
If none of the above fixes it, run with --debug and send us the output:
ADSCAN_DOCKER_IMAGE=ghcr.io/adscanpro/adscan-pro:latest adscan ci auth \
--type audit \
--interface eth0 \
--domain <domain> \
--dc-ip <dc_ip> \
--username <user> \
--password <pass> \
--generate-report \
--frameworks iso27001 \
--debug \
--keep-workspace 2>&1 | tee adscan-debug.logSend adscan-debug.log to [email protected] or paste it in Discord. We'll respond same day.