We successfully installed Discourse through DigitalOcean using the following guide: discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub Our DNS is fully propagated, and we also installed our SSL CERTS per the following guide: [תמונה] Allow SSL / HTTPS for your Discourse Docker setup Self-Hosting This guide is likely out of date as there are now very few reasons not to use the built-in Let’s Encrypt certificate that Just Works. See also: 2023-04-10 @pfaffman says: This is left here mostly for historical purposes. So you’d like to enable SSL for your Docker-based Discourse setup? Let’s do it! This guide assumes you used all the standard install defaults – a container configuration file at/var/discourse/containers/app.yml and Discourse docker is installed at: /var/discourse Buy a SS… When browsing to our Discourse installation via IP or domain name, we get the following message: This site can’t be reached XX.XX.XX.XX refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED What could be the problem?

Using let’s encrypt is an easy way to get ssl.

I am running into this same issue, To rebuild with plain HTTP, does that require just commenting out the SSL template line in app.yml?

Yes, but browsers that have visited your site will refuse to connect. You really should use https.

For anyone that face it in the future, make sure to not exceed the rate limit of LetsEncrypt: [תמונה] After initial setup of DigitalOcean droplet, get Refused to Connect error Self-hosting Just to point out something that happened to me. I used a testing server whose setup is entirely done by ansible, and after I use the site, I destroy it (ansible handles the destruction of the droplets, digital ocean spaces and so on, so that I’m not charged when not using). What happened is that LetsEncrypt have rate limits, and my domain exceeded, so I started receiving the error that the page couldn’t be reached and it was a bit hard to track the reason to the rate limit of certificates (fir… You can see if it was exceeded in the logs: ./launcher logs app

I met exectly the same prompt from chrome. For my case there were several configuration that was wrongly setted, some were Discourse settings, some were hosting server configuration. I post my checklist here for you as a reference: Check /var/discourse/containers/app.yml (Follow this post: Allow SSL / HTTPS for your Discourse Docker setup ) Make sure you either allows https/http (open the 443 port, uncomment the ssl related template config, and the Let’sEncrypted related configs), or only http request (ban the 443 port, comment out the ssl related template config and Let’sEncrypted related configs). If any changes were made to app.yml, run ./launcher rebuild app to activate the updated configs. Run ./laucher logs app. If you failed frequently to rebuild a functional discourse server, like I did, you may at the same time had requested too much Let’s Encrypt credentials and exeeded their limit. Then run ./laucher logs app will print a json. with a 429 error included. Check your Security group settings for your ECS server instance In my case, Security group is simply a bundle of perssioned ports (for example, 80 HTTP 443 HTTPs), whichs allow you to control your server’s transportation with the outter space. Make sure to allow the ports that are necessary for hosting discourse. Check firewall settings In my case, step 3 didn’t open the required ports for me. Something wrong happened with my firewall settings. it’s weird that I never set the firewall for my server, but those ports were indeed opened after configured with apt install firewall-cmd firewall-cmd --permanent --add-port=20-21/tcp (… and the other ports) firewall-cmd --reload You check the status of opened ports for your domain with some online services.

Had this issue too - over the rate limit for certificates. Fixed by following your step #1 (commenting out the 2 SSL templates in app.yml) and opening up the site in another browser once rebuilt. Assuming I’ll be able to reenable SSL once a week passes.

Were you able to connect after a week passed?

Unable To Connect/Connection Refused due to https certificates

Product Support Self-hosting

codinghorror (Jeff Atwood) 9 באוקטובר,‏ 2016,‏ 12:18am 2

Almost certainly a SSL problem. Try rebuilding with plain HTTP first to make sure everything is working before adding on the complexity of HTTPS.

נושא		תגובות	צפיות
After initial setup of DigitalOcean droplet, get Refused to Connect error Self-hosting	3	8900	1 בינואר,‏ 2021
No connection accepted on http / https after fresh installation on Ubuntu 22.04 LTS Self-hosting	5	2624	16 בדצמבר,‏ 2022
Forum doesn't load after enabling SSL with Let's Encrypt Self-hosting	9	1369	8 באוגוסט,‏ 2018
Port issue - Please help Self-hosting	17	2276	19 בפברואר,‏ 2021
Discourse Setup Error Self-hosting	3	1223	22 בדצמבר,‏ 2021

Unable To Connect/Connection Refused due to https certificates

נושאים קשורים