Just installed Let’s Encrypt on Discourse and now the site won’t open. Any ideas what I may have done wrong? I uncommented the lines to install Let’s Encrypt and rebuilt the app. Now I’m getting “Safari can’t connect …” Is there anything I missed?

Did you also uncomment port 443 in the expose section? samples/standalone.yml main - "templates/web.ratelimited.template.yml" ## Uncomment these two lines if you wish to add Lets Encrypt (https) #- "templates/web.ssl.template.yml" #- "templates/web.letsencrypt.ssl.template.yml" ## which TCP/IP ports should this container expose? ## If you want Discourse to share a port with another webserver like Apache or nginx, ## see https://meta.discourse.org/t/17247 for details expose: - "80:80" # http - "443:443" # https params: db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to a max of 25% of the total memory. ## will be set automatically by bootstrap based on detected RAM, or you can override #db_shared_buffers: "256MB" ## can improve sorting performance, but adds memory usage per-connection #db_work_mem: "40MB" If there is a # in front of this line, You may remove it and rebuild.

How and when did you install discourse? Let’s encrypt has been the default for quite a while. You need to make sure that the ports are open, as suggested already. And if you rebuild too many times with stuff not configured rift you can hit rate limits with let’s encrypt.

Yep did that. I’m on an EC2 instance so I’m wondering if there’s somewhere else a redirect has been set up. @pfaffman it was set up already without SSL but I’m attempting to test it with Auth0 so I need https running on the site.

You might need to check the security settings to see that port 443 is open. If you run discourse-setup it’ll do a check to see if it can access itself on both ports via the host name.

Just tried it and it says it can’t reach the installation on both ports. Checked the security settings on the instance and I have ports open to the instance from my IP

For letsencrypt to work, you also need to allow their servers to be able to reach your instance. It’ll be best to open port 80 & 443 for 0.0.0.0/0 i.e. everywhere setting in the AWS security groups

Oh, Hey Clement. I just noticed that this was you! According to an email from last November, you have a load balancer in front of Discourse, so you’ll need to get the load balancer to handle https. That would explain why let’s encrypt wasn’t turned on for your instance. You’ll want to remove the let’s encrypt certificate (and it wouldn’t hurt to not open port 443, but it doesn’t much matter). And then figure out how to make your AWS load balancer do the https. This also explains why the ports aren’t open, as the load balancer is in the way.

Thanks Jay. I’ll check but I don’t think I put the dev one behind a load balancer. I’ll double check just in case.

[image] Clement Oke: I don’t think I put the dev one behind a load balancer. Hmm. I would think that you would have either, but it would explain what’s happening.

Nope. No load balancer. It’s pointing to the IP address of the instance. I’ll have to try something else.

Can't access site after Let's Encrypt install

Product Support Self-hosting

cokestroke (Clement Oke) September 7, 2022, 5:23pm 17

OK I’ll wait. That’s going to the bottom of my backlog then
Thanks for your help

Topic		Replies	Views
Discourse website not loading after installation without enabling Let's Encrypt Self-hosting	17	3338	April 9, 2020
Using letsencrypt inside Discourse Self-hosting letsencrypt	11	1004	March 22, 2019
Set up HTTPS support with Let's Encrypt Self-Hosting how-to , domains	2	111814	February 25, 2024
Lets Encrypt Certificate - Issuing Problem Self-hosting	2	787	November 6, 2023
Installed without error but site wont come up Self-hosting	12	2038	February 13, 2017

Can't access site after Let's Encrypt install

Related topics