Hallo, after activating Lets Enrypt Templates and rebuilding Discourse nothing works: NGINX gives a cryptical error: [image] The strange thing is: there is no nginx directory in /ETC These templates are active: [image] These are the settings, the app has been rebuilt with [image] What ca…

you seem to be in your home directory (~) when you cd etc cd /etc/nginx should work

No, I have checked it in the correct directory: [image]

If this is a standard Docker install, you’ll also need to enter the app first. cd /var/discourse ./launcher enter app Assuming that succeeds, you can print line 46 of the config file with sed: sed -n '46p' /etc/nginx/conf.d/discourse.conf With the same templates as you and no specific modificati…

[image] Simon_Manning: sed -n '46p' /etc/nginx/conf.d/discourse.conf Thank you. I have found as follows: [image] As you see the field “Discourse hostname” is filled in app.yml: [image]

Looks like it’s failing to substitute the hostname for some reason but I’m not sure why that might be. When you rebuilt Discourse, did you do it by running these commands? cd /var/discourse ./launcher rebuild app The only difference I can see between what you and I have is the use of a hyphen in t…

Yeah, this is how I have rebuilt the app … After rebuild seems everythin to work: [image]

If you rebuilt a bunch of times then you hit the let’s encrypt rate limits. There is no nginx on the server, it’s inside the discourse container. That’s why you can’t find it. [image] ITAS-Isti: After rebuild seems everythin to work: So you solved your problem by rebuilding? You should mar…

I have simply meant, that I how found no error or anything like this in the log. (See Screenshot) The build-process SEEMS to be OK … I have now requested the final domain. I will rebuild the app with it. After removing all the lets encrypt specific seetings and using the original host name of the…

Hi Simon, I have rebuild it again and I have seen that the ceritificate is issue with the wrong name: [image] Is the app.yml possibly configured on a wrong way? app.txt (4,1 KB) What do you mean? I

line 51 DISCOURSE_HOSTNAME: deinbalkonnetz.de that is not your config file. where did you get it from ?

Après activation de HTTPS, Discourse ne fonctionne plus

Soutien Installation

IAmGav (Gavin Perch) Octobre 27, 2021, 10:46 11

ligne 51

DISCOURSE_HOSTNAME: deinbalkonnetz.de

ce n’est pas votre fichier de configuration. D’où l’avez-vous obtenu ?

Sujet		Réponses	Vues
Using letsencrypt inside Discourse Self-hosting letsencrypt	11	923	Mars 22, 2019
Http shows nginx page Self-hosting	6	365	Mai 10, 2024
HTTPS : issue while trying to set up SSL certification Self-hosting	24	2696	Août 31, 2019
Discourse website not loading after installation without enabling Let's Encrypt Self-hosting	17	3158	Avril 9, 2020
Set up Let’s Encrypt with multiple domains / redirects Sysadmins how-to , letsencrypt	111	21709	Décembre 16, 2025

Après activation de HTTPS, Discourse ne fonctionne plus

Sujets connexes