Problems with SSL certificate in IIS 8

Problems with SSL certificate in IIS 8 - If a page has internal and external outgoing links to redirecting URLs, it’s returning 3xx (301, 302, etc.) HTTP status codes standing for redirection. This issue means that the page does not exist on a permanent or temporary basis. It appears on most of the popular web browsers, usually caused by a misconfigured website. However, there are some steps you can take to ensure the issue isn’t on your side. You can find more details about redirecting URLs by reading the Google Search Central overview. In this article, we’ll go over how you can fix the Problems with SSL certificate in IIS 8 error on your web browser. Problem :

I bought certificate only for name_domain.com under the configuration for IIS 8 (on Windows Server 2012).

I have 301 redirects from www.name_domain.com to https://name_domain.com. If I open the following link in a browser: www.name_domain.com , there's a certificate error.

Should I buy a new certificate or maybe there is another solution to the problem?

Solution :

I would guess you purchase a static single domain certificate which only covers the domain name and not subdomain.

Sadly, www. is a sub by certificate standards.

If that is the case I see 3 moves you could make.

1. Purchase another certificate for the www. that you never plan on using and make a redirect. (Waste of cash, forget I even mentioned it. Unless you plan on using www.name_domain.com to host content one day.

2. Leave your name_domain.com as it is, create a new website in your IIS name it www.Redirect_domain.com. In your basic bindings settings assign the common IP (SSL/Non SSL) using port 80 http: www.name_domain.com. Save it.
In the HTTP Redirect make your permanent redirect to exact destination of name_domain.com (or relative if you are migrating for SEO reasons.)

3. Leave both on the one binding www.name_domain.com port 80 http and the name_domain.com on SSL port 443.
Now you'll have to work with a local redirect from any.name_domain.com to name_domain.com this can be done with your web.config.

My personal experience (The second option is best 2) is to take a few minutes and create a new IIS website for the www.name_domain.com and do the redirect to the https://name_domain.com
But this is only true if you're planning on 301 redirects from www.name_domain.com.

Your settings my be SSL "All Unassigned" if you have any issues with routing in your IIS bindings.

You should be able to configure a different virtual host for you www version of the domain using these instructions. When the certificate is handled by a separated virtual host than the www removal redirect, it should check the certificate when redirecting.

We hope that this article has helped you resolve the redirects, security-certificate, iis8 error in your web browsers. Enjoy browsing the internet uninterrupted!