Hi, let's encrypt no get ssl.Why?
Welcome to the Let's Encrypt Community, @Fdt! 
Let's Encrypt only provides certificates for publicly-recognized domain names (with public DNS entries).
6 Likes
How make certificates for publicly-recognized domain names (with public DNS entries) in iis or windows server 2019
Learning how to setup websites is generally out of scope for this forum and you should attend a suitable training course, or get help from a local expert to get you started.
In general, you would register your own unique domain name using a domain registrar such as Cloudflare, Porkbun, namecheap etc, then point that domain at your servers public IP address and open TCP port 80 and port 443 on your server firewall, then setup a site in IIS and add an http binding with that domain as the hostname.
Once you can browse to your website using http://<yourdomain> you're ready to start adding certificates using something like win-acme or Certify The Web in order to secure the communication with your site using TLS.
Certificates are used to ensure the trusted identity of your server (acting as a particular domain name) and in turn this trust is used to start the process of secure communication over TLS. As they need to be publicly trusted your domain needs to be verified and the simplest way to do that is to check that the server asking for a certificate is the same one that hosts the website, this is called HTTP authorization (or validation) or an HTTP challenge/response.
4 Likes
Probably the same as what you did with the fake domain name earlier, but now with an actual public domain name you own and is configured on your server.
Are you sure this is the question you need to be asking yourself? Because it feels more like you're asking "how do I get a publicly recognized domain name", which is indeed, as already mentioned by Christopher, outside of the scope of this Community.
3 Likes
Finish
I make web site on beget.com.Get my domen name. Then install iis, make in iis site. My site is loaded on port 80 with the http protocol
No work https, i can't install ssl via let's encrypt, Errors appear
You're making good progress. The current problem is that your server is not accepting public TCP port 80 (http) connections and this is most likely caused by either your Windows Firewall or your VM hosts networking settings (you likely need to enable http or TCP port 80 traffic to your VM in your hosting control panel).
I can see that your server is accepting HTTPS (TCP port 443) connections ok, so you just need to fix the port 80 problem. A good test is to use your phone data (not wifi) to browse to your site as http (not https), that way you can confirm your site is publicly accessible on port 80.
3 Likes
The problem was Windows Firewall I didn't miss port 80
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.