Overview
Chrome error messages generally fall into a few buckets:
Connectivity - Problems reaching the website at all
SSL/certificates - Problems with the site's security setup
Browser state - Problems with how the page or browser session behaved
Audit actions - One error specific to ObservePoint itself
Knowing which bucket an error falls into is the fastest way to narrow down the cause.
Connectivity Errors
These errors mean the browser couldn't establish or maintain a connection to the website.
Error | What it means | What to check |
ERR_INTERNET_DISCONNECTED | There was no network connection to the website. | Confirm the target URL is reachable and not behind a VPN or firewall that blocks ObservePoint's scanning locations. |
ERR_NAME_NOT_RESOLVED | A DNS error - either the domain doesn't exist, or DNS failed to resolve it. | Double-check the URL for typos, and confirm the domain's DNS records are live and correctly configured. |
ERR_CONNECTION_TIMED_OUT / ERR_TIMED_OUT | The webpage took too long to load. | Check the page's load performance and server response time; a slow-loading page under normal load may need a longer timeout or performance fixes. |
ERR_CONNECTION_RESET | The connection was reset, usually because the IP address of the requested page changed while it was being accessed. | Look for DNS or load-balancer changes happening mid-request, or an unstable hosting environment. |
ERR_NETWORK_CHANGED | Similar to a connection reset, but caused by a change in network connectivity rather than an IP change. | Usually transient - re-run the scan; if it persists, check for network instability on the hosting side. |
ERR_CONNECTION_REFUSED | The web server refused the connection. This is a common sign that ObservePoint is being detected and blocked as a bot. | Check your bot-detection or WAF settings and confirm ObservePoint's scanning IPs and user agent are allowlisted. |
ERR_EMPTY_RESPONSE | The web server didn't send any data back to the browser. | Check server logs for the request; this often points to a server-side error or a resource limit being hit. |
SSL and Certificate Errors
These errors mean the browser couldn't validate the site's security setup.
Error | What it means | What to check |
ERR_SSL_PROTOCOL_ERROR | A configuration issue with the website's SSL certificate. | Verify the certificate is valid, not expired, and correctly installed for the domain being scanned. |
ERR_BAD_SSL_CLIENT_AUTH_CERT | An incorrect client certificate is preventing login to the website. | Confirm the client certificate configured for the scan matches what the site expects. |
Browser and Page State Errors
These errors relate to how the page or browser session behaved, rather than a network or security problem.
Error | What it means | What to check |
Aw, Snap! | Chrome's own crash notification. | Usually indicates the page caused the browser tab to crash. Check for heavy scripts, memory issues, or content that destabilizes the page. |
ERR_CACHE_MISS | The page requires a form resubmission after navigation. | Common on pages with forms; if this blocks a Journey step, review whether the step relies on browser history navigation. |
ERR_ABORTED | An operation was aborted, typically due to a user action (or, in ObservePoint's case, an action taken during the scan). | Review the audit or journey configuration for steps that might interrupt page load, such as a navigation triggered before the page finishes loading. |
ObservePoint-Specific Errors
Error | What it means | What to check |
Error: An audit action failed. | A user-configured audit action was unable to execute correctly. | Review the audit action's configuration (e.g., the selector or click target) to confirm it still matches the current page. |
FAQ
Q: I'm seeing ERR_CONNECTION_REFUSED. Does that mean my site is down?
A: Not necessarily. It's more often a sign that the site is actively blocking ObservePoint as a suspected bot. Check your bot-detection or WAF configuration before assuming the site itself is down.
Q: A page loads fine in my own browser but fails during an Audit or Journey. Why?
A: ObservePoint scans with a synthetic browser, which can be treated differently than a real visitor by bot-detection tools, rate limits, or scripts that expect user interaction. Start by checking whether the site is blocking automated traffic.
Q: What should I do if none of these explanations match what I'm seeing?
A: Reach out to ObservePoint support with the specific error message and the audit or journey where it occurred. Some errors can have more than one underlying cause.
Conclusion
Most browser error messages point to one of three places: the connection to the site, the site's SSL/certificate setup, or the way the page behaved during the scan. Start by identifying which bucket the error falls into, then work through the relevant checks above. If the error persists after ruling out the common causes, ObservePoint support can help dig into the specific audit or journey.