tag:help.appveyor.com,2012-11-13:/discussions/suggestions/1930-deploying-to-custom-nuget-feed-using-tls-12-requires-a-workaroundAppVeyor: Discussion 2018-08-25T02:19:13Ztag:help.appveyor.com,2012-11-13:Comment/432157252017-08-15T22:57:08Z2017-08-15T22:57:08ZDeploying to custom NuGet feed using TLS 1.2 requires a workaround<div><p>Hi David,</p>
<p>This is right way to solve the problem.<br>
I believe we could do this with registry settings found <a href="https://blogs.technet.microsoft.com/keithab/2015/06/22/error-while-configuring-wapthe-underlying-connection-was-closedpart-2">here</a> and <a href="http://www.johnlouros.com/blog/enabling-strong-cryptography-for-all-dot-net-applications">here</a>, but this will probably break a lot of communication with servers which do not support TLS 1.2. So for now we recommend people to do exactly what you did :)</p>
<p>Ilya.</p></div>Ilya Finkelshteyn