The underlying connection was closed: An unexpected error occurred on a send.

Published: Jul 11, 2018
Post Author Written by eOne Solutions

I have a Shopify REST connector set up in SmartConnect that has been working for some time.
Now when I try to run a SmartConnect map using that Shopify REST connector as either a source or destination I get the error:

Connection could not be validated.
The underlying connection was closed: An unexpected error occurred on a send.

What is the issue and how can it be resolved?

The specific problem is that SmartConnect made a connection to the REST destination, but that destination client was terminated by the host/server- Shopify in this specific instance but it could be any other REST provider.

The reason this happened without warning in this situation is that Shopify recently disabled TLS 1.0/1.1 support and will now only allow TLS 1.2 connections. 

The first version of SmartConnect to support TLS 1.2 on REST connector method calls is SmartConnect  Previous versions of SmartConnect would only use TLS 1.0/1.1 which was why this was working before the protocol change by Shopify.

To resolve this issue:
1. Download and install SmartConnect or later

2. Enable TLS 1.2 on this client machine.  If TLS 1.2 is not enabled on the client machine, SmartConnect won’t be able to connect with TLS 1.2 and would return the same error.  This Microsoft article discusses how to enable TSL 1.2 on the client machine.  Since this machine is the “client”, make sure to enable the “client” TLS 1.2 protocol and not the “server” protocol unless you require that setting in another context.

Again note that this isn’t specifically a “Shopify” issue – it would affect any REST provider that requires a TLS 1.2 connection.

Feeling stuck? Get the support and guidance you need to help you power through any data challenge

We're on your integration team. Connect with our people and let us know how we can help you.