Firefox throws error for WWW in-url despite redirects

Question

I recently installed SSL on a website and set it up so that http(s)://www.my-url.com redirects to https://my-url.com . I confirmed that this is working in Chrome.

Unfortunately, if a Firefox visitor browses to https://www.my-url.com, they get a security warning. This seems to happen only in firefox, so I believe there is some server-side setting I could change to fix this.

Is there a way to circumvent this? I know technically that SSL is established before the redirect happens but it seems to work in every other browser. I'd like to avoid getting a new certificate if possible.

What is the actual security warning code? – Byron C. Aug 07 '14 at 16:01 — Byron C., Aug 07 '14 at 16:01
`Error code: ssl_error_bad_cert_domain` – ahjohnston25 Aug 07 '14 at 16:02 — ahjohnston25, Aug 07 '14 at 16:02
Your site isn't responding for me _at all_. Is it up? – Michael Hampton Aug 07 '14 at 16:32 — Michael Hampton, Aug 07 '14 at 16:32
Yes, thats a dummy url. – ahjohnston25 Aug 07 '14 at 16:33 — ahjohnston25, Aug 07 '14 at 16:33

NuTTyX · Accepted Answer · 2014-08-07T20:36:27.433

Do you have a valid certificate for BOTH domains? Either two certs with a SNI-aware server, or a single certs for both domains (SAN) should work. A wildcard cert would NOT work, as it only applies to subdomain level (ie. www1.my-url.com and www2.my-url.com, but not to my-url.com) Depending on your server setup, the problem could be related to SNI/SAN browser support (nevertheless any updated browser should work) or a "feature" of chrome allowing a wildcard to work on a 2-level domain such as my-url.com.

Firefox throws error for WWW in-url despite redirects

1 Answers1