Closed Bug 1033174 Opened 11 years ago Closed 11 years ago

getfirebug.com uses an invalid security certificate.

Categories

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

x86_64
Windows 7
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Honza, Assigned: nmaul)

Details

(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/478] [firebug-p1])

Load https://getfirebug.com/wiki/index.php/Main_Page There is a message: This Connection is Untrusted getfirebug.com uses an invalid security certificate. The certificate is only valid for the following names: generic-san.mozilla.org, inform.mozilla.org, air.mozilla.org, basket.mozilla.org, blog.mozilla.com, blog.mozilla.org, boardwiki.mozilla.org, creative.mozilla.org, foundationwiki.mozilla.org, join.mozilla.org, mpl.mozilla.org, outgoing.mozilla.org, quality.mozilla.org, securitywiki.mozilla.org, wiki.mozilla.org, tbpl.mozilla.org, basket.mozilla.com, air.mozilla.com, hacks.mozilla.org, brendaneich.com, www.brendaneich.com, dragnet.mozilla.org, www.itisatrap.org, itisatrap.org, calendar.mozilla.org, allizom.org, www.allizom.org, moztrap.mozilla.org, careers.mozilla.com (Error code: ssl_error_bad_cert_domain) Pleas fix ASAP, the entire getfirebug.com site is broken now! Honza
Whiteboard: [firebug-p1]
Whiteboard: [firebug-p1] → [kanban:https://kanbanize.com/ctrl_board/4/478] [firebug-p1]
Assignee: server-ops-webops → nmaul
This is my fault. I was sure getfirebug.com was on that SAN, but alas it is not. I've temporarily enabled SNI using the getfirebug.com cert, and it's back up and running. I will shortly revert my earlier changes to put this back to its previous state, to eliminate the inevitable SNI weirdness. Very sorry for the brokenness. :(
Thanks for prompt fix Jake! Honza
This is fixed properly now, though it may take a bit longer for *full* DNS propagation worldwide.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.