Fails with no such file error

[rlaferla]

nginx_1 | 2019/10/13 01:17:59 [emerg] 1#1: open() "/etc/letsencrypt/options-ssl-nginx.conf" failed (2: No such file or directory) in /etc/nginx/conf.d/app.conf:22
nginx_1 | nginx: [emerg] open() "/etc/letsencrypt/options-ssl-nginx.conf" failed (2: No such file or directory) in /etc/nginx/conf.d/app.conf:22
certbot_1 | Saving debug log to /var/log/letsencrypt/letsencrypt.log
certbot_1 |
certbot_1 | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
certbot_1 |
certbot_1 | No renewals were attempted.
certbot_1 | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[rlaferla]

The init-letsencrypt.sh requires that you create a "conf" subdirectory under "data" before you run it.

[rlaferla]

This is actually an issue that can be resolved by adding the directory and file to this repository.

[wmnnd]

Thanks for pointing this out! Would you create a pull request for the 2.x branch to add folder creation?

[sharpist]

I keep getting this problem. The script init-letsencrypt.sh is not working.

[tavor118]

ng01 | 2019/11/30 16:49:08 [emerg] 1#1: unexpected end of file, expecting ";" or "}" in /etc/letsencrypt/options-ssl-nginx.conf:2
ng01 | nginx: [emerg] unexpected end of file, expecting ";" or "}" in /etc/letsencrypt/options-ssl-nginx.conf:2
@wmnnd Tried to use v.2.x, but got this error
Used this configuration - #52 (comment)

[chrstsrs]

There is the case that you have to make a few small changes to the init-letsencrypt.sh file in case that you are not using a single docker-compose.yml file. If you are using multiple docker-compose files you have to pass the file names to any docker-compose command. for example instead of:
docker-compose run ...
to replace it with the:
docker-compose -f docker-compose.yml -f docker-compose.production.yml run ...
There have to be done 5 replacements.

[nikolas-dev]

Same problem. Have any solution?

[chrstsrs]

I think you may have to make changes to the init-letsencrypt.sh. Just adapt it to your needs (you can see a change in docker-compose commands in my previous post)