Closed Bug 547792 Opened 16 years ago Closed 16 years ago

drumbeat.stage.mozilla.com needs a better SSL certificate

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: reed, Assigned: oremj)

References

()

Details

The current SSL certificate on https://drumbeat.stage.mozilla.com states the following: * Server certificate: * subject: CN=oremj-drumbeat-tmp * start date: 2010-01-27 20:42:48 GMT * expire date: 2020-01-25 20:42:48 GMT * common name: oremj-drumbeat-tmp (does not match 'drumbeat.stage.mozilla.com') * issuer: CN=oremj-drumbeat-tmp * SSL certificate verify result: self signed certificate (18) Since drumbeat.stage.mozilla.com is not running on the normal staging servers, a self-signed SSL certificate using the MoCo CA should be generated and used instead. Another option would be to rename the staging site to www-stage.drumbeat.org and use the DV SSL certificate that mrz bought in bug 543706.
The right fix for this is to change the stage name to the one I was told to buy the cert for. Your last option is the one we should do.
oremj, passing this to you to coordinate the name change.
Assignee: server-ops → jeremy.orem+bugs
Can we have an HTTP redirect from the old name to the new one, to avoid breaking existing links? (Mark has asked some people to start populating the staging server with content...) Gerv
www-stage.drumbeat.org is now an A record pointing at the IP 67.23.45.13. Gerv
https://www-stage.drumbeat.org/ is responding with the correct cert. I assume you just need to make in-app changes to change the domain?
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.