Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

var state = await dnsChallenge.Validate(); returns pending state, what are next steps?

See original GitHub issue

Hello,

var state = await dnsChallenge.Validate();

returns pending state. If to wait several seconds and call that command again exception will be thrown:

Certes.AcmeRequestException: Fail to load resource from 'https://acme-v02.api.letsencrypt.org/acme/challenge/YP51fWU6Lm7y5X0I1VaBs0S-lUfYQ3ORyS3AJxRiC1E/19464011558'. urn:ietf:params:acme:error:malformed: Unable to update challenge :: authorization must be pending at Certes.Acme.IAcmeHttpClientExtensions.d__0`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime

So, what is the correct next step?

Issue Analytics

State:
Created 4 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

webprofusion-chrisccommented, Aug 13, 2019

@hhblaze if making DNS updates you generally have a propagation time for the changes to copy to all of your nameservers, which is the main thing you need to wait for with DNS challenges. So you can optionally wait for a fixed delay before even attempting to validate.

0reactions

hhblazecommented, Aug 13, 2019

Yeah, it looks like it is a point of delays. I have increased time to 30 seconds, between first validation call (await dnsChallenge.Validate()) and the next validation check (await challenge.Resource()), also increased time to 5 seconds between changing TXT record and first validation call and finally await challenge.Resource() returned me ChallengeStatus.Valid even after the first attempt. Will go on to test further.

Thank you!