Skip to main content
Question

The SSL connection could not be established

  • February 18, 2025
  • 2 replies
  • 42 views

Forum|alt.badge.img+1

Im integrating eSignature API using ASP .NET web api core and getting the below error after deploying it on our test site.  My test server supports TLS12 and I explicitly set it for http client handler in my api for DocusignClient.  

 

Monitored the traffic using Wireshark and I could see my test server sends hello handshake, but I do not see the hello handshake from Docusign server, 

Any leads to resolve this issue greatly appreciated. Thank you

 

Error Content: System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
 ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
 ---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
   --- End of inner exception stack trace ---

2 replies

Forum|alt.badge.img+7
  • Docusign Employee
  • 59 replies
  • February 19, 2025

Hello Saravana

 

Please verify with the cipher Suites https://support.docusign.com/en/articles/DocuSign-Supported-Cipher-Suites and make sure outbound traffic to DocuSign is not blocked.

 

If the issue persists after the above checks also, then please create a support case with DS by attaching HAR File  for further analysis.

 

Thanks & Regards

Sai HariPriya Dandamudi | Developer Support Engineer | DocuSign

A picture containing clipartDescription automatically generated

 


Forum|alt.badge.img+1

the link is broken, unable to access the content.

https://support.docusign.com/en/articles/DocuSign-Supported-Cipher-Suites

Page not found

Looks like this content no longer exists.