Learn / Operations
Operations · CERTSKOPE 0.6.15
Troubleshooting by symptom
Start with the exact stage and error, then check the dependency.
CA policy returns 400
Create an enrollment group before creating its policy. Select at least one group and enabled CA. Missing names, invalid OIDs or reversed IP ranges produce specific validation errors. Reopen the form after changing the available groups.
IPv4 or IPv6 enrollment fails
Use the IP SAN field, not DNS SANs. The IP common name must be included there. Remove brackets, ports, network prefixes and scope IDs. The selected CA/template and enrollment policy must also allow the request.
Private export unavailable
Check for a matching managed key, its export policy and your ExportPrivate permission. Discovery and public CA imports do not retrieve private keys. Import an original matching PFX/P12 or request a replacement.
Scan has no useful result
Check approved scope and ports, application-server DNS, exclusions, filter rules and endpoint reachability. Do not infer revocation from a TLS handshake. A domain scan does not enumerate subdomains.
SMTP test fails
Verify saved settings rather than unsaved form edits. Check host/port, authentication, relay authorization, certificate trust and client-key permissions. A timeout may leave delivery uncertain; check relay logs before resending.
Deployment stays queued
Check approval and execution state, agent polling/last-seen, service identity, target allowlist, key availability and the receipt. A stored certificate and a bound IIS endpoint are separate outcomes.
Continue exploring
This guide describes CertSkope 0.6.15. A saved integration profile alone does not activate an external connector. See feature availability.