I have a development server that I'm trying to enable a self-signed SSL on so that we can test some functionality specific to the SSL before pushing out to our production server (which has a real, certified SSL)
I first tried to use the Self-Signed Certificate feature inside IIS 7.5, but that didn't work. I was looking around and found that IIS manager doesn't set the IssuedTo to the domain of the site, so I tried doing that.
I found this walkthrough (http://www.robbagby.com/iis/self-signed-certificates-on-iis-7-the-easy-way-and-the-most-effective-way/) and tried it, but it still wasn't working. When I try to access the site via https, it can't find the site (Chrome returns "Webpage not available", Firefox returns "unable to connect"). That tutorial looks to be correcting the issue of whether the cert is trusted or not, but I can't even get mine working at all.
I'm not sure if this could be some sort of network issue at our hosting provider or what. We have full control of the server via RDP to make any changes necessary on the server itself, but I don't know where to start looking for what's wrong with this.
Just for reference, we have numerous sites set up on this development server, including review.site.com and stage.site.com. I am trying to set up the SSL for stage.site.com. The production site (www.site.com) is hosted on a different server within the same network as the dev server.
Any ideas on where to start looking for this?