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…

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: [imagen] 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…

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'…

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 …

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.

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

La aplicación por defecto no se vuelve a compilar

Soporte Instalación

pfaffman (Jay Pfaffman) 24 Agosto, 2019 01:19 9

Simplemente ejecuta discourse-setup nuevamente y proporciona una dirección para Let’s Encrypt.

Tema		Respuestas	Vistas
Can't rebuild due to failed postgres 12 upgrade Self-hosting	44	4509	13 Julio 2020
Moving to New Server woes Support	16	582	10 Marzo 2025
Building bootstrap error Self-hosting	45	2737	20 Noviembre 2022
After rebuild, site won't load Self-hosting	13	2304	23 Abril 2018
Discourse Rebuild Self-hosting	14	2495	28 Enero 2021

La aplicación por defecto no se vuelve a compilar

Temas relacionados