You may attach a specific IP address to each Web site to host more than one Web site on a Web server, specify a non-standard TCP port number for a Web site, or use host headers. If the three approaches, host headers are more common than assigning specific IP addresses to Web servers or using non-standard TCP port numbers.
Multiple websites hosted on the same domain can be connected to port 443, but you can’t effectively do it from the Interface because, as seen in Figure 1, the host name is greyed out. If the SSL Certificate starts with a *, however, then it is activated. Wild card approvals are likely to be supported in line with Figure 2.
Figure 1, Hostname greyed out
Figure 2
When you want to connect numerous SSL certificates to different websites, all of which wish to use port 443, this misunderstanding emerges. That isn’t going to work.
As per figure 2, a quick modification is to go ahead and change the friendly name of the installed certificate and apply * before the friendly name. That * does not mean that this is actually a wild card certificate.
This will allow the Host Name Portion, where you can now correctly add URLs and connect multiple SSL Single IP and Port Combination certificates.
Utilizing CLI
1)After opening a command prompt with administrative privileges, navigate to cd C:\Inetpub\AdminScripts
2) Type the order below
cscript.exe adsutil.vbs set /w3svc/<site identifier>/SecureBindings: “443:<host header >”
< host header > is the Web site ‘s host header value (www.myothersite.com). When looking at all the websites in IIS, < domain identifier > is the IIS domain ID seen.
Run that command for each of the websites that need to use that certificate. They will then use the same certificate that was install to the first site on the IP.