Cannot reach project URL

Bot challenge (Cloudflare / hCaptcha)

Cloudflare, hCaptcha, or a similar bot-protection layer intercepts Wolfix's headless browser and serves a challenge page instead of your app.

62%

of cases

How to fix

Wolfix identifies itself with a real browser user agent, but aggressive bot-protection tiers can still block an automated visitor before your app ever loads.

To let Wolfix through:

1. In your Cloudflare dashboard, open Security → Bots and set bot-fight mode to Off for the duration of the scan.
2. Alternatively, add an IP allow-list rule for the scanner — the source IP is logged in your report under the connectivity check.
3. Re-run the scan. The live-URL checks proceed once the challenge is bypassed.

You can re-enable bot protection the moment the scan completes — Wolfix only needs a single clean fetch.

DNS has not propagated

A newly registered or recently changed domain has not finished resolving across global DNS, so the scanner cannot find your host.

23%

of cases

How to fix

If you connected a custom domain in the last day or two, DNS records may still be propagating. Wolfix gets a resolution failure and aborts the live-URL check.

To verify and fix:

1. Check propagation with a tool like dnschecker.org. If the record hasn't resolved in most regions, wait — full propagation can take up to 24–48 hours.
2. Confirm the A / CNAME record points at the right host at your DNS provider.
3. Once the domain resolves globally, re-run the scan. In the meantime you can scan the platform-provided URL (for example a Lovable preview link) instead.

HTTPS is misconfigured

The certificate is missing, expired, or served for the wrong hostname, so the scanner's secure connection fails before any page loads.

11%

of cases

How to fix

Wolfix connects over HTTPS. An expired certificate, a hostname mismatch, or an incomplete certificate chain causes the TLS handshake to fail.

To diagnose:

1. Open your URL in an incognito window and look for a certificate warning in the address bar.
2. Run curl -vI https://yourproject.example.com and check for certificate verify failed or a hostname-mismatch error.
3. Reissue or renew the certificate at your host (most platforms do this automatically once the domain resolves), then re-run the scan.

A geo block is rejecting the scanner

A firewall or WAF rule restricts traffic by country or region, and the scanner's egress region is outside the allow-list.

4%

of cases

How to fix

Some projects restrict access to specific countries at the firewall or WAF layer. If the scanner's egress region isn't on the allow-list, the request is refused before it reaches your app.

To fix:

1. Review the geo rules in your WAF or firewall (Cloudflare WAF, AWS WAF, or your host's equivalent).
2. Temporarily widen the allow-list, or add an exception for the scanner's source IP shown in the connectivity check.
3. Re-run the scan, then restore your original geo rules once it completes.