Skip to content
CheckView
Get Started

Navigation Blocked

Error: “Navigation blocked”

Code: navigation-blocked

This error means a step in your test flow tried to open an address that CheckView does not allow. The test stops at that step, and the error message tells you which rule the address broke.

What Addresses Are Blocked

CheckView tests run on CheckView’s own infrastructure, so they can only visit public websites. A step is blocked when its URL points to:

  • A private or internal network address, such as 10.0.0.5, 172.16.0.1, 192.168.1.10, or localhost / 127.0.0.1.
  • A link-local or metadata address, such as anything in the 169.254.x.x range.
  • A domain name that resolves to one of the addresses above. The check applies to where the domain actually points, not just to how the URL looks.
  • A URL with a username and password embedded in it, such as https://user:pass@example.com.
  • An address that is not a web page, such as a file: or ftp: URL. Only http and https are allowed.

How to Fix It

  1. Open the test flow and find the step that failed. It is usually a Go to URL step.
  2. Check the URL in that step. Look for a typo, a leftover local or development address, or a staging address that is only reachable from inside your network.
  3. Replace it with the site’s public address, the same one a visitor would type into their browser.
  4. If the URL has a username and password in it, remove them. For a password-protected staging site, contact support and we will help you find a way to test it.
  5. Save the step and run the test again.

Is It Retried Automatically?

No. A blocked address will be blocked again on every attempt, so CheckView does not retry these failures automatically. Fix the URL, then run the test again.

When You See a Page-Load Error Instead

Some problems with a step’s URL are reported as a page-load error rather than Navigation Blocked:

  • The domain could not be looked up, for example because it does not exist or its DNS is not set up yet.
  • The URL is not valid once its variables have been filled in.

See “The page did not fully load after 60 seconds” Error for how to troubleshoot those.