Skip to content
New issue

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

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

Already on GitHub? # to your account

let's encrypt renewal not automated #82

Open
willk opened this issue Jan 5, 2024 · 1 comment · May be fixed by #119
Open

let's encrypt renewal not automated #82

willk opened this issue Jan 5, 2024 · 1 comment · May be fixed by #119
Assignees

Comments

@willk
Copy link
Contributor

willk commented Jan 5, 2024

Our ssl certificates are not automatically renewed, which makes renewal error-prone. This is a particular problem for let's encrypt certs, as they have a very short lifetime.

previous discussion on internal bug tracker:

tophertimzen:
I can see this being a tricky one to solve for as right now we do manual cert generation for 2 reasons

  1. We use openresty, which certbot doesn't support well
  2. We don't want SAN leakage since we use many domains on each proxy

We have to do a manual acme challenge for each cert too, so I am unsure how we can automatically update. There is perhaps a way we can script this out to be ran on the date certs expire, but I am unsure if certbot can handle this for us.

r00tkillah:
Agreed. I have updated description and title to reflect let's encrypt vs certbot. This is a tricky problem. Propose throwing into backlog.

tophertimzen:
Current manual commands are

sudo certbot certonly --manual --force-renew -d

r00tkillah:
automated renew should also be opsec safe

tophertimzen:
Problems with rules we use in our nginx sites

  1. We are redirecting all /
  2. We need to add root to port 80
  3. We need to let /.well-known through
@devzspy
Copy link
Contributor

devzspy commented Aug 25, 2024

@0xBienCuit has elected to work on this.

@devzspy devzspy moved this to Ready in Feature Release Aug 25, 2024
@devzspy devzspy assigned devzspy and unassigned devzspy Aug 26, 2024
@devzspy devzspy moved this from Ready to Backlog in Feature Release Aug 26, 2024
@devzspy devzspy linked a pull request Sep 4, 2024 that will close this issue
@devzspy devzspy linked a pull request Sep 4, 2024 that will close this issue
@devzspy devzspy moved this from Backlog to In review in Feature Release Sep 4, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
Status: In review
Development

Successfully merging a pull request may close this issue.

3 participants