Certbot renewals failing #513

Closed
opened 2023-09-09 17:37:30 +00:00 by raucao · 3 comments
Owner

Investigating...

Investigating...
raucao added this to the Current operational issues project 2023-09-09 17:37:31 +00:00
raucao added the
bug
label 2023-09-09 17:37:49 +00:00
Author
Owner

It's still trying to use webroot auth on fornax, even though we have switched to DNS auth recently. Looks like we didn't test that on fornax after setting it up successfully on draco.

It's still trying to use webroot auth on fornax, even though we have switched to DNS auth recently. Looks like we didn't test that on fornax after setting it up successfully on draco.
Author
Owner

I have deleted the expired cert for the RS forums and kept the rest as is for now. We need to delete the others and run Chef again to create new certs and have them be renewed using DNS auth.

I have deleted the expired cert for the RS forums and kept the rest as is for now. We need to delete the others and run Chef again to create new certs and have them be renewed using DNS auth.
raucao added the
ops
kredits-1
labels 2023-10-06 14:32:18 +00:00
Author
Owner

Did a dry-run and then carefully replaced the existing certs via Chef runs (not all at once to prevent extended downtimes).

Did a dry-run and then carefully replaced the existing certs via Chef runs (not all at once to prevent extended downtimes).
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#513
No description provided.