Status

Mozilla Messaging
Server Operations
--
critical
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: dmose, Assigned: gozer)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

2.46 KB, application/x-x509-ca-cert
Details
(Reporter)

Description

8 years ago
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)
(Reporter)

Comment 1

8 years ago
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
(Assignee)

Comment 2

8 years ago
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)

Updated

8 years ago
Assignee: nobody → gozer
(Assignee)

Comment 3

8 years ago
Dan, assigning back to you, csr creation is in your hands, re-assign to me once you attach the CSR.
Assignee: gozer → dmose
(Reporter)

Comment 4

8 years ago
Created attachment 441817 [details]
CSR file
(Reporter)

Updated

8 years ago
Assignee: dmose → gozer
(Assignee)

Comment 5

8 years ago
Created attachment 441868 [details]
Signed certificate

Enjoy, please close the bug once you verify it works.
Attachment #441817 - Attachment is obsolete: true
(Reporter)

Comment 6

8 years ago
It's working; thanks!
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.