-
Notifications
You must be signed in to change notification settings - Fork 270
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
Step 3 failing #12
Comments
Howdy, can you please copy and paste the Step 3 commands and their output into this bug? Thanks! |
Also, can you please paste the CSR you're using into this bug? Thanks! |
I have the same issue. My CSR:
Commands and outputs:
|
Howdy, you have the same nonce for all of these, so I think your browser is aggressively caching the requests for the anti-replay nonces. I just added a cachebuster to fix this. Can you please refresh and try again? |
@diafygi Yes, it works now! Thanks. |
Here at steps 3 it yields: Console says: /LE: NVM, works under a clean profile browser now. |
Hi,
When I run Step 3 I get the following error:
Error: Domain failed. Please start back at Step 1. {"type":"urn:acme:error:badNonce","detail":"Unable to read/verify body :: JWS has invalid anti-replay nonce","status":400}
The console log shows:
[Error] Failed to load resource: the server responded with a status of 409 (HTTP/2.0 409) (new-reg, line 0)
[Error] Failed to load resource: the server responded with a status of 400 (HTTP/2.0 400) (new-authz, line 0)
The text was updated successfully, but these errors were encountered: