(SSL: error:02001002:system library:fopen:No such file or directory:fopen('/var/dis (…) I’m following the guide, but I can’t find anything about this error

Hi @slivo Let’s see the output of this: cd /var/discourse/shared/standalone/ssl ls -l Any clues?

cd ssl: No such file or directory

Hey @slivo This indicates that your Lets Encrypt setup did not create the certs when you last rebuilt your container. Of course, I an sure you know that already!

I had an install that failed something like that this week. Maybe try to do a ./launcher rebuild app

I rebuilt it again. I set it up according to the guidelines. Certified ssl set (/etc/nginx/sites-enabled/discourse.conf) but I have an error: SSL: error:0909006C:PEM routines:get_name:no start line:Expecting: TRUSTED CERTIFICATE I can’t take off with nxinx at all nginx.service: Control process exited, code=exited status=1 nginx.service: Failed with result 'exit-code'. Process: 3840 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=0/SUCCESS) Process: 25108 ExecReload=/usr/sbin/nginx -g daemon on; master_process on; -s reload (code=exited, status=1/FAILURE) // Failed to start A high performance web server and a reverse proxy server.

[image] slivo: // Failed to start A high performance web server and a reverse proxy server. Hey @slivo Thanks for the update on getting this setup. Are you setting up Discourse with the standard Docker build without a reverse proxy outside the container?

[image] neounix: standard Docker build without a reverse proxy outside yes and also im using this guide Run other websites on the same machine as Discourse

[image] slivo: yes and also im using this guide Hey @slivo In that link above, that is an outline of running Discourse in a docker container exposing the application using a UNIX socket to a reverse proxy. In that case, you should NOT enable SSL in the container yml file; and you SHOULD configure SSL with Let’s Encrypt using certbot outside the container on the reverse proxy only. The general high level architecture looks like this: WEB USERS REVERSE PROXY DOCKER CONTAINER Please post your yml file by xxxx’ing out your password and email addresses; and let’s see what you have going on. Thanks.

But now I don’t understand. Then I made a new certificate using certbot. And I have it here like: /etc/letsencrypt/live/myadress.com/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/myadress.com/privkey.pem Do I have to change the address in this file or like /etc/nginx/sites-enabled/discourse.conf or I’m doing it completely wrong ?

Hi @slivo When you are configuring a reverse proxy in front of another app with a nginx instance : you must be very specific about the location of the config files, in the container or out?

I can't set nginx: [emerg] cannot load certificate "/var/discourse/shared/standalone/ssl/ssl.crt": BIO_new_file() failed

Product Support Self-hosting

slivo (slivo) August 18, 2020, 8:16am 8

yes and also im using this guide Run other websites on the same machine as Discourse

Topic		Replies	Views
Disabe letsencrypt failed and Run discourse-setup had some not normal alert Self-hosting	6	1915	September 30, 2021
Regenerating LetsEncrypt keys from behind nginx Self-hosting	2	1506	August 29, 2018
Troubles installing SSL Self-hosting	5	2450	January 10, 2017
Allow SSL / HTTPS for your Discourse Docker setup Self-Hosting docker , how-to , advanced-setup	0	259379	March 18, 2014
Cannot install custom SSL new_file: no such file Product Support	6	2084	March 20, 2025

I can't set nginx: [emerg] cannot load certificate "/var/discourse/shared/standalone/ssl/ssl.crt": BIO_new_file() failed

Related topics