Changed SSL/TLS on server cannot publish via visual studio now

Question

I created a new server to move our Windows 2008 server to Windows 2012R2. I was publishing to the new server without issue for a few days and testing the site. I realized du

Answer 1

I found the answer here:

http://www.diaryofaninja.com/blog/2016/02/28/pci-compliant-web-deploy-getting-webdeploy-working-after-disabling-insecure-ciphers-like-ssl-30-and-tls-10

It turns out that after much stuffing around on my servers, the issue actually lies with the client doing the deploying.

The issue lies in .Net and it’s default settings for use of SSL.

By default .Net has a setting called “useStrongCrypto” that allows the client PC to use TLS 1.1 and higher.

To enable secure your local client PC to use TLS 1.1 and higher (or as Microsoft terms is “strong crypto”) you need to edit the following registry entries:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001

I restarted visual studio and was able to publish.