Eugene Bekker

No renewals yet. All verified Identifiers have an explicit expiration date when they _will_ need to be re-Challenged and verified. I believe the verification lasts a year or so, and...

You can simply request a new certificate using the same DNS name as before. If your Identifer (DNS name) has been previously Challenge-approved in less than 12mos (which of course...

Correct, neither revocation nor renewal are handled _yet_. The original rate limit allowed you to do this 5 times in a 7 day period, and if you're just trying to...

The early versions of the ACME protocol actually did account for optional support by the CA for *renewals* and many moons ago, when an Identifier validation (i.e. a validated DNS...

You need to execute Complete-Challenge again.

Read my comments [above](https://github.com/ebekker/ACMESharp/issues/57#issuecomment-279385932) -- there is really no longer any distinct renewal* operation because of the [current expiration times](https://github.com/ebekker/ACMESharp/wiki/Let%27s-Encrypt-Reference-Sheet), so you need essentially need to start with the very...

The new bool parameter `OutputJson` has been added to the Manual Challenge Handler. If true, it will output all the same info as before, but as structured JSON. See the...

A sample output of an HTTP challenge with JSON: ```json { "Label": "Manual Challenge Handler - HTTP", "CleanUpTime": "2017-08-08T11:41:47.1072234-04:00", "ChallengeToken": "XpPNofCQvBJxuw3hs_sMb_I6SGVPgEPJD2_qE_LHGbA", "ChallengeType": "HTTP", "Description": [ "The Challenge has been completed...

Hi 1trevor, which version of ACMESharp are you using? This feature was added to 0.9.0 which is not released as the *main* version yet -- it's only available in the...

Hmm, you guys are absolutely right -- I am writing to the standard output stream in the underlying challenge handler. So the fundamental issue is that all of the providers...