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

How to resolve challenge / identifier status "invalid" #332

Open
alexhass opened this issue Feb 18, 2018 · 1 comment
Open

How to resolve challenge / identifier status "invalid" #332

alexhass opened this issue Feb 18, 2018 · 1 comment

Comments

@alexhass
Copy link

alexhass commented Feb 18, 2018

I have two failues of requests and both are marked with status invalid. Both are resolved now by fixing the DNS and IIS redirect rules. However the status cannot set back to pending and I have no idea how to request the check from let enrypt again.

  1. I missed to add an IP to DNS for wildcard. Therefore lets encrypt reports "No valid IP address found for ...". So I fixed this in DNS and like to request again.
  2. I also had a conflicting rewrite rule that has not skipped .well-known path and therefore returned invalid content to lets encrypt server.

Both error are valid "invalid"'s, but now I fixed both of them and need to request again. How can I tell the lets encrypt API to check again???

Complete-ACMEChallenge : authorization is not in pending state; use Force flag to override this validation

Running this with -Force does also NOT reset the validation. This could be a bug, too.

@WallyRanson
Copy link

Once a challenge have changed to invalid that challenge is dead for good.
You need to start over with a new identifier. Just a timestamp to the identifier, then it works everytime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants