Understand Umbrella Connector Error "Register() fail: The underlying connection was closed: An unexpected error occurred on a receive."

Available Languages

Download Options

PDF (17.1 KB)
View with Adobe Reader on a variety of devices

Updated:September 24, 2025

Document ID:225011

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

Overview

Explanation

Introduction

This document describes the Umbrella Connector error "Register () fail: The underlying connection was closed: An unexpected error occurred on a receive."

Overview

You notice that the Umbrella Connector service is displaying an error status on the Dashboard or does not appear in the dashboard and when looking in the Connector logs you see these errors:

1/30/2018 8:39:44 PM:Register() fail: The underlying connection was closed: An unexpected error occurred on a receive.

Note: The connector logs are located here: C:\Program Files (x86)\OpenDNS Connector\v1.x.x\OpenDNSAuditClient.log

Explanation

This error is similar to this "Please validate that https://support.umbrella.com/hc/en-us/articles/230902528-Umbrella-Connector-error-The-underlying-connection-was-closed-Could-not-establish-trust-relationship is not also being seen and start there."

There are several possible causes for .NET to fail to reach the Umbrella API server even when the network is wide open. These causes are due to the .NET HTTP call via the .NET crypto API v2. To resolve this issue, use these steps:

Uninstall .NET 3.5 if possible, and update the .NET 4.5 branch to .NET 4.7.x or higher. There are known issues with the minimum version to support TLS 1.2 4.6.2 which are resolved in .NET 4.7.
1. If uninstalling .NET 3.5 is not possible, see these steps to make it work with TLS 1.2 natively. https://support.umbrella.com/hc/en-us/articles/115005871543-Requirements-for-forcing-TLS-1-2-on-the-Connector-and-Roaming-Client
Ensure that TLS 1.2 is not disabled, or that any erroneous registry keys are written to the registry's SCHANNEL TLS settings at HKLM SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols keys. Ensure that TLS 1.2 is not set to disabled, and there are no broken keys. Before making any changes to the registry, take a backup and refer to Microsoft's official instructions here.
image001__5_.png
Reboot. After making .NET upgrades or registry key changes, reboot your machine.