I bought a PositiveSSL from Namecheap today and followed the instructions at:
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
@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.
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.
Iâm still wondering if your A Record is only handling www. What is the URL Redirect Record handling?
Because if the URL Redirect Record is redirecting to https://yourhost.com, and your A Record is only supporting www., then you are correct that nothing knows how to support it.
I have 2 A records with my setup, one for non-www and one for www.
@cpradio thanks but unfortunately thats not solving the issue. When I check the ssl certificate, it is not giving off any errors. Discourse is running from what I see in the logs, but it doesnât show up on the hostname or IP.
One thing that I noticed was I donât have these two files:
/etc/nginx/conf.d/discourse.conf
and
/var/www/discourse/config/discourse.conf
Wait, are you running other sites on the machine hosting Discourse too? If you arenât, you donât need web.socketed.template.yml, if you are, did you check the nginx configuration (or whatever HTTP server you are using) on the actual server to verify it is permitting HTTPS to pass through to Discourse?
These would be inside the container. Did you run ./launcher enter app before searching for those configuration files?
@cpradio no I am only running discourse and am not using the socket template. The strange thing is that my other domains work using the SSL with the exact same settings. I am trying with Namecheap support but its a weird bug - one SSL domain resolves using the same settings while another does not.