LetsEncrypt Certificates for Development Machine

I'm fairly new to testing Lets Encrypt and I have some Windows Server 2016 machines that I'd like to test on.

When I attempt to setup Lets Encrypt certs, I, for the most part get the same error. Essentially that the sites needs to be publicly accessible.

Certify The Web:
"Config checks failed to verify http://SITE.com is both publicly accessible and can serve extensionless files e.g. http://SITE.com/.well-known/acme-challenge/configcheck"

Open in new window


Win.Acme v1.9.10.1:
"Authorization result: invalid
 [EROR] ACME server reported:
 [EROR] [type] urn:acme:error:unauthorized
 [EROR] [detail] Invalid response from http://SITE.com/.well-known/acme-challenge/Z7oLhYqhHZ6gFO6C9LVTVG8h60AcAP_BLYWDvWKzsws: "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Inter"
 [EROR] [status] 403"

Open in new window


Is it possible to get Lets Encrypt certificates to work in a Development/Test environment? Perhaps I'm missing something obvious, like a work-around putting in files in Production. (Unfortunately, that sorts defeats the security aspect of it.)

Any advice would be appreciated.

Thanks for your assistance.
TessandoIT AdministratorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nociSoftware EngineerCommented:
LetsEncrypt has no idea if a system is sued for production, testing or development.., that's you who decide what to use your systems for.

The error message show "unauthorized" / not publlicly accessible......
You system MUST be reachable for the LE servers (they try to fetch some data from there)...
 The query fails ==> you don't get access.
http://SITE.com/.well-known/acme-challenge/Z7oLhYqhHZ6gFO6C9LVTVG8h60AcAP_BLYWDvWKzsws

LE will never tesolve .local addresses as they cannot be reached from the internet as a domain name.

Another option might be DNS authorisation during setup. You need to be able to update DNS then.
Either manual (which doesn't scale well) or through a DNS Plugin...  LetsEncrypt 0.20+   has those options as plugins.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.