However, trying to transition to any action that requires https gets me a "server refused connection" error. In this article, we are going to create a simple ASP.NET MVC Core Web Application using Visual Studio 2019 and. When I launch the MVC app from within VS2010 it correctly ties back to (on port 80, the default I haven't included all the steps for getting IIS Express to work with unsecure/normal connections on port 80, but they're essentially steps 5 thru 7, but focusing on http and port 80, not https and port 443). The sites section for the file ended up looking like this: ħ) Restarted the http service by executing the following at an elevated commandline prompt: net stop httpĨ) Changed the Project URL on the Web tab of my MVC project's Property page to the following: Saving the project property page triggered a reconfiguration of the server after I made this change. In my case I gotĤ) Installed the self-signed certificate to port 443 by executing the following on an elevated commandline prompt: netsh http add sslcert ipport=0.0.0.0:443 certhash=9B088F80A4FC314128F6289070BA1FC449FDD009 appid=ĥ) Modified the ACL by running the following from an elevated commandline prompt: netsh http add urlacl url= user=everyoneĦ) Modified the nfig file for IIS Express by adding a binding for port 443 and the https protocol. The sample application is a web site for a fictional Contoso. It has been updated for ASP.NET Core 5.0.
This tutorial has not been updated for ASP.NET Core 3.1.
I learned later that I need to delete the spaces when using the thumbprint.Ģ) Deleted whatever certificate was linked to port 443 by executing the following on an elevated commandline prompt: netsh http delete sslcert ipport=0.0.0.0:443ģ) Generated a new GUID by running Create GUID off the VS2010 Tools menu. The Contoso University sample web application demonstrates how to create ASP.NET Core 2.2 MVC web applications using Entity Framework (EF) Core 2.2 and Visual Studio 2017 or 2019. I've taken the following steps, based on googling:ġ) Located the SHA1 thumbprint for my IIS Express Server self-signed certificate via executing the following on a VS2010 commandline: certmgr.exe /c /s /r localMachine MY I can get it to accept unsecure connections on port 80, but not secure on port 443. I am unable to get IIS Express to accept secure connections for a VS2010 MVC3 project that I'm developing.