Durch die Nutzung von AWS re:Post stimmt du den AWS re:Post Nutzungsbedingungen
AWS re:Postre:Post

Using Windows ACME Simple (WACS) to setup Let's Encrypt Certificate on MS Windows Server 2022 LightSail Instance

0

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?

Themen
KalkulationVernetzung & Bereitstellung von Inhalten.NET auf AWS
Tags
Amazon LightsailAmazon Route 53.NET auf AWSWindows
Sprache
English
Shamil
gefragt vor 9 Monaten524 Aufrufe
2 Antworten
0
Akzeptierte Antwort

Hello.
It is a timeout error, please check your firewall settings.
Make sure HTTPS (443) is allowed in Lightsail's firewall.
Even if the Lightsail firewall is not a problem, check to see if the Windows Server OS firewall is preventing it.
https://lightsail.aws.amazon.com/ls/docs/en_us/articles/understanding-firewall-and-port-mappings-in-amazon-lightsail

profile picture
EXPERTE
Riku_Kobayashi
beantwortet vor 9 Monaten
profile picture
EXPERTE
Gary Mclean
überprüft vor 9 Monaten
  • Shamil
    vor 9 Monaten

    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!

0

Just a screenshot to comment on Riku's advice, which helped to solve the subject issue.

Enter image description here

Shamil
beantwortet vor 9 Monaten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen

Relevanter Inhalt