Scanning failed – How to Fix the Error
Last updated on 12 November 2024
If you have come across a “Scanning failed” error on WebYes, worry not – there are easy fixes. In this guide, we’ll walk you through some quick and simple steps to sort it out, so you can continue scanning without any hassle.
How to Fix the “Scanning failed” Error
The “Scanning failed” error is most likely caused by geo-blocking restrictions, redirect issues, AWS IP blocking, or an incorrect URL. To resolve the issue, follow the troubleshooting steps below – one of them should fix the problem.
Check for Geo-blocking Restrictions
Verify if your website has geo-blocking enabled. Allow access from WebYes server regions or temporarily disable geo-blocking for the scan.
Review Redirect Configurations
Ensure your website’s redirects are set up correctly (e.g., HTTP to HTTPS) and eliminate any excessive or improper redirects.
Whitelist AWS IPs
Check if AWS IP addresses are blocked by your website’s security settings. Whitelist WebYes’ AWS IP ranges to allow scanning.
Verify the URL
Double-check that the URL is correct, including the protocol (http/https) and domain/subdomain. Ensure the URL directs to the intended page.
If All Else Fails, Contact Support
In some cases, the issue may be caused by factors not covered above, and the troubleshooting steps might not resolve it. If that happens, reaching out to our support team is your best option. We’re here to help get things back on track quickly.