Skip to main content

Troubleshooting scans and CI checks

Fix the common Pentrova problems: domain not verified, sign-in failures, codes and CAPTCHAs, sessions that expire, scope, plan errors, and incomplete results.

Reading mode

Most problems fall into a few groups. Find the symptom, then apply the fix.

The domain is not verified#

Symptom. You cannot start a scan for a URL, or a CI check returns 403 (target outside your verified domains) or 409 DOMAIN_RECHECK_FAILED.

Fix. Ask an Owner or Admin to open the Targets page and check that the root domain is verified and that verification has not expired after 90 days. If the DNS TXT record, meta tag or /.well-known/pentrova-verify.txt file was removed, put it back and verify again. Re-verification checks the same record, so leave it in place.

The scan cannot reach the host#

Symptom. The scan ends with little or nothing tested.

Fix. Pentrova tests from the internet. A host that is reachable only over a VPN or a private network cannot be tested. Use a staging host that is publicly reachable and protected by its own test accounts, and check that a firewall or bot protection is not blocking the requests.

Sign-in fails#

Symptom. Test sign-in fails, or an authenticated scan reports that it could not sign in.

Fix.

  • Run Test sign-in and watch the live view: it shows the page the sign-in sees.
  • Check the test account in a normal browser. Accounts that are locked, expired or awaiting a password change cannot sign in.
  • If the sign-in page is not found automatically, enter its URL under Advanced.
  • Choose the right sign-in method: Password, Code by SMS or Code by email. If a password account also uses an authenticator app, paste its Base32 setup key in the TOTP Secret field, not a six-digit code.
  • For SMS and email codes, type in the code that arrives while the scan waits.
  • A CAPTCHA on the sign-in page needs CAPTCHA solving, which paid scans can use unless India-only processing is on. Free pentests never use it. Use a staging sign-in without a CAPTCHA where you can.

Configuring authentication covers each method.

The session expires during the scan#

Symptom. The first part of a scan is signed in and later results look like a signed-out user’s.

Fix. Add a session check under Advanced: a URL only a signed-in user can load, and the text or CSS selector that appears on it. When the text disappears, Pentrova signs in again.

Too little or too much was tested#

Symptom. Pages you expected are missing, or the scan spends time on parts you did not want tested.

Fix. Check the crawl scope regex under Advanced: only matching URLs are tested, so a narrow expression leaves pages out. Use the traffic exclusion list to keep URLs out of the recorded traffic. For API scans, check which endpoints are selected and that the base URL matches where the API runs.

A CI check does not start#

ResponseWhat to do
202 with status: "queued"Wait and poll the status endpoint. fair_use_review means this month’s CI checks for the target are used up; the request is reviewed within one working day.
402 CI_REQUIRES_PLANCI checks need a Continuous plan for the target. See the pricing page.
402 PLAN_PAUSEDThe target’s plan is paused until its invoice is paid.
402 PLAN_ENDEDThe plan has ended.
401The API key is missing, invalid, expired or revoked, or its creator has left the organization.
403The key lacks scan:create, the host is outside your verified domains, or the account needs action first (for example MFA_SETUP_REQUIRED).
429Too many requests. Retry after the Retry-After header’s seconds.
422The body is invalid: check target_url, scan_type and the fail_on object.
503Retry after the number of seconds in the Retry-After header.

The full list is in the CI API reference.

The pipeline fails with a network error#

Symptom. The CI job fails while the check itself finishes in Pentrova.

Fix. Start the check with "wait": false and poll /api/ci/scan/{scan_id}/status. Holding one request open for the whole check fails behind proxies and load balancers that close idle connections. The CI/CD guide shows the polling loop.

The status is incomplete#

Symptom. A scan or CI check ends as incomplete.

Fix. incomplete means the scan finished but did not run cleanly, so its results may not cover everything. Open the scan from scan_url to see what happened, fix the cause above (usually sign-in or reachability), and run it again.

Still stuck#

Contact support through the contact page and include the scan ID. It is in the scan’s URL and in every CI API response.

Last updated: November 20, 2026

Was this page helpful?

Site search

↑↓ navigateEnter openEsc close