# Timeout when trying HTTPS

**URL:** <https://community.letsencrypt.org/t/timeout-when-trying-https/141596>\
**Category:** Help\
**Created:** [December 30, 2020, 8:25am UTC](https://community.letsencrypt.org/t/timeout-when-trying-https/141596 "2020-12-30T08:25:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![iiacob](https://avatars.discourse-cdn.com/v4/letter/i/c5a1d2/32.png) [@iiacob](https://community.letsencrypt.org/u/iiacob)\
**Post date:** [December 30, 2020, 8:25am UTC](https://community.letsencrypt.org/t/timeout-when-trying-https/141596/1 "2020-12-30T08:25:35Z")

</div>

Hi Let's Encypt community,

I have installed a wildcard certificate on my IIS 10.0 website (hosted on [aws.amazon.com](http://aws.amazon.com)) and even after the binding was added succesfully, the certificate doesn't seem to work - when I request [https://application.redmedsolutions.ro/redmed](https://application.redmedsolutions.ro/redmed) from my Chrome browser, the request times out and no page get's displayed. Can anybody give me a hint about what's going on?

My domain is: \*.redmedsolutions.ro

I ran this command: wacs.exe as Administrator

It produced this output:

My web server is (include version): IIS 10.0

The operating system my web server runs on is (include version): Windows Server 2019

My hosting provider, if applicable, is: [aws.amazon.com](http://aws.amazon.com)

I can login to a root shell on my machine (yes or no, or I don't know): yes

Thank you in advance,  
John

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [December 30, 2020, 8:43am UTC](https://community.letsencrypt.org/t/timeout-when-trying-https/141596/2 "2020-12-30T08:43:49Z")

</div>

Have you opened port 443 (TCP) in your AWS Security Group and also the Windows Firewall?

---

<div class="post-metadata">

**Author:** ![iiacob](https://avatars.discourse-cdn.com/v4/letter/i/c5a1d2/32.png) [@iiacob](https://community.letsencrypt.org/u/iiacob)\
**Post date:** [December 30, 2020, 9:00am UTC](https://community.letsencrypt.org/t/timeout-when-trying-https/141596/3 "2020-12-30T09:00:28Z")

</div>

Thank you for your suggestion \_az. Even though I have opened port 443 yesterday, I checked the Inbound rules once more. I added two Inbound rules for each AWS Security group and that solved the issue. I was concerned more with the other opperations - DNS Chalenge, defining the IIS binding and so on - than with the firewall rules. Problem solved!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [January 29, 2021, 9:00am UTC](https://community.letsencrypt.org/t/timeout-when-trying-https/141596/4 "2021-01-29T09:00:42Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.