I ran into an issue today with how the IIS 7.0 admin GUI deals with SSL certificates when assigning bindings to web sites. I had two websites that I was binding to the same IP address, but I was using different ports for each (including different ports for SSL). Even though I was using a different SSL port for the second website, it was telling me that my certificate was already in use by another website and that changing the setting would affect the other site. The strange thing was, I was using two completely different certificates. Why in the world would it tell me my certificate was in use on the other website, when it clearly was not? Changing the SSL settings on one site would end up deleting the settings on the other site. After searching online, I found out that there are some known bugs with how the admin GUI deals with bindings and SSL in general. By settings the bindings on the command line, I was able to work around the issue.
Below are some useful command line commands that can assist in creating SSL bindings manually.
To list SSL certificates in use, with their bindings: Continue reading Configuring SSL Bindings Directly for Http.sys
||Although this configuration works on Windows Server 2008 R2, it is unsupported by Microsoft. Use at your own risk.
Use these steps to install ASP.NET 1.1 on either Windows Server 2008 x64 SP2, or Windows Server 2008 R2.
- Follow all of the steps in How to install ASP.NET 1.1 with IIS7 on Vista and Windows 2008
- Then implement this workaround for an acknowledged bug: Workaround: Running ASP.NET 1.1 on Vista SP2/WS08 SP2
- Ensure that the “IIS Metabase Compatibility” Role Feature is installed in IIS
- Download and install:
- Make sure ASP.NET 1.1 is enabled under ISAPI and CGI Restrictions
- In my experience, this has already been enabled after installation
- Add this IgnoreSection handler to the <configSections> element on the .NET 1.1 machine.config, located in %windir%\Microsoft.NET\Framework\v1.1.4322\CONFIG