Allow Let's Encrypt ACME challenge requests in Azure/IIS #211
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gazab
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request will allow static file requests to slackin-installation.com/.well-known/acme-challenge/STATIC_FILE which Let's Encrypt (https://letsencrypt.org/) uses to verify domain ownership when automatically issuing and renewing certs for HTTPS.
This change only changes web.config so it only works on Azure or other IIS-based hosts. A better change would probably be to make Node itself serve the directory correctly but my few tries to do that failed.
This change works like a charm together with the Azure Let's Encrypt extension (https://github.com/sjkp/letsencrypt-siteextension) which takes care of the Let's Encrypt setup.
I've used it successfully on this site: https://www.fpv-sverige.se/
Which now lets through request like this one: https://www.fpv-sverige.se/.well-known/acme-challenge/1paIJkZJOxMjch3FHasm9xBGFqdrUopegAeaee_Cgyc
Before this fix node would just respond with CANNOT GET /path