---
title: "[50011] Connection Failure While Using Chrome Browser"
slug: "50011-connection-failure-while-using-chrome-browser"
updated: 2023-01-19T21:19:20Z
published: 2023-01-19T21:19:20Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# [50011] Connection Failure While Using Chrome Browser

## Overview

If a test running on the Chrome browser reports a **[50011] Connection Failure**, it means that the TCP connection failed. This error message comes through our Windows API library on Catchpoint nodes.

## Explanation

While Catchpoint does not show the same error message as the browser, the error message does display something similar. In the below screenshot, the Chrome browser displays the error: **ERR_CONNECTION_TIMED_OUT**.

![](https://cdn.document360.io/cb4af8f9-6751-4fd2-b39c-07aae832badb/Images/Documentation/202895943-50011_Error.png)

Chrome returns a message, such as **net::ERR_CONNECTION_FAILED** if the connection failed. This message shows up in both the Chrome waterfall and HAR files. There is no Chrome-equivalent error message in Catchpoint.

## Troubleshooting

The "Debug Primary Host" option will run the traceroute to the original host. However, information from request overrides is not accessible through the "Debug Primary Host" feature. To collect this data, please use the **DNS override** option instead. Error code 50011 is agent-specific. Since Catchpoint nodes use the Windows API library, the MS error code is displayed as well, but anything that starts with 5XXXX is a node-specific error.

**Note:- Some of the Error codes like 50011 and 50014 can be both Client-side and Server-side.**

## See also

A list of Catchpoint's error codes can be found [here](https://docs.catchpoint.com/docs/Error-Code-by-Monitor-Type).