Hey, I set up the default discourse on a linux machine using this guide. It went super smoothly, and the site came up perfectly. I decided to allow users to connect via facebook, so I went through the facebook instructions linked to from the above link (I’d link again but new users can only post 2 links apparently). That ended up not working, but the site was still up and running (I don’t remember the error I got when trying to log in via facebook). While going through the facebook docs I saw something about needing to have https enabled, so I started going through these docs.. That all went well until the ./launcher rebuild app, where I got a postgres error. Which surprised me, because I hadn’t done anything to the postgres config (to the best of my knowledge). The first error is below: INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' rake aborted! PG::ConnectionBad: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"? I didn’t stop the postgres service, but I tried running service start postgres and it said it wasn’t installed. So I assume it’s installed automatically some other way than I’m used to. Any ideas on what I could have done wrong? Thanks my container/app.yml: templates: - "templates/web.template.yml" - "templates/web.ssl.template.yml" - "templates/web.letsencrypt.ssl.template.yml" - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" expose: - "80:80" # http - "443:443" # https params: db_default_text_search_config: "pg_catalog.english" db_shared_buffers: "128MB" env: LANG: en_US.UTF-8 LETSENCRYPT_ACCOUNT_EMAIL: 'myotheremail@gmail.com' UNICORN_WORKERS: 2 DISCOURSE_HOSTNAME: mysite.com DISCOURSE_DEVELOPER_EMAILS: 'myemail@gmail.com' DISCOURSE_SMTP_ADDRESS: smtp.gmail.com DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: myemail@gmail.com DISCOURSE_SMTP_PASSWORD: "myPa$$word" ## The http or https CDN address for this Discourse instance (configured to pull) ## see https://meta.discourse.org/t/14857 for details #DISCOURSE_CDN_URL: https://discourse-cdn.example.com volumes: - volume: host: /var/discourse/shared/standalone guest: /shared - volume: host: /var/discourse/shared/standalone/log/var-log guest: /var/log hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/discourse/docker_manager.git run: - exec: echo "Beginning of custom commands" - exec: echo "End of custom commands"

If you were following the official guide, HTTPS should have been set up automatically. Note at the very top of the guide you linked to: [image]Set up HTTPS support with Let's Encrypt :exclamation: This guide is only for existing installs where HTTPS is not enabled. Following the official setup guide automatically enables HTTPS by default.

Yes, that’s correct. And those are the instructions I followed. I did move to the facebook login connect guide first, but I am doubtful that that’s the issue. I went through the guide that you posted, and moved on to https, and now I’m having the issues listed above.

Ok, let’s regroup for a moment. These two guides are all you should need to follow: discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub Configure Facebook login for Discourse This one you do not want to follow since HTTPS is enabled by default: Set up HTTPS support with Let's Encrypt I would start fresh if possible and then report back any errors you receive when trying to log in with Facebook.

Ok, well when I finished the first guide, the site was up, but it wasn’t https. I assumed it wouldn’t be https until I enabled it. I’ll go back through the instructions, maybe I didn’t understand something, then I’ll report back.

Ok, I got the app back up, but I don’t see anywhere in these instructions that could possibly setup the site as https as there’s nowhere that involves a cert other than the Let’s Encrypt method at the bottom. What am I missing? Can you point me to where exactly in those instructions it would set up https?

It’s all done behind the scenes. When you enter your email in the last configuration step: [01%20PM]

I bet I hit ENTER to skip and didn’t even realize it. If that’s the case, would it just be best to re-run the config, or go through the let’s encrypt instructions. Keeping in mind, I have a little bit of content on the site right now and I don’t want it wiped. (Thanks again for your help)

Just run discourse-setup again and provide an address for let’s encrypt.

What a fantastic feature. I feel so ridiculous for missing that the first time around. Thanks to both of you, and the team for implementing that.

Defaultish app won't rebuild

Product Support Self-hosting

pfaffman (Jay Pfaffman) August 24, 2019, 2:09am 12

Is there some way to change the words that would have made you understood it sooner?

Topic		Replies	Views
Can't rebuild due to failed postgres 12 upgrade Self-hosting	44	4708	July 13, 2020
Moving to New Server woes Product Support	16	657	March 10, 2025
Building bootstrap error Self-hosting	45	2964	November 20, 2022
After rebuild, site won't load Self-hosting	13	2335	April 23, 2018
Discourse Rebuild Self-hosting	14	2563	January 28, 2021

Defaultish app won't rebuild

Related topics