Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- text error warn system array login
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ /data/nginx/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- [3/16/2023] [9:06:42 AM] [Migrate ] › ℹ info Current database version: none
- [3/16/2023] [9:06:42 AM] [Setup ] › ℹ info Logrotate Timer initialized
- [3/16/2023] [9:06:42 AM] [Setup ] › ⚠ warning Error: Command failed: logrotate /etc/logrotate.d/nginx-proxy-manager
- error: skipping "/data/logs/fallback_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/letsencrypt-requests_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-10_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-11_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-12_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-13_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-14_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-15_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-16_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-1_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-2_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-3_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-4_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-5_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-6_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-7_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-8_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-9_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/fallback_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/letsencrypt-requests_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-10_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-11_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-12_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-13_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-14_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-15_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-16_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-1_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-2_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-3_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-4_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-5_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-6_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-7_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-8_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- error: skipping "/data/logs/proxy-host-9_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
- at ChildProcess.exithandler (node:child_process:402:12)
- at ChildProcess.emit (node:events:513:28)
- at maybeClose (node:internal/child_process:1100:16)
- at Socket.<anonymous> (node:internal/child_process:458:11)
- at Socket.emit (node:events:513:28)
- at Pipe.<anonymous> (node:net:301:12)
- [3/16/2023] [9:06:42 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
- [3/16/2023] [9:06:42 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- [3/16/2023] [9:06:43 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
- [3/16/2023] [9:06:43 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
- [3/16/2023] [9:06:43 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
- [3/16/2023] [9:06:43 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
- [3/16/2023] [9:06:43 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
- [3/16/2023] [9:06:43 AM] [Global ] › ℹ info Backend PID 246 listening on port 3000 ...
- [3/16/2023] [9:06:44 AM] [SSL ] › ✖ error Error: Command failed: /usr/sbin/nginx -t -g "error_log off;"
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- nginx: configuration file /etc/nginx/nginx.conf test failed
- at ChildProcess.exithandler (node:child_process:402:12)
- at ChildProcess.emit (node:events:513:28)
- at maybeClose (node:internal/child_process:1100:16)
- at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
- ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
- ❯ /etc/nginx/conf.d/include/assets.conf
- ❯ /etc/nginx/conf.d/include/block-exploits.conf
- ❯ /etc/nginx/conf.d/include/force-ssl.conf
- ❯ /etc/nginx/conf.d/include/ip_ranges.conf
- ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
- ❯ /etc/nginx/conf.d/include/proxy.conf
- ❯ /etc/nginx/conf.d/include/ssl-ciphers.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/default_host/site.conf
- ❯ /data/nginx/proxy_host/3.conf
- ❯ /data/nginx/proxy_host/4.conf
- ❯ /data/nginx/proxy_host/5.conf
- ❯ /data/nginx/proxy_host/8.conf
- ❯ /data/nginx/proxy_host/10.conf
- ❯ /data/nginx/proxy_host/9.conf
- ❯ /data/nginx/proxy_host/13.conf
- ❯ /data/nginx/proxy_host/15.conf
- ❯ /data/nginx/proxy_host/6.conf
- ❯ /data/nginx/temp/letsencrypt_17.conf
- nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-6/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-6/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement