Skip to main content

Unable to Access Test Site

When a SeeTestAutomation Chrome browser opens a test site, the page can fail to load if Chrome blocks local or private network resources.

You may see:

  • the Local Network Access prompt
  • blocked requests to local or private network resources

Cause​

Chrome 120 and later include a security policy that can block requests from an HTTPS site to resources on a local or private network.

If your test site is served over HTTPS and tries to access resources on:

  • a private IP address
  • a local server such as localhost

Chrome treats the request as a potential security risk and blocks it by default. Standard Selenium or WebDriver settings may not override this behavior.

Solution​

For test execution only, disable the Chrome Local Network Access security check.

info

This configuration must be applied in your test automation code where the Chrome browser is initialized.

Update Chrome options​

Add this argument when initializing the Chrome browser:

ChromeOptions options = new ChromeOptions();
options.addArguments("--disable-features=LocalNetworkAccessChecks");
WebDriver driver = new ChromeDriver(options);

Disable additional network checks​

If the issue persists, add this argument as well:

options.addArguments("--disable-features=PrivateNetworkAccessSendPreflights");

Last updated on