Troubleshooting One and Out Audits

Typically audits will complete without issue. Occasionally an audit may only scan the starting page(s). Sometimes these are referred to as "one and out" audits. Below is a list of common reasons and resolutions to this problem.

Issues Relating to Include and Exclude Lists

Problem: Bad starting page(s).

Resolution: Verify Starting Pages are valid and accessible. If pages are accessible check audit Include and Exclude Lists.

Problem: Starting page redirects to another site that is not allowed in the Include List.

Resolution: Replace Starting Page, delete the Include List, then save the audit. ObservePoint will automatically recreate the default Include List based on the Starting Page.

Problem: Incorrect audit Include or Exclude Lists.

Resolution: Reset the lists by deleting everything from the Include/Exclude fields on the audit's Advanced tab, then save the audit. ObservePoint will automatically recreate the default audit filters based on starting pages.

Problem: Much of the content could have a different top level domain (TLD) than that of the starting page(s). For example, if http://tw.domain.com was listed as the starting page but most of the content of the site was on http://www.domain.com.tw, our default include filter will prevent the .com.tw TLD from being audited. To resolve this, add an additional include filter allowing for domain.com.tw.

Problem: No document object map (DOM) links. This could be that there are simply no links on the site or that one of the include/exclude list items is preventing discovered pages from being audited.

Resolution: Verify that the site has links, if necessary check the DOM by opening the developer console of your browser and typing document.links. If there are no links or the output reads unavailable then you may need to list several URLs as additional starting pages. If the site has links, verify that the links are permitted to be audited by the Include and Exclude Lists.

Web Server Related Issues

Problem: ObservePoint has been banned from accessing the site. This may happen if the website employs very strict security policies designed to protect the site from denial of service attacks and other nefarious behaviors.

Resolution: Ask your IT security team to whitelist the ObservePoint IP range and re-run the audit.

Problem: Site is unavailable.

Resolution: Ensure the site is up and responsive before starting an audit. You may need to run with reduced server load enabled on the audit (see Advanced Audit settings tab).

Problem: Site is behind a firewall, this is common for Development, QA and Staging webservers.

Resolution: Ask your IT security team to allow HTTP/HTTPS from our IP range to your protected sites. See the whitelisting document for IP addresses.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.