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

Expected challenge type tls-sni-01 not available for sub.domian.com #760

Closed
1liminal1 opened this issue Feb 22, 2018 · 2 comments
Closed

Comments

@1liminal1
Copy link

1liminal1 commented Feb 22, 2018

Issue description

Hi guys,

When trying to create a new certificate i get the above response. This is with the verbose enabled. its very vague?

FYI; As I'm using server farms and URL rewrite, there is no /wellknown HTTP cannot be used.

[DBUG] Loading signer from C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org\Signer
[DBUG] Getting AcmeServerDirectory
[DBUG] Send GET request to https://acme-v01.api.letsencrypt.org/directory
[DBUG] Loading registration from C:\ProgramData\letsencrypt-win-simple\httpsacme-v01.api.letsencrypt.org\Registration
[INFO] Authorize identifier: DOMAIN
[DBUG] Send POST request to https://acme-v01.api.letsencrypt.org/acme/new-authz
[DBUG] Certificate store: WebHosting
[EROR] Expected challenge type tls-sni-01 not available for sub.domian.com.
[EROR] Create certificate failed

Steps to reproduce

Create a SAN cert with manually entered host names.

[INFO] Let's Encrypt Windows Simple (LEWS)
[INFO] Software version 198.4.6605.15190 (RELEASE)
[INFO] IIS version 10.0
[INFO] ACME Server https://acme-v01.api.letsencrypt.org/

@1liminal1 1liminal1 changed the title Expected challenge type tls-sni-01 not available for Expected challenge type tls-sni-01 not available for sub.domian.com Feb 22, 2018
@WouterTinus
Copy link
Member

Unfortunately TLS-SNI-01 has been disabled by Let's Encrypt for most cases due to security concerns.

https://community.letsencrypt.org/t/important-what-you-need-to-know-about-tls-sni-validation-issues/50811

@WouterTinus
Copy link
Member

In the new release the option is no longer presented, though the plugin will still work for existing renewals.

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