Closed Bug 745389 Opened 12 years ago Closed 12 years ago

ssl_error_bad_cert_domain visiting https://blog.mozilla.com/

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: briansmith, Assigned: jd)

References

Details

+++ This bug was initially created as a clone of Bug #690008 +++
+++ This bug was initially created as a clone of Bug #689996 +++

Go to:

https://blog.mozilla.com/futurereleases/2012/03/23/upcoming-firefox-support-changes/

This Connection is Untrusted

blog.mozilla.com uses an invalid security certificate.

The certificate is only valid for tbpl.mozilla.org

(Error code: ssl_error_bad_cert_domain)
assigning this to jd, the redirect is in place so it -should- work but does not appear to be.  (for context, we changed from .com to .org)
Assignee: server-ops → jcrowe
Brian,

This is due to a lack of an SSL cert for .com

This means that all non-SSL .com redirects are working along with all SSL and non-SSL requests for .org.

I have initiated a conversation to determine the best solution to this issue.  I will let you know the solution as soon as I know.

Regards
Status: NEW → ASSIGNED
Brian,

We went ahead and set .com up to use an old wild-card cert which is due to expire on May 27.  This solves the immediate issue, but I am told that we will not be re-issuing this cert.  The best path will be to update any links that point to the .com site prior to that time.  If this is completely unrealistic, please let us know.

Regards
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.