I haven’t tried following the INSTALL-cloud.md instructions for a while, and they’ve changed and now there’s this new ./discourse-setup script. Problem is, it doesn’t work, at least on the base Ubuntu image for DigitalOcean. First, there isn’t execute permission on the ./discourse-setup script. Easy enough to change but might block some. After answering the prompts, I get the following. Press ENTER to continue, 'n' to try again, or ^C to exit: LETSENCRYPT_ACCOUNT_EMAIL change failed. web.ssl.template.yml enabled letsencrypt.ssl.template.yml enabled Unfortunately, there was an error changing containers/app.yml root@host:/var/discourse# This seems like some type of permissions issue, but not sure. Update: Apparently these is super (like hours) new, so I guess someone had to be first! :slight_smile:

I just ran it with letsencrypt on a fresh 2GB droplet (too lazy to fuss with setting up swap on a 1GB, but that should work too if you configure swap). wget -qO- https://get.docker.com/ | sh git clone https://github.com/discourse/discourse_docker.git /var/discourse cd /var/discourse/ ./discourse-setup app ./launcher start app And that was it! I’m glad it worked, as I’m dangerously close to hitting letsencrypt’s rate limits. [image] pztrick: I also had to follow advice in another thread and delete the /var/discourse/shared/standalone/ssl and /var/discourse/shared/standalone/letsencrypt folders. Then, SSL worked. @pztrick’s problem probably is due to stuff left about when the ports were broken and le.sh failed. That would make sense because letsencrypt needs access to those ports as part of the certification process, so that’s a fragility of the letsencrypt template. (@tgxworld, maybe we need to have that script delete those directories if le.sh fails? Or test on the front end to look for bogus certs and delete them before it runs again?) I think that discourse-setup should probably not call ./launcher bootstrap app itself in case people need to fuss with something. Right now, people will need to edit app.yml by hand to deal with (1) allowing no SMTP username and password (requiring something explicit to make sure that people don’t omit them carelessly) and (2) SiteSetting.notification_email if they use sparkpost. I hope to get the script to deal with those cases tomorrow, but there will always be edge cases. Having discourse-setup do just the, you know, Discourse setup seems reasonable, and it can say Successfully configured, to bootstrap use ./launcher start app just like launcher bootstrap does.

My server is back online, unfortunately I don’t have time at all to look into what’s going on though. I checked out HEAD~25 and rebuilt and it works. Hopefully that’ll narrow down where the problem might be for whoever looks into it. Edit: I decided to take a quick look anyway, my guess is it’s this bit which was removed from launcher.

I found the problem. and solved. in discourse-setup shell script at line 281 sed -i -e "s/^ #LETSENCRYPT_ACCOUNT_EMAIL: your.email@example.com/ LETSENCRYPT_ACCOUNT_EMAIL: $letsencrypt_account_email/w $changelog" $config_file you have to replace your.email@example.com with me@example.com and after that the script works

[image] penzoiders: you have to replace your.email@example.com with me@example.com and after that the script works Likely due to the change @codinghorror made 9 hours ago: https://github.com/discourse/discourse_docker/commit/650f4c25d4897dc36e0ebf04f46051cdb59c6528

[image] DeanMarkTaylor: Likely due to the change @codinghorror made 9 hours ago: yes, sorry, didn’t notice… I’m just a git-goat (pull and run) I should have checked that.. anyway glad it will be fixed. cheers

[image] savef: My server is back online, unfortunately I don’t have time at all to look into what’s going on though. I checked out HEAD~25 and rebuilt and it works. Hopefully that’ll narrow down where the problem might be for whoever looks into it. Edit: I decided to take a quick look anyway, my guess is it’s this bit which was removed from launcher. That looks like the problem with launcher to me. [image] penzoiders: sed -i -e “s/^ #LETSENCRYPT_ACCOUNT_EMAIL: your.email@example.com/ LETSENCRYPT_ACCOUNT_EMAIL: $letsencrypt_account_email/w $changelog” $config_file you have to replace your.email@example.com with me@example.com and after that the script works I’ve fixed the sed replacement so that it’s not so finicky about those addresses in a soon-to-be submitted PR. This seems to fix the config_file edits, but it looks to me that the launcher problem above is the real culprit. I’ll submit a PR that fixes launcher in a few minutes.

[image] tgxworld: The ports not being published problem has been fixed I went through the directions again (doing my app.yml manually for now) with a fresh/clean install starting from nothing, but the ports still weren’t active. I’m trying to the workaround (commenting out the line in launcher) in the other post, though, and that worked… but Lets Encrypt is still causing errors so the site isn’t functional.

@downey After pulling latest changes for port expose, port 80 worked but not SSL. Then, for SSL, I also had to follow advice in another thread and delete the /var/discourse/shared/standalone/ssl and /var/discourse/shared/standalone/letsencrypt folders. Then, SSL worked. Could try that?

Sorry for the issues, the port problem was 100% my mistake! Thanks for that fix @tgxworld. We’re trying to make setup a bit easier by prompting people for common values using the discourse-setup script. I can confirm the version as of right now works fine, I just built and bootstrapped a site with it. I am not 100% sure the Let’s Encrypt stuff works, but @pfaffman will be testing it and looking into it today or tomorrow.

I found I still had to manually edit app.yml and then run sudo ./launcher bootstrap app. This was because the discourse-setup script requires SMTP username and password, and I don’t need to set that (it’s an internal SMTP server at my company). Fortunately I’d gone through the process recently so I knew what to do, but if I hadn’t done so before I might’ve been lost when the discourse-setup process said it couldn’t continue. Just posting in case anyone else runs into that.

Problems with INSTALL-cloud.md directions

Product Support Self-hosting

tgxworld (Alan Tan) April 27, 2016, 6:05pm 15

The ports not being published problem has been fixed. See https://meta.discourse.org/t/upgraded-docker-site-brokedown/43328/8?u=tgxworld

Topic		Replies	Views
Discourse not serving pages Self-hosting	25	3482	August 4, 2020
Discourse installation for beginners but are willing to be part of the community Self-hosting	62	5321	September 17, 2019
After Discourse installation can’t reach it in browser Self-hosting	24	4392	September 5, 2020
My Discourse is Down. Certificate Issue? Self-hosting	23	2304	February 22, 2023
Bootstrap error during Discourse install: ENOENT - /etc/runit/1.d/letsencrypt Self-hosting	24	824	November 21, 2025

Problems with INSTALL-cloud.md directions

Related topics