Back to Troubleshooting Guides

Introduction

In this guide, we’ll give you more information on why specific pages fail during site scans on AAArdvark and instructions on what to do when this happens.

Filtering Pages with Scan Errors

In the Pages page within your site dashboard, select the All Filter button and select the Pages with Scan Errors checkbox. This will instantly give you an overview of all the pages that failed to scan.

Pages with scan errors checkbox selected in the All Filter menu.

Page Scan Failed

In the case that one or more pages failed during the scan, there are a few reasons that may cause this issue. In the Pages page, hover over the View Details button with your mouse to see a brief overview of the error details.

If a code is listed, you can check out the HTTP status codes below for some clues:

  • 400 Bad request: The server can’t process the request to access the URL, which can be caused by incorrect URL syntax.
  • 401 Unauthorized: Authentication is required, AAArdvark will need login credentials for the page.
  • 403 Forbidden: The server refuses access to the page, which could be due to authentication issues or the page is private.
  • 404 Not found: The page could not be found on the server.
  • 410 Gone: The page was permanently removed.
  • 500 Internal Server Error: This is a generic error message from the website’s server. You may have to check with your host to see a more detailed error.
  • 502 Bad Gateway: The server is set up as a proxy, and the upstream server for the website is not responding.
  • 504 Gateway Timeout: The server is set up as a proxy, and the website’s upstream server is not responding in a timely manner.
Hovering over the View Details button for the failed page scan and a tooltip shows, "Bad response code: 404".

Otherwise, general reasons for pages to return errors during scans include:

  • The Page is Not Published: The page may still be in draft mode. Make sure that it’s published and can be visited even if you’re not logged into your website.
  • The Page is Offline: It might be temporarily unavailable. Does that specific page load in a separate tab?
  • Network Connection Issues: The internet connection may be unstable and cannot reach AAArdvark servers. Can you load a different webpage successfully?
  • Page URL is Incorrect: The page you’re scanning may not exist. Double-check to make sure the full URL is entered correctly in AAArvark. Or, check to see if the page has moved to another page location.

If none of these suggestions are helpful, please contact our support team right away so that we can review them. In the meantime, you can also Retry the Scan after a few minutes to see if that helps.


Still stuck?

File a support ticket with our five-star support team to get more help.

File a ticket

  • Please provide any information that will be helpful in helping you get your issue fixed. What have you tried already? What results did you expect? What did you get instead?
  • This field is for validation purposes and should be left unchanged.

Related Guides