When working on other things, I found that our coverage tests were failing on master on macOS. I quickly fixed this in certbot/certbot#7972, but there's nothing stopping us from hitting this problem again in the future. I think we should avoid this because it can be a confusing/frustrating experience, especially for new Certbot developers, to investigate test failures on

When singular items are missing we say "does not exist" or doesn't exist".
When singular items are present we say "does exist" or "exists".
Yes, English can be difficult.
https://github.com/acmesh-official/acme.sh/search?q=%22doesn%27t+exists%22&unscoped_q=%22doesn%27t+exists%22
Text says "doesn't exists".

Ref also : https://github.com/acmesh-official/acme.sh/search?q=%22does+not+exists%22&

I cannot see any docs on how the OCSP feature is suppose to work. Please document it. Thanks.

Hi,
not a big issue but as you asked to contribute to the documentation with an CLI example I thought it's worth sharing mine here so one of you with permissions could update the page https://go-acme.github.io/lego/dns/dode/:

export DODE=1234567890abcdefghij lego -d myserver.mydomain.com -a --dns dode --email [email protected] run

In case the local DNS server (e.g. 10.1.1.1) is not rea

At https://github.com/letsencrypt/boulder/blob/97390560a3bf1f68404087c7011752cf1e4bc302/va/va.go#L421, we log when an RPC to a remote VA failed (e.g. due to network timeout or connection refused). However, we don't currently have a stat that shows just that number (as opposed to overall validation failures, which includes cases where we got, e.g., and invalid challenge token). We should add a stat

What would you like to be added

I would love to have a MongoDB database connector.

Why this is needed

All our other services use MongoDB and I would love to keep everything unified in one database system.

Failing that, is it possible to provide a pluggable webhook that we can have and then enter into our own database?

This basically the same as certbot/certbot#1215 but for acmetool. I want to change the contact e-mail for accounts created by acmetool.

I just tried to "import" the acmetool account to certbot but failed doing it. Is there any documentation on how to do this? Is it even possible?

Ideally Let's Encrypt would publish their current service rate limits (those documented at https://letsencrypt.org/docs/rate-limits/) as a JSON feed. We would then ideally use this limit information to warn users and to manage the automated renewals process.

Beyonce said it best. If you like it then you shoulda put a test on it. Scenarios I like:

• Cert is created with right DN
• Cert is stored to X509Store after creation
• Cert request is not resubmitted
• Handles failures gracefully
• HTTP challenge/response works as expected
• Certificate renewal when cert is about to expiration

The "integration guide" https://letsencrypt.org/fr/docs/integration-guide/#implement-ocsp-stapling explains why it's important:

• Privacy
• Speed
• Costs for Let's Encrypt

But doesn't explain how to do it. Maybe a dedicated page could explain it, for most common servers?

Also:

• In the advantages, "avoid downtime in case of revocation" could be added
• The sentence about cost co

It's not really clear how "orders" are stored or how they are related to New-PACertificate.

As someone who is unfamiliar with ACME, I read in one of these issues that New-PACertificate is pretty much the same as Renew if an order exists. It wasn't clear to me that orders apparently only exist locally.

I want to renew my certificate as necessary from a cron-scheduled GitHub Action. Howe

When I first tried to get Pebble running using the binary I downloaded from the releases, it complained about missing files it was looking for. I got it working by copying the test directory from the source repository into the same folder as the Pebble binary. With that, I was able to run Pebble without needing to specify any arguments.

This would be useful to document for people just startin

The text should scroll if you make a selection and move the cursor out of vertical bounds of the window, even if the mouse isn't moved. Currently, it only scrolls if the mouse is moved (ever so slightly works).

This bug was introduced during the shiny hard fork.

Upgrading from v1, I ran the cluster wide steps in the deployment guide.

The new pods failed. I checked the image stream and it was still using the old v1 images. I didn't catch it but it was some error about Unknown parameter --expose...something (sorry), so I figured the image was still out of date.

I deleted the imagestream and re ran all the deployment commands and everything worked beca

As @rjkroege mentioned in rjkroege/edwood#288 tokenizing the results of the getarg function would allow for more robust parsing of the given arguments.