Setting up SSL on IIS
Posted on 2015-02-05
one of my clients has been working with an ecommerce integration group to get their website up and running which is
already working as of now but now they wanted to use SSL for the website so they want me to handle the install of the certificate on the webserver. I'm trying to get an overall understanding of all the components that go into doing this.
I already am in the process of downloading the intermediate certificate from godaddy and it looks pretty straightforward per their instructions. They also wanted me to open up port 443 on the firewall which i did already but when i tested the port using canyouseeme.org it reported that the connection was refused. Does there have to be another step for 443 traffic to be accepted on the webserver? Port 80 i was able to successfully test as not being blocked. What i was really confused about was that they said i had to create another name for the website to handle the SSL. In other words, if the current website is accessible as www.xyz.com they wanted me to use www.test.xyz.com when i applied for the certificate. Then they said i would have to add a dns record for that xyz.test.com pointing to the same public ip as www.xyz.com. They said they could add the record to their local overrides but preferred not to unless i really had problems with the dns. Thanks.