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: [image] I am trying to access the site at the moment via the public IP4: http://18.220.41.204 is working but not https://18.220.41.204. Can anybody help?

As I said earlier, IP based installs are wholly unsupported. Let’s encrypt will work immediately, the certificate verification method is DNS.

Https over a port without a certificate? How?

So this does not work? I tought it is working but I get a warning in the browser that this site is not secure.

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 :wink:

Did you run discourse-setup? Did you enable let’s encrypt there?

[image] chrisonline: but not https://18.220.41.204. It seems you fixed it using a certificate as above link is currently responding.

I pointed my subdomain now to the IP and rerun the setup with SSL. After a few hours it is now working.

Amazon AWS EC2 - HTTPS 443 does not work

Product Support

Stephen (Stephen) February 16, 2019, 7:19pm 5

Accessing via IP isn’t supported. What certificate are you using to access over 443? Self-signed?

Topic		Replies	Views
Discourse instance unreachable on AWS Product Support	27	4372	February 8, 2017
Discourse setup on aws ec2 doesn't work with default IPv4 DNS Self-hosting hosting	13	1714	September 3, 2021
Discourse not working on private AWS EC2 Self-hosting	2	705	May 3, 2023
HTTPS refused to connect at a direct IP address Self-hosting	2	1436	March 28, 2018
How to install Discourse in the AWS EC2 Instances(Ubuntu Server LTS)? Self-hosting	36	5510	March 30, 2019

Amazon AWS EC2 - HTTPS 443 does not work

Related topics