# Reverse Proxy and HTTPS **URL:** https://meta.discourse.org/t/reverse-proxy-and-https/109342 **Category:** Support **Tags:** unsupported-install **Created:** [February 16, 2019, 7:26pm UTC](https://meta.discourse.org/t/reverse-proxy-and-https/109342 "2019-02-16T19:26:17Z") **Posts on this page:** 1 **Showing post:** 14
### 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, 8:27am UTC](https://meta.discourse.org/t/reverse-proxy-and-https/109342/14 "2019-02-17T08:27:32Z")
> [@Amazon AWS EC2 - HTTPS 443 does not work](https://meta.discourse.org/t/amazon-aws-ec2-https-443-does-not-work/109340): > > 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] With HTTPS I get the chrome browser error “ERR\_CONNECTION\_REFUSED” I have already allowed 80 and 443 withing Amazon EC2: 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? --- _[View the full topic](https://meta.discourse.org/t/reverse-proxy-and-https/109342)._