• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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