Having two websites on the same IIS server accessible with SSL certificates and URL Rewrite Enabled

Hi @Kaplan, Andrew H ,

Thanks for the update.

I agree with Bruce’s point here, the existing HTTP binding on port 10000 is likely what is blocking the HTTPS binding from being added.

Since Site Two already has an HTTP binding on port 10000, IIS is not letting the HTTPS binding use that same port. If the second site should now be accessed as:

https://recovery.domain.com:10000

then I would remove the existing HTTP binding on port 10000 for Site Two, then add the HTTPS binding with the recovery_2026 certificate.

The final binding for Site Two should look like this:

Type: https
IP address: All Unassigned
Port: 10000
Host name: recovery.domain.com
SSL Certificate: recovery_2026

After that, test the site directly with https://recovery.domain.com:10000.

Just note that once the HTTP binding is removed, http://recovery.domain.com:10000 would no longer be the expected URL. If IIS still reports that the port is in use after removing that HTTP binding, then another site or process may also be using port 10000.

Hello Tom.

It appears the above will not work. I cannot remove the http binding to port 10000 from the second site. The ability to remove that binding is greyed out.

Thank you for checking.

Please try these steps next:

1. Close IIS Manager and reopen it as Administrator.
2. Go back to Site Two → Bindings, select the existing http binding on port 10000, and check if Remove is available.
3. If Remove is still greyed out, try removing the binding from an elevated PowerShell window:

Import-Module WebAdministration
Remove-WebBinding -Name "Site Two" -Protocol "http" -Port 10000

Please replace Site Two with the actual IIS site name.

After that, add the HTTPS binding again:

Type: https
IP address: All Unassigned
Port: 10000
Host name: recovery.domain.com
SSL Certificate: recovery_2026

If PowerShell also cannot remove the binding, then the next thing I would check is whether the binding is being controlled by another IIS configuration layer or another site configuration.

Hello Tom.

Thank-you for your response. I have been going with generic names for the two websites, but at this point I believe I can give the actual names.

The above steps did not work, as the Remove option in IIS Manager was still greyed out, and the output from the elevated PowerShell prompt came back with the following error:

Remove-WebBinding : Cannot find binding '*:10000:'.

I am starting from the beginning with the SSL Certificate available and assigned to the first site. The URL Rewrite Rule has been removed until this issue has been resolved. The bindings at the time of this posting for the two sites are the following:

NAME: Default Web Site (site one) TYPE: http IP ADDRESS: All Unassigned PORT: 80 HOST NAME

NAME: Default Web Site (site one) TYPE: https IP ADDRESS: All Unassigned PORT: 443 HOST NAME : rorecovery2.partners.org SSL CERTIFICATE: rorecovery2_2026

NAME: rowebconsole (site two) TYPE: http IP ADDRESS: All Unassigned PORT: 10000 HOST NAME

Hi Kaplan, Andrew H,

Thank you for the details.

Since the earlier command did not find *:10000:, I would first confirm how PowerShell is seeing the binding before trying to remove it again.

Could you run this from an elevated PowerShell window and share the output?

Import-Module WebAdministration
Get-WebBinding -Name "rowebconsole" | Format-List protocol,bindingInformation,sslFlags

Once we can see the exact bindingInformation value, the remove command can be matched to that output instead of guessing the binding string.

Hello Tom. The output from the PowerShell command is the following:

protocol : http bindingInformation : *:10000:rorecovery2.partners.org sslFlags : 0

Hi Kaplan, Andrew H,

Thank you for the output. The binding seems to include the host name, so it needs to be removed using the full value:

*:10000:rorecovery2.partners.org

Please try this from an elevated PowerShell window:

Import-Module WebAdministration

Get-WebBinding -Name "rowebconsole" |
Where-Object {
    $_.protocol -eq "http" -and
    $_.bindingInformation -eq "*:10000:rorecovery2.partners.org"
} |
Remove-WebBinding

After that, you can confirm it was removed with:

Get-WebBinding -Name "rowebconsole" | Format-List protocol,bindingInformation,sslFlags

Then add the HTTPS binding for rowebconsole:

Type: https
IP address: All Unassigned
Port: 10000
Host name: rorecovery2.partners.org
SSL Certificate: rorecovery2_2026

Then test it with:

https://rorecovery2.partners.org:10000

If it still does not load after that, I would first check whether the HTTPS binding now appears under rowebconsole in IIS Manager.

Hello Tom.

The above steps worked. I can connect to the https://rorecovery2.partners.org:10000 website. It appears the redirect for the first site, rorecovery2.partners.org is also working without issue.

The URL Rewrite rule is not in place, but the first site has bindings for ports 80 and 443. Regarding that: Should the URL Rewrite be put in place for the https://rorecovery2.partners.org:10000 website?

Hi @Kaplan, Andrew H,

Sorry for the late response and thanks for confirming.

Since https://rorecovery2.partners.org:10000 is working now, I would not add the URL Rewrite rule to rowebconsole.

URL Rewrite would only be needed if you want an HTTP request to redirect to HTTPS. Since this site is now being accessed directly over HTTPS on port 10000, no rewrite rule is needed there.

For the first site, if the redirect is already working as expected, I would leave that configuration unchanged as well.

If you still have any issues, please feel free to comment. I'd happy to assist.