I have MS Windows Server 2022 LightSail Instance with static IP, IIS up & running, and a registered domain, let's call it my-web-site.com (domain name here is fictious).
I have bound my registered domain my-web-site.com to the IIS Default Web Site and I have created a Domain Zone for this domain with 'A' DNS record pointing to my LightSail Instace's static IP.
Then I have set proper Amazon's domain name servers records on my domain's registar's site so that the Default IIS Web Site has become available by http://my-web-site.com address.
Next I have used "Windows ACME Simple (WACS)" (https://github.com/win-acme/win-acme) procedure to setup renewable "Let's Encrypt" Security Certificate. It was installed correctly.
And I expected my Default IIS Web Site to become SSL/TLS protocol protected. But accessing my web site secure https://my-web-site.com URL results in ERR_CONNECTION_TIMED_OUT error.
I must note I did test the same as above SSL setup on an MS Windows Server 2019 running as a VPS on another hosting provider site, using a different domain name and it worked flawlessly - I have got my test web site secured and accessible using SSL/TLS protocol.
What additional steps I have to do to make my MS Windows Server 2022 LightSail instance's Default IIS Web Site be available using SSL/TLS protocol?
Hello, Riku -- Yes, your advice helped, I have opened port 443 in Lightsail Firewall and HTTPS access works now for my web site. I must only note that when adding an IPv4 Firewall rule port 443 should be opened for 'Any ApV4 Address' - if port 443 is restricted just to the static IP of the Lightsail instance the issue with HTTPS timeout still occurs. Thank you!