Every once in a while, I come across an issue where the IIS binding is deleted unexpectedly or the SSL certificate in the IIS binding is replaced or removed for some reason. In one of these cases, I saw “SSL Certificate Settings deleted for endpoint” warning message in Event Viewer:
Event ID 15300 (HttpEvent)
SSL Certificate Settings deleted for endpoint
Especially after a new installation of IIS role in a server, you may notice that your browser returns “404 Page Not Found” error if you try to visit ASP.NET pages. Files exist and the URL is correct. What to do in this situation?
Due to the company policies, many developers don’t have Administrator rights on the machines they use for development. Microsoft released IIS Express to allow these developers load and run projects in Visual Studio without Administrator rights.
If your project is somehow not compatible with IIS Express and you want to run it on Local IIS without Administrator rights on the machine, try the two workarounds below. They are not guaranteed to work but you may save a lot of time if they do work.
IIS websites use all the available CPU power by default. There are application pool settings you can play around if you want to limit the CPU usage or you want to assign specific processors to specific websites.
TLS (Transport Layer Security) is a cryptographic protocol to provide secure communications over networks. IETF (Internet Engineering Task Force) built TLS on the SSL (Secure Socket Layer) specification which is now deprecated. Over the time, IETF release TLS versions 1.0, 1.1, 1.2, and 1.3.
Denial of Service (DoS) attacks cause web servers to become unavailable because of the big amount of requests that max out the server resources. Attackers specifically craft these requests to take the server down. One type of DoS attack is the Slow HTTP POST attack.
Windows Server makes it easier to extend the server capabilities by installing new roles and features. You can use Server Manager to install or uninstall new capabilities. Server Manager provides an easy-to-use wizard to guide you through the process. However, you may come across to this error code in some cases: 0x800f0831.
We have recently upgrade a .NET Core 2.2 application to 3.1 version. While trying to run it in Visual Studio, we came across “rzc discover exited” and “hostpolicy.dll required” errors:
rzc discover exited with code -2147450749A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in [path]
Visual Studio makes it easy to run your application project by using IIS installed in Windows. You don’t have to explicitly go to IIS Manager and deploy your application there. You can simply click the “Run” (green arrow) icon to view your project on browser.