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.

Sign up for GitHub

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

Jump to bottom

Submit-ACMEChallenge : Unexpected error #67

Open
Jojoshua opened this issue Jan 1, 2016 · 4 comments
Open

Submit-ACMEChallenge : Unexpected error #67

Jojoshua opened this issue Jan 1, 2016 · 4 comments

Comments

@Jojoshua
Copy link

Jojoshua commented Jan 1, 2016

I am working through this using manual dns
I have added the TXT record to my domain and now trying to tell ACME I am finished.

I am running into the following error doing Submit-ACMEChallenge. Please help.

Submit-ACMEChallenge -Ref dns1 -Challenge dns-01
Submit-ACMEChallenge : Unexpected error
At line:1 char:1

  • Submit-ACMEChallenge -Ref dns1 -Challenge dns-01
  • - CategoryInfo          : NotSpecified: (:) [Submit-ACMEChallenge], AcmeWebException
- FullyQualifiedErrorId : ACMESharp.AcmeClient+AcmeWebException,ACMESharp.POSH.SubmitChallenge
@ebekker
Copy link
Owner

ebekker commented Jan 2, 2016

Please see the recently updated troubleshooting page, the LE servers currently do no support the DNS challenge method. I believe the updated support for DNS has been committed in the source repo for the Boulder CA server, but those changes have not yet been deployed to STAGING or BETA/PROD.

@Jojoshua
Copy link
Author

Jojoshua commented Jan 2, 2016

I see. What is my other option with this client?

@ebekker
Copy link
Owner

ebekker commented Jan 2, 2016

The LE servers correctly support the HTTP and TLS-SNI challenge types, and the ACMESharp project currently supports HTTP, so that's your option.

If you're configuring IIS or one of the AWS resource types included in the project, you can even have ACMESharp configure the endpoint for you for satisfying the challenge, otherwise you can use the manual HTTP challenge handler and follow the instructions it spits out.

ebekker referenced this issue Jan 9, 2016
@ebekker
Restoring DNS challenge test
99e59a0 
* As per [letsencrypt/boulder#1242] and the
[LE Community
Support](https://community.letsencrypt.org/t/dns-challenge-is-in-staging/8322)
site, Boulder has restored DNS challenge support conforming to the
latest ACME specification.
* I've re-enabled the integration tests for the DNS challenge, and after
adding a short delay between the handling and submission of the
challenge (to make sure it's not verified too soon), the validation is
working.
* Yay!!! DNS challenges are back baby!
@ebekker
Copy link
Owner

ebekker commented Jan 9, 2016

The DNS challenge support has been restored to the LE staging server and I've run some tests and confirmed it's working once again for ACMESharp as well.

ebekker added a commit that referenced this issue Jan 26, 2016
@ebekker
Improving error feedback
9f3feb8 
* Exposing more specific details of underlying remote error when it is
available as part of a problem detail response.
* This fixes #80 and improves on #67.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ebekker @Jojoshua