# Amazon AWS EC2 - HTTPS 443 does not work **URL:** https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340 **Category:** Support **Tags:** unsupported-install **Created:** [February 16, 2019, 7:11pm UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340 "2019-02-16T19:11:15Z") **Posts on this page:** 11 **Page:** 1
### Author: ![chrisonline](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisonline/32/130860_2.png) [@chrisonline](https://meta.discourse.org/u/chrisonline) #### Post date: [February 16, 2019, 7:11pm UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/1 "2019-02-16T19:11:15Z")
I have setup the Discourse installation on a Amazon AWS EC2 without Let’s Encrypt. The docker is listening on port 80 and 443 but I can’t access the site via HTTPS. HTTP works fine but not HTTPS. ![image](https://global.discourse-cdn.com/meta/original/3X/e/7/e75d97e42a1e6b73acf849d0da08c3829139b4b2.png) With HTTPS I get the chrome browser error “ERR\_CONNECTION\_REFUSED” I have already allowed 80 and 443 withing Amazon EC2: ![image](https://global.discourse-cdn.com/meta/original/3X/c/8/c80d2c4979af93cd283ab766929896f098be558a.png) I am trying to access the site at the moment via the public IP4: [http://18.220.41.204](http://18.220.41.204) is working but not [https://18.220.41.204](https://18.220.41.204). Can anybody help? ---
### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen) #### Post date: [February 16, 2019, 7:13pm UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/2 "2019-02-16T19:13:58Z")
Https over a port without a certificate? How? ---
### Author: ![chrisonline](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisonline/32/130860_2.png) [@chrisonline](https://meta.discourse.org/u/chrisonline) #### Post date: [February 16, 2019, 7:18pm UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/4 "2019-02-16T19:18:53Z")
So this does not work? I tought it is working but I get a warning in the browser that this site is not secure. ---
### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen) #### Post date: [February 16, 2019, 7:19pm UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/5 "2019-02-16T19:19:30Z")
Accessing via IP isn’t supported. What certificate are you using to access over 443? Self-signed? ---
### Author: ![chrisonline](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisonline/32/130860_2.png) [@chrisonline](https://meta.discourse.org/u/chrisonline) #### Post date: [February 16, 2019, 7:21pm UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/6 "2019-02-16T19:21:26Z")
No certificate at the moment. This was only a test before I point my domain subdomain to the Amazon EC2. I will create another thread of my main problem because I wanted to test this with Amazon EC2 😉 ---
### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman) #### Post date: [February 17, 2019, 12:34am UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/7 "2019-02-17T00:34:36Z")
Did you run discourse-setup? Did you enable let’s encrypt there? ---
### Author: ![jose-zama](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jose-zama/32/131701_2.png) [@jose-zama](https://meta.discourse.org/u/jose-zama) #### Post date: [February 17, 2019, 4:52am UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/8 "2019-02-17T04:52:09Z")
> [@chrisonline](#): > > but not [https://18.220.41.204](https://18.220.41.204). It seems you fixed it using a certificate as above link is currently responding. ---
### Author: ![chrisonline](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisonline/32/130860_2.png) [@chrisonline](https://meta.discourse.org/u/chrisonline) #### Post date: [February 17, 2019, 6:19am UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/9 "2019-02-17T06:19:23Z")
I pointed my subdomain now to the IP and rerun the setup with SSL. After a few hours it is now working. ---
### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen) #### Post date: [February 17, 2019, 7:08am UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/10 "2019-02-17T07:08:23Z")
As I said earlier, IP based installs are wholly unsupported. Let’s encrypt will work immediately, the certificate verification method is DNS. ---
### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system) #### Post date: [March 12, 2022, 2:28am UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/11 "2022-03-12T02:28:24Z")
---
### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie) #### Post date: [March 12, 2022, 3:05am UTC](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340/12 "2022-03-12T03:05:28Z")