ERROR:Error in Generating Shipment: The underlying connection was closed: An unexpected error occurred on a send.

ERROR:Error in Generating Shipment: The underlying connection was closed: An unexpected error occurred on a send. I found information about it below. I need to get this fixed.. __________________________________________________________________________________________ Link to answers: [login to view URL] _______________________________________________________________________ answer: that I read, but do not how to implement…. ______________________________________________________________________________ For me it was tls12: [login to view URL] = [login to view URL]; shareimprove this answer edited Jan 8 '16 at 14:37 user3071284 3,49962340 answered Jan 8 '16 at 13:48 Lanklaas 75557 Same here. Thanks! – Max Wikström Sep 28 '16 at 0:13 10 Note that you must be careful because this change is global to your AppDomain, and will cause calls to any site which doesn't offer TLS 1.2 to fail (which you may prefer if the data to be transported is truly sensitive). To prefer TLS 1.2 but still allow 1.1 and 1.0, you have to OR them: [login to view URL] = [login to view URL] | [login to view URL] | [login to view URL]; – Dusty Mar 17 at 17:33 same here, you saved my life, spent so much time to figure out what was wrong with RestSharp – darul75Mar 31 at 10:19 This solution also works for those not using RestSharp as well as for those that are not using ServicePointManager. Just copy and paste the above line before your WebRequest call or whatever you're using to make the request. I initially ignored this solution because of the above reasons. – goku_da_masterAug 16 at 17:14