Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PROD: Fix and document LetsEncrypt configuration for Torque servers. #71

Open
kfogel opened this issue Jul 15, 2020 · 0 comments
Open
Assignees
Labels

Comments

@kfogel
Copy link
Member

kfogel commented Jul 15, 2020

Apparently the LetsEncrypt regular refresh job is shutting down Torque? It happens every two months, like clockwork. That means something is misconfigured. We have until September 12th to fix this permanently before the next one happens. See this thread for details:

From: Karl Fogel
To: Frank Duncan
Cc: Jason Owen, Mike Nolan
Subject: Re: Torque shut down this morning
Date: Wed, 15 Jul 2020 17:04:55 -0500
Message-ID: <[email protected]>

@Nolski, I've assigned this to you, at least for now, just to make sure it has an owner. We may discuss and decide to re-assign it somewhere else, but I want to make sure someone owns it at all times so it doesn't slip along. "Owning" means please bring it up at meetings if I don't (but I'll try to remember to do so). It doesn't take precedence over the editability work in Torque, but it's the next thing after that.

@kfogel kfogel added the bug label Jul 15, 2020
@kfogel kfogel assigned jasonaowen and unassigned Nolski Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants