I bought a PositiveSSL from Namecheap today and followed the instructions at: [image] 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… Which included placing ssl.key and ssl.crt at /var/discourse/shared/standalone/ssl/ and adding the additional templates to app.yml. I have set up the A record to point to the IP Address of the droplet/instance. The site was running perfectly before on both Google Compute and then on Digital Ocean (for testing) but once I enabled SSL, it went down. If I type in www.hostname.com or the IP address, it resolves to https://hostname.com and gives a “Unable to connect” or “Server not found” error. There are no errors in the logs. If someone can help, it would be massively appreciated. I have been going at this for 10 hours straight without any luck :anguished:

I solved the issue by removing the url redirect. The bare redirect was creating a loop due to nginx. Hope this helps someone in future. A big thank you to @cpradio and @fefrei for their help!

Can you post your app.yml here, without the credentials for SMTP?

@cpradio I have 2 TXT records (one SPF and one DKIM for sending mail through Sparkpost) and 1 URL redirect record. However, everything was resolving nicely before the SSL change.

Can you tell us which hostname your installation should be running at?

@fefrei here are the screenshots: [image] [image] I was using Google Compute before. I have tried again with DO, but no luck..

You just pasted your sparkpost password :sadpanda: Please change that password as immediately.

In the meantime, it looks like @cpradio was right in suspecting a DNS problem. I get SERVFAIL when resolving your hostname – both with and without the WWW.

@fefrei Oops have corrected it. Should I try re-issuing the certificate or should I try fixing the DNS records?

DNS should be your first priority – as long as this is broken, your server doesn’t even have a chance to present any SSL certificate :slight_smile:

Hmm, the only A record I have is pointed to the DO droplet. I will try with Namecheap support and report back. Thank you guys!\ [image]

Site down after enabling SSL

Product Support Self-hosting

cpradio (cpradio) July 3, 2016, 7:01pm 3

And do you have a non-www A record defined too?

Topic		Replies	Views
Problem in installing Let's Encrypt SSL for www and non-www Self-hosting	10	4976	December 3, 2019
Cannot connect to IP address and no errors in log Self-hosting	7	2263	January 14, 2019
Adding SSL certificate Self-hosting unsupported-install	3	1214	June 14, 2024
Making 'www' work with Discourse Product Support	30	3040	May 15, 2020
Correct DNS records to set when Discourse is hosted on WWW subdomain? Self-hosting	2	1269	May 9, 2020

Site down after enabling SSL

Related topics