Closed Bug 558786 Opened 14 years ago Closed 14 years ago

try server cert expired

Categories

(Mozilla Messaging Graveyard :: Server Operations, defect)

x86
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dmosedale, Assigned: gozer)

Details

Attachments

(1 file, 1 obsolete file)

Attempting to log in to https://build.mozillamessaging.com/try/ fails:

An error occurred during a connection to build.mozillamessaging.com.

SSL peer rejected your certificate as expired.

(Error code: ssl_error_expired_cert_alert)
Turns out I was misinterpreting the error message.  It's _my_ cert that's expired.  Gozer, can you generate a new cert for me?  I'm bumping the prio to critical because it's not quite a blocker for me, but being able to turn around a try build today for one my 3.1b2 blockers would be exceedingly helpful.
Severity: major → critical
Component: Release Engineering → Server Operations
QA Contact: release → server-ops
Yes, not a problem, but I need a new CSR, as described in https://wiki.mozilla.org/Thunderbird/Infrastructure/TryServer. Follow the same steps as if creating a new cert.
Assignee: nobody → gozer
Dan, assigning back to you, csr creation is in your hands, re-assign to me once you attach the CSR.
Assignee: gozer → dmose
Attached file CSR file (obsolete) —
Assignee: dmose → gozer
Attached file Signed certificate
Enjoy, please close the bug once you verify it works.
Attachment #441817 - Attachment is obsolete: true
It's working; thanks!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: