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

ACME server was probably unable to reach #44

Closed
humblecscoder opened this issue Dec 23, 2015 · 2 comments
Closed

ACME server was probably unable to reach #44

humblecscoder opened this issue Dec 23, 2015 · 2 comments

Comments

@humblecscoder
Copy link

Hello, I read all issues, but still don't understand why this problem appears.
I use IIS 8.5 on Windows Server12 R2. In IIS 8.5 create site with host www.hellohttps.com, but when letsencrypt-win-simple validate key:
The ACME server was probably unable to reach http://www.hellohttps.com/.well-known/acme-challenge/Key, but I can open it in browser.

I have suppose it appears because I don't use hosting, and appel directly ip-address, instead hostname and LE cant reach it. Or am I wrong?
FireWall turned off.
http://80.76.96.182/.well-known/acme-challenge/7IK-bb0WB3v0TjmlycxYqP25TKubKLp8YjVDjrpaoGc
Please answer if possible more detalized. I'm newbie in this.

@humblecscoder
Copy link
Author

I already added StaticFile Handler above 3 ExtenssionlessHandler and create web.config in .well-known directory. And still doesn't work

@humblecscoder
Copy link
Author

There is domen validation...
I create a domain, and now autorization result valid

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