• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Wildcard SSL and IIS 7

P

PhilMI

Guest
Hi,

I'm running Plesk on IIS 7 for hosting various sites within our organization. The sites share a common domain with different host names for each one. E.g., site1.mydomain.com, site2.mydomain.com... They all share the same IP address.

I have a wildcard SSL certificate for the domain. I installed this certificate and had been using it on a test site - test.mydomain.com. Anytime that I would try HTTPS/443 with another site, e.g., https://site1.mydomain.com, it would redirect to https://test.mydomain.com.

I recently needed to use the certificate for another site (newsite.mydomain.com). In Plesk I added the wildcard cert to that site. Now newsite is the default end point for all HTTPS/443 traffic on the server. So a request for https://test.mydomain.com gets redirected to https://newsite.mydomain.com.

Is there any way to keep the HTTPS/443 requests going to the correct site, instead of just the one?

Note that the wildcard cert works well with the Plesk Panel 8443 admin sites.

Thanks,

Phil
 
Thanks, Davis J. I found a solution using appcmd.exe to resolve this, but forgot to post it. In my notes I also mentioned that, similar to the solution you posted, this could be done via the IIS management console as long as the friendly name for the certificate had the asterisk in it. E.g., *.domainname.com.

Here's the solution using appcmd:

With wildcard certificate already installed, do the following:
1. Go to command prompt (run as administrator).
2. Change directory to c:\windows\system32\inetsrv
3. Run a command in the following format:
a. appcmd set site /site.name:"<IISSiteName>" /+bindings.[protocol='https',bindingInformation='*:443:<hostHeaderValue>']
i. <IISSiteName> is the name for the site as displayed in the "Name" column in the Sites section of IIS
ii. <hostHeaderValue> is the FQDN/binding for the site
b. E.g., appcmd set site /site.name:"mysite.domainname.com" /+bindings.[protocol='https',bindingInformation='*:443:mysite.domainname.com']

Phil
 
Back
Top