-3

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.

Improve this question
4
  • What is the actual security warning code?
    – Byron C.
    Commented Aug 7, 2014 at 16:01
  • Error code: ssl_error_bad_cert_domain
    – ahjohnston25
    Commented Aug 7, 2014 at 16:02
  • Your site isn't responding for me at all. Is it up?
    – Michael Hampton
    Commented Aug 7, 2014 at 16:32
  • Yes, thats a dummy url.
    – ahjohnston25
    Commented Aug 7, 2014 at 16:33

1 Answer 1

Reset to default
2

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.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .