etc/letsencrypt/live

[jorgeg73]

Hi to all. I am new at docker and more nginx.
I am getting this error Can't open /etc/letsencrypt/live/npm-6/fullchain.pem for reading, No such file or directory, I ave gone to the directory and there is no live folder so i think that's the problem. Is there a nother way of fixing it before i try a new installation? or is it another problem that i am not seeing?.
Thank you

),
[8/24/2020] [5:22:12 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-6/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-6/fullchain.pem for reading, No such file or directory,
3069211992:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r'),
3069211992:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[8/24/2020] [5:22:12 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-8/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-8/fullchain.pem for reading, No such file or directory,
3070027096:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-8/fullchain.pem','r'),
3070027096:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening,
[cont-finish.d] executing container finish scripts...,
[cont-finish.d] done.,
[s6-finish] waiting for services.,
finish: applet not found,
[s6-finish] sending all processes the TERM signal.,
[s6-finish] sending all processes the KILL signal and exiting.,
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.,
[s6-init] ensuring user provided files have correct perms...exited 0.,
[fix-attrs.d] applying ownership & permissions fixes...,
[fix-attrs.d] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,
❯ Enabling IPV6 in hosts: /etc/nginx/conf.d,
❯ /etc/nginx/conf.d/include/assets.conf,
❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf,
❯ /etc/nginx/conf.d/include/ssl-ciphers.conf,
❯ /etc/nginx/conf.d/include/proxy.conf,
❯ /etc/nginx/conf.d/include/ip_ranges.conf,
❯ /etc/nginx/conf.d/include/force-ssl.conf,
❯ /etc/nginx/conf.d/include/block-exploits.conf,
❯ /etc/nginx/conf.d/include/resolvers.conf,
❯ /etc/nginx/conf.d/default.conf,
❯ /etc/nginx/conf.d/production.conf,
❯ Enabling IPV6 in hosts: /data/nginx,
❯ /data/nginx/proxy_host/3.conf,
[8/24/2020] [5:36:24 AM] [Migrate ] › ℹ info Current database version: 20200410143840,
[8/24/2020] [5:36:24 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...,
[8/24/2020] [5:36:24 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json,
[8/24/2020] [5:36:24 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4,
[8/24/2020] [5:36:24 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6,
[8/24/2020] [5:36:25 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized,
[8/24/2020] [5:36:25 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry...,
[8/24/2020] [5:36:25 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized,
[8/24/2020] [5:36:25 AM] [Global ] › ℹ info Backend PID 207 listening on port 3000 ...,
[8/24/2020] [5:36:27 AM] [Nginx ] › ℹ info Reloading Nginx,
[8/24/2020] [5:36:27 AM] [SSL ] › ℹ info Renew Complete,
[8/24/2020] [5:36:27 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-4/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-4/fullchain.pem for reading, No such file or directory,
3070006616:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-4/fullchain.pem','r'),
3070006616:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[8/24/2020] [5:36:27 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-3/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-3/fullchain.pem for reading, No such file or directory,
3069994328:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-3/fullchain.pem','r'),
3069994328:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[8/24/2020] [5:36:27 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-2/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-2/fullchain.pem for reading, No such file or directory,
3069822296:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r'),
3069822296:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[8/24/2020] [5:36:27 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-1/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-1/fullchain.pem for reading, No such file or directory,
3069236568:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-1/fullchain.pem','r'),
3069236568:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[8/24/2020] [5:36:27 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-6/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-6/fullchain.pem for reading, No such file or directory,
3069318488:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r'),
3069318488:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[8/24/2020] [5:36:27 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-5/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-5/fullchain.pem for reading, No such file or directory,
3069842776:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-5/fullchain.pem','r'),
3069842776:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[8/24/2020] [5:36:27 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-7/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-7/fullchain.pem for reading, No such file or directory,
3069355352:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-7/fullchain.pem','r'),
3069355352:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),
[8/24/2020] [5:36:27 AM] [SSL ] › ✖ error Certificate is not valid (Command failed: openssl x509 -in /etc/letsencrypt/live/npm-8/fullchain.pem -subject -noout,
Can't open /etc/letsencrypt/live/npm-8/fullchain.pem for reading, No such file or directory,
3069801816:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/etc/letsencrypt/live/npm-8/fullchain.pem','r'),
3069801816:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76:,
unable to load certificate,
),

[gregfr]

In your docker-compose.yml file, please check that there's a valid volume configured for the letsencrypt, like this:

    volumes:
      - ./config.json:/app/config/production.json
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

[jorgeg73]

I have look for it. There a lot docker-compose.yml.
/volumes/portainer_data/_data/compose/2/docker-compose.yml
I look at it in this path.
/srv/dev-disk-by-label-Docker/Docker/volumes/portainer_data/_data/compose#
theres 5 folder i look at all of them and it something to do whit my other containers that i have install in docker but can not find the one for nginx or the folder has you mention.
thnks

find . -name docker-compose.yml
./overlay2/4b98f3caeadd18869467949215dcccd5f98d4ffbceb8b4302934bb183d1b9414/diff/app/node_modules/knex/scripts/stress-test/docker-compose.yml
./overlay2/4b98f3caeadd18869467949215dcccd5f98d4ffbceb8b4302934bb183d1b9414/diff/app/node_modules/knex/scripts/docker-compose.yml
./overlay2/4b98f3caeadd18869467949215dcccd5f98d4ffbceb8b4302934bb183d1b9414/diff/usr/local/share/.cache/yarn/v6/npm-knex-0.20.15-b7e9e1efd9cf35d214440d9439ed21153574679d-integrity/node_modules/knex/scripts/stress-test/docker-compose.yml
./overlay2/4b98f3caeadd18869467949215dcccd5f98d4ffbceb8b4302934bb183d1b9414/diff/usr/local/share/.cache/yarn/v6/npm-knex-0.20.15-b7e9e1efd9cf35d214440d9439ed21153574679d-integrity/node_modules/knex/scripts/docker-compose.yml
./overlay2/b607fc2b318b3864965b6190d74ae46473953cdbf75ac4cc6539d3ed61ab252a/merged/usr/local/share/.cache/yarn/v6/npm-knex-0.20.15-b7e9e1efd9cf35d214440d9439ed21153574679d-integrity/node_modules/knex/scripts/stress-test/docker-compose.yml
./overlay2/b607fc2b318b3864965b6190d74ae46473953cdbf75ac4cc6539d3ed61ab252a/merged/usr/local/share/.cache/yarn/v6/npm-knex-0.20.15-b7e9e1efd9cf35d214440d9439ed21153574679d-integrity/node_modules/knex/scripts/docker-compose.yml
./overlay2/b607fc2b318b3864965b6190d74ae46473953cdbf75ac4cc6539d3ed61ab252a/merged/app/node_modules/knex/scripts/stress-test/docker-compose.yml
./overlay2/b607fc2b318b3864965b6190d74ae46473953cdbf75ac4cc6539d3ed61ab252a/merged/app/node_modules/knex/scripts/docker-compose.yml
./overlay2/b607fc2b318b3864965b6190d74ae46473953cdbf75ac4cc6539d3ed61ab252a/diff/app/node_modules/knex/scripts/stress-test/docker-compose.yml
./overlay2/b607fc2b318b3864965b6190d74ae46473953cdbf75ac4cc6539d3ed61ab252a/diff/app/node_modules/knex/scripts/docker-compose.yml
./overlay2/b607fc2b318b3864965b6190d74ae46473953cdbf75ac4cc6539d3ed61ab252a/diff/usr/local/share/.cache/yarn/v6/npm-knex-0.20.15-b7e9e1efd9cf35d214440d9439ed21153574679d-integrity/node_modules/knex/scripts/stress-test/docker-compose.yml
./overlay2/b607fc2b318b3864965b6190d74ae46473953cdbf75ac4cc6539d3ed61ab252a/diff/usr/local/share/.cache/yarn/v6/npm-knex-0.20.15-b7e9e1efd9cf35d214440d9439ed21153574679d-integrity/node_modules/knex/scripts/docker-compose.yml
./volumes/portainer_data/_data/compose/2/docker-compose.yml
./volumes/portainer_data/_data/compose/13/docker-compose.yml
./volumes/portainer_data/_data/compose/4/docker-compose.yml
./volumes/portainer_data/_data/compose/5/docker-compose.yml
./volumes/portainer_data/_data/compose/1/docker-compose.yml

[jorgeg73]

I uninstall the stack now i am getting this

[8/25/2020] [12:46:33 AM] [Global ] › ✖ error Config file /app/config/production.json cannot be read. Error code is: EISDIR. Error message is: EISDIR: illegal operation on a directory, read Error: Config file /app/config/production.json cannot be read. Error code is: EISDIR. Error message is: EISDIR: illegal operation on a directory, read at Config.util.parseFile (/app/node_modules/config/lib/config.js:771:13) at /app/node_modules/config/lib/config.js:601:26 at Array.forEach () at Config.util.loadFileConfigs (/app/node_modules/config/lib/config.js:600:16)at new Config (/app/node_modules/config/lib/config.js:116:27
at Object. (/app/node_modules/config/lib/config.js:1441:31)
at Module._compile (internal/modules/cjs/loader.js:1200:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1220:10)
at Module.load (internal/modules/cjs/loader.js:1049:32)
at Function.Module._load (internal/modules/cjs/loader.js:937:14)

[gregfr]

The "docker-compose.yml" file is a file that you have to provide yourself, it's a kind of recipe that is "cooked" by the "docker-compose" utility.
You need to write one like this: https://nginxproxymanager.com/setup/.
As you are using Portainer, you can use it to create a "stack", but if I remember correctly Portainer doesn't support version 3 docker-compose spec.

[jorgeg73]

I am following that one. still get error. But i think i know why. Let me scratch my head a little more and i will get back.
Thanks

[mdgnys]

I'm having the same issue on Open Media Vault. The volume is configured, as there are other files next to it. Only the live folder is having issues.

[chaptergy]

A lot has changed with certificates since the last activity in this issue. Closing this for now.

[flygav1]

im currently having this issue " I am receving the error with nginx reverse proxy manager of the following
" nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-1/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-1/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) "

[gregfr]

im currently having this issue " I am receving the error with nginx reverse proxy manager of the following " nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-1/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-1/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) "

did you check the letsencrypt folder is correctly mounted by Docker?

[flygav1]

im currently having this issue " I am receving the error with nginx reverse proxy manager of the following " nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-1/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-1/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) "

did you check the letsencrypt folder is correctly mounted by Docker?

I ended up re deploying the stack with a manuly created value as well as changing the valume location and it started up, had to basicly re start sadly... new certs... new loging. idk why after everyreboot or update it borks :(

[EeeMt]

I faced the same issue just now, And I solve it by creating the missing directory manually.

For me, I copy the whole directory /mnt/user/appdata/NginxProxyManager/letsencrypt/archive/npm-6 to /mnt/user/appdata/NginxProxyManager/letsencrypt/archive/npm-7(The missing one).
Operate it inside the docker container for avoid permission issue.

Just for someone may encounter this.