After installing VS 2015 Update 3, by sending an HTTPS request for WebAPI development, IIS Express raises a SocketException

Question

I have a Desktop client making HTTPS requests to a WebServer hosted in Visual Studio IIS Express. I have been developing the use of VS 2015 Update 2 for several months and everything works without problems.

However, yesterday I installed the VS 2015 update. First I had to install a local SSL certificate on my computer (I am pretty sure that I did not need to do this with Update 2). But as soon as it was aloof, everything was in order.

When I turned on my machine today and loaded my development environment, I get the following exception chain when sending an HTTPS request:

HttpRequestException: An error occurred while sending the request.

WebException: The underlying connection was closed: An unexpected error occurred while sending.

IOException: Unable to read data from transport connection: An existing connection was forcibly closed by the remote host.

SocketException: An existing connection is forcibly closed by the remote host.

I did not make any other changes in my dev environment other than updating Resharper from 9.2 to 2016.1, but I cannot imagine that it had anything to do with my problems.

Does anyone know what might cause problems?

Update:

I do not get an exception if I do not use SSL. So it seems like some of the changes in IIS Express used in Visual Studio 2015 Update 3 are causing some SSL issues.

Answer 1

It seems that my problem was caused by the wrong approach to adding a new IIS Express 10.0 SSL certificate as a trusted certificate.

The following "Authorization Number # 1" on this blog resolved this for me: https://blogs.msdn.microsoft.com/robert_mcmurray/2013/11/15/how-to-trust-the-iis-express-self-signed -certificate /

Answer 2

I do not know about IIS Express, but I ran into the same problem in IIS. It turned out that the certificate was disconnected from the https bindings during the installation of Update 3, and I had to reuse it by choosing the IIS Express development certificate.

Another answer may lead you in the right direction regarding IIS Express.

Answer 3

I had the same problem with updating Visual Studio 2015 Update 3 and fixed it by fixing IIS Express 10.0 in the program and functions (or "Add or Remove Programs").