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

Challenge not completing iis handler #343

Open
woody0130 opened this issue Apr 27, 2018 · 2 comments
Open

Challenge not completing iis handler #343

woody0130 opened this issue Apr 27, 2018 · 2 comments

Comments

@woody0130
Copy link

woody0130 commented Apr 27, 2018

Running Windows 2012 R2

used powershell gallery to install

also installed ACMESharp.Providers.IIS

steps:

Initialize-ACMEVault

New-ACMERegistration .....

New-ACMEIdentifier -Dns www.ccimef.org -Alias ccimef2

Complete-ACMEChallenge ccimef2 -ChallengeType http-01 -Handler iis -HandlerParameters @{ WebSiteRef = 'CCIMEF' }

status will not change from pending:

(Update-ACMEIdentifier ccimef2 -ChallengeType http-01).Challenges

ChallengePart : ACMESharp.Messages.ChallengePart
Challenge : ACMESharp.ACME.HttpChallenge
Type : http-01
Uri : https://acme-v01.api.letsencrypt.org/acme/challenge/G43bhxXfonUJD7ZIWKeIVXE4V8nncO8Lscfa5Sb9MHk/4392804137
Token : Q1P0Qi8s52TxGW4Wxz1lPrtsIAVNrs0ft2e7C2L8hTk
Status : pending
OldChallengeAnswer : [, ]
ChallengeAnswerMessage :
HandlerName : iis
HandlerHandleDate : 4/27/2018 12:19:44 AM
HandlerHandleMessage : * Challenge response content has been written to local file path
at: [......\ccimef.org\.well-known/acme-challenge/Q1P0Qi8s52TxGW4Wxz1lPrtsIAVNrs0ft2e7C2L8hTk]
* Challenge response should be accessible with a MIME type of [text/json]
at: [http://www.ccimef.org/.well-known/acme-challenge/Q1P0Qi8s52TxGW4Wxz1lPrtsIAVNrs0ft2e7C2L8hTk]
* Local web.config has been created to serve response file as JSON
however, you may need to adjust this file for your environment
at: [http://www.ccimef.org/.well-known/acme-challenge/Q1P0Qi8s52TxGW4Wxz1lPrtsIAVNrs0ft2e7C2L8hTk]

HandlerCleanUpDate :
HandlerCleanUpMessage :
SubmitDate :
SubmitResponse :

ChallengePart : ACMESharp.Messages.ChallengePart
Challenge :
Type : dns-01
Uri : https://acme-v01.api.letsencrypt.org/acme/challenge/G43bhxXfonUJD7ZIWKeIVXE4V8nncO8Lscfa5Sb9MHk/4392804138
Token : 7U2kBXHsiHMMN6NTZOHh4G0LfFEFXprnFOPO5S39PNw
Status : pending
OldChallengeAnswer : [, ]
ChallengeAnswerMessage :
HandlerName :
HandlerHandleDate :
HandlerHandleMessage :
HandlerCleanUpDate :
HandlerCleanUpMessage :
SubmitDate :
SubmitResponse :

@woody0130
Copy link
Author

I have also checked that the .well-known url responds via browser.

@woody0130
Copy link
Author

Also, interesting change in output of Update-ACMEIdentifier for this alias today.
Notice that these three items have changed:

HandlerName :
HandlerHandleDate :
HandlerHandleMessage :

Compare below output to above:

(Update-ACMEIdentifier ccimef -ChallengeType http-01).Challenges

ChallengePart : ACMESharp.Messages.ChallengePart
Challenge :
Type : http-01
Uri : https://acme-v01.api.letsencrypt.org/acme/challenge/G43bhxXfonUJD7ZIWKeIVXE4V8nncO8Lscfa5Sb9MHk/4392804137
Token : Q1P0Qi8s52TxGW4Wxz1lPrtsIAVNrs0ft2e7C2L8hTk
Status : pending
OldChallengeAnswer : [, ]
ChallengeAnswerMessage :
HandlerName :
HandlerHandleDate :
HandlerHandleMessage :
HandlerCleanUpDate :
HandlerCleanUpMessage :
SubmitDate :
SubmitResponse :

ChallengePart : ACMESharp.Messages.ChallengePart
Challenge :
Type : dns-01
Uri : https://acme-v01.api.letsencrypt.org/acme/challenge/G43bhxXfonUJD7ZIWKeIVXE4V8nncO8Lscfa5Sb9MHk/4392804138
Token : 7U2kBXHsiHMMN6NTZOHh4G0LfFEFXprnFOPO5S39PNw
Status : pending
OldChallengeAnswer : [, ]
ChallengeAnswerMessage :
HandlerName :
HandlerHandleDate :
HandlerHandleMessage :
HandlerCleanUpDate :
HandlerCleanUpMessage :
SubmitDate :
SubmitResponse :

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

1 participant