Yesterday I almost lose my mind trying to figure out why Discourse wouldn’t load after a 100% fresh install on Digital Ocean. No error messages, followed every step by the book, even when I had successfully deployed a test install last year, but no browser could access the page. I was baffled!
The culprit was this seemingly innocent setting
discourse-setup. I figured "oh sure, I’ll just put the email and configure Let’s Encrypt later". Of course my assumption was incorrect, although the guide doesn’t mention anything about this. Turns out I couldn’t access Discourse with the IP because SSL is immediately enforced.
So, is it OK if I do a pull request for INSTALL-cloud.md with a big disclaimer for that configuration step? Surely someone else out there must be having the same issue.