Hi @gelwin
your server can't connect Letsencrypt. So it's impossible to create a certificate.
Please share your domain name, the picture is small.
What says
curl https://www.google.com/
PS: Is your domain really misorcares.org?
If yes, that can't work - https://check-your-website.server-daten.de/?q=misorcares.org - the domain isn't registered.
Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (no Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner.
Please read the basics:
i created my domain in windows server 2102r2
That’s not relevant. That’s not a worldwide unique, public visible domain name, only a private name on your local system.
Select a domain provider, then register a domain that isn’t registered. Then you can create a certificate with that domain name.
do i have to connect to the internet before i use lets encrpyt ?
Your server doesn’t necessarily have to be accessible on the Internet, but you do have to publicly register the domain name that you want to use. Let’s Encrypt issues only publicly-trusted certificates, which can only be issued to people who prove their control over publicly-registered domain names.
Unfortunately, your free domain misorcares.ml is still pointed at the IP address of the free domain registrar's server, not at your own computer.
When I said
I should probably have been more specific about the "doesn't necessarily have to be accessible" part: it looks to me like the Let's Encrypt client software that you're using at the moment does have the requirement that your site be publicly accessible on the Internet under the domain name that you're requesting a certificate for. Although this isn't a requirement from Let's Encrypt, it may be a requirement with the tools that you're using now.
There is a check of your domain - ~~7 hours old - https://check-your-website.server-daten.de/?q=misorcares.ml
Now it’s better, but it can’t work:
| Host | T | IP-Address | is auth. | ∑ Queries | ∑ Timeout |
|---|---|---|---|---|---|
| misorcares.ml | A | 195.20.52.215 Amsterdam/North Holland/Netherlands (NL) - OpenTLD Web Network No Hostname found | yes | 1 | 0 |
| AAAA | yes | ||||
| www.misorcares.ml | C | misorcares.ml | yes | 1 | 0 |
| A | 195.20.52.215 Amsterdam/North Holland/Netherlands (NL) - OpenTLD Web Network No Hostname found |
Your domain has an ip address.
But the content - is a frame to your private ip:
| Domainname | Http-Status | redirect | Sec. | G |
|---|---|---|---|---|
| • http://misorcares.ml/ | ||||
| 195.20.52.215 | 200 | 0.093 | H | |
| small content: | ||||
| • http://www.misorcares.ml/ | ||||
| 195.20.52.215 | 200 | 0.590 | H | |
| small content: | ||||
| • https://misorcares.ml/ | ||||
| 195.20.52.215 | -14 | 10.027 | T | |
| Timeout - The operation has timed out | ||||
| • https://www.misorcares.ml/ | ||||
| 195.20.52.215 | -14 | 10.027 | T | |
| Timeout - The operation has timed out | ||||
| • http://misorcares.ml/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de | ||||
| 195.20.52.215 | 200 | 0.103 | ||
| Visible Content: misorcares.ml |
Info: Html-Content with frame found, may be a problem creating a Letsencrypt certificate using http-01 validation
|
The content is always the same:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd">
<html> <head> <title>misorcares.ml</title> <meta name="description" content="misorcares.ml"> <meta name="keywords" content="misorcares.ml"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <script type="text/javascript"> var _gaq = _gaq || []; _gaq.push(['_setAccount', 'UA-23441223-3']); _gaq.push(['_setDomainName', 'none']); _gaq.push(['_setAllowLinker', true]); _gaq.push(['_trackPageview']); (function() { var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); })(); </script> </head>
<frameset rows="*">
<frame frameborder=0 src="http://209.200.39.244" name="dot_tk_frame_content" scrolling="auto" noresize>
</frameset>
</html>
A frameset, pointing to 209.200.39.244.
That’s a frame redirect of your hoster. You must change your A-record so your A-record has that ip address 209.200.39.244.
And the ip address must answer, if you want to use http-01 validation.