DoesQA runners reach your site from the public internet. If the Open step cannot load the URL, allowlist the runner IPs, confirm the host is publicly reachable, and check whether a bot challenge is blocking the session.

  1. Confirm the Open URL is reachable from the public internet. A localhost or 127.0.0.1 address on a local machine is not reachable from DoesQA runners unless you expose it with a tunnel such as ngrok. The same applies to hosts that exist only on a private network or VPN.
  2. On your firewall, WAF, or IP allowlist, add the DoesQA runner IPs: 
    18.130.52.75
18.170.153.192
    If support will open the site with you, also allow: 
    89.32.127.20
83.151.231.56
155.133.21.62
  3. Re-run and open the Open step responses. Look for the IP allowlist hint and any timeout or navigation message.
  4. If the site uses Basic Auth, set it on the Open step (URL or Header mode) rather than relying on a browser password prompt.
  5. If a captcha or bot wall appears in screenshots, point the Flow at a test environment that does not challenge automation, or allowlist the runner IPs in that product’s bot settings.
  6. Start a new Run after the allowlist or URL change. Existing Runs keep the earlier result.

If Open still fails after the host is public and the IPs are allowlisted, open Help in DoesQA and select Create new ticket. Include the Run ID.

Related docs: Whitelisting IPs, Open.