Hi all.
I have an SSL cert I've been using succesfully in other versions of IIS, but recent cut backs at home has forced me back to WHSV1 (my 2008R2 trial ran out) and I'm finding it very difficult to install a valid SSL cert for the remote web access site that WHS serves up.
When I use the baked in self issued one for my server, it serves the page up just fine. However if I issue the SSL cert (valid until 2015), IIS exhibits some strange behavior including:
- Not serving HTTPS up (either just won't connect or states there is an SSL error)
- If I go and check the cert again, it tells me sometimes that there is no cert assigned
If I replace the cert with the self issued one, no issues... so I'm not sure what's going on here.
WHSv1 does not seem to have the feature set like SBS did where you can just go through and use your own domain settings, etc. The homeserver configuration domain doesn't even work any longer so that cannot be truly completed. I have my own domain name and was using it succesfully for the greater part of the last 120 days or so...so not sure what else is happening here.
I suppose if desperate I can shell out $$$ for Server 2008 R2, but would rather not at this time.
Any hints?