Could not create SSL/TLS secure channel.

Comments

• Repetier

  December 2019

  Does 2.1.6 already have the checkbox to not use SSL connection in settings?
  I already fixed that for next update. You are not doing anything wrong, but windows now requires new settings to use TLS for https to use current certificates.
• toddho

  December 2019

  OK, Thanks.  I see the check box in Config->Preferences->Push-Messages.  The check box is labeled:  Use http instead of https for sending (only required for Windows XP).

  I check that box and it works!  Thanks!  I hope that this post will help someone else too....

  
  

  Thanks

  Todd
  
• tophi_topha

  April 2020

  INCREDIBLE. I needed a long time to found your answer. I think, this little box is not at the right place. And the win XP thing is wrong.
  

  Bye
  
• warnerjonn

  June 2022

  The error is generic and there are many reasons why the SSL/TLS negotiation may fail. ServicePointManager.SecurityProtocol property selects the version of the Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocol to use for new connections; existing c# socket connections aren't changed. Make sure the ServicePointManager settings are made before the HttpWebRequest is created, else it will not work. Also, you have to enable other security protocol versions to resolve this issue:

   

  ServicePointManager.Expect100Continue = true;

  ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12

       SecurityProtocolType.Tls

       SecurityProtocolType.Tls11

       SecurityProtocolType.Ssl3;

   

  //createing HttpWebRequest after ServicePointManager settings

  HttpWebRequest request = (HttpWebRequest)WebRequest.Create("https://google.com/api/")

  
  

  If you create HttpWebRequest before the ServicePointManager settings it will fail and shows the error message.