IIS 10 - Chrome 44 ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY

Question

After upgrading to Windows 10, I get ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY in Google Chrome (Firefox 39 just doesn’t load the page) when I try to access my computer via HTTPS. I have a certificate signed by GoDaddy for my computer.

I tried to disable most of my encryption ciphers at https://http2.imtqy.com/http2-spec/#BadCipherSuites .

I went so far as to disable the ciphers that keep me from RDPing on my desktop ... and still throw an error!

Any guidance is appreciated.

Answer 1

Apparently, you are not the only one who has this problem: Disabling HTTP / 2 / SPDY in HTTP.SYS and IIS in Windows 10

According to the error message, this is a problem with SPDY, so the certificate and cipher suites are not the cause.

SPDY is a protocol that allows multiplexing HTTPS requests, but it will be replaced by HTTP / 2. As a temporary fix, you can disable its support in your browser / registry / server.

Answer 2

I ran into the same problem after my win 10 dev machine was recently updated twice (updates took about 35-40 minutes each time) and after that I was not able to run my Visual Studio 2015 web applications via Https on Chrome, but was able to run on IE

• I tried the registry method to disable Http 2, as mentioned here , but it didn’t work for me
• Then I stumbled upon the solution posted here and used IIS Crypto and selected the Cipher Suites option and clicked the Best Practices button and applied it, my problem disappeared and now I can run my web application via Https in Chrome, as before

Answer 3

Uncheck "Enable SSl" in the properties of your project on the "Debug" tab.

Answer 4

The inconvenience in the Google Chrome browser and the Mozila Firefox browser "ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY" was resolved by performing the following configuration of the IIS website server using the tool: IISCrypto https://www.nartac.com/Products / IISCrypto /

and I used the "BEST PRACTICES" button to set the configuration recommended by the program.

In IIScrypto, run on my server where my site is hosted. Schannel.

Cipher Suites.

after that my website was loaded into the required browsers without any warnings, however, I needed to prevent TL1.0 and TLS1.1 from being enabled on the server due to vulnerability problems and only

I enabled TLS 1.2 in IIS version 10 (the IIS version of the server on which I hosted my website), leaving it operational as follows.

I hope you find this useful.

In IIScrypto, run on my server where my site is hosted. Schannel. Cipher Suites.