search

NginxProxyManager / nginx-proxy-manager

Docker container for managing Nginx proxy hosts with a simple, powerful interface
https://nginxproxymanager.com
MIT License
22.25k stars 2.57k forks source link

2.10.0 unable to start on clean install #2753

Open troykelly opened 1 year ago

troykelly commented 1 year ago

Checklist

Describe the bug

The :latest and 2.10.0 image fails to start either with an existing configuration, or with a clean install.

Nginx Proxy Manager Version

2.10.0

To Reproduce Steps to reproduce the behavior:

  1. Start a container
  2. Watch it fail

Expected behavior

The container should start

Screenshots

➜  lb-pi003 docker compose up -d && docker compose logs -f app
[+] Running 3/3
 ⠿ Network lb-pi003_default  Created                                                                                                                                                        0.8s
 ⠿ Container lb-pi003-db-1   Started                                                                                                                                                       27.7s
 ⠿ Container lb-pi003-app-1  Started                                                                                                                                                       18.7s
lb-pi003-app-1  | s6-rc: info: service s6rc-oneshot-runner: starting
lb-pi003-app-1  | s6-rc: info: service s6rc-oneshot-runner successfully started
lb-pi003-app-1  | s6-rc: info: service fix-attrs: starting
lb-pi003-app-1  | s6-rc: info: service fix-attrs successfully started
lb-pi003-app-1  | s6-rc: info: service legacy-cont-init: starting
lb-pi003-app-1  | s6-rc: info: service legacy-cont-init successfully started
lb-pi003-app-1  | s6-rc: info: service prepare: starting
lb-pi003-app-1  | ❯ Configuring npmuser ...
lb-pi003-app-1  | id: 'npmuser': no such user
lb-pi003-app-1  | ❯ Checking paths ...
lb-pi003-app-1  | ❯ Setting ownership ...
lb-pi003-app-1  | s6-rc: fatal: timed out
lb-pi003-app-1  | s6-sudoc: fatal: unable to get exit status from server: Operation timed out
lb-pi003-app-1  | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

Operating System

Rpi

Additional context

MaciejGorczyca commented 1 year ago

I updated containers and here is the time frame:

NPM doesn't start. Recreated entire compose stack and it doesn't work again. Rebooted only NPM container and it worked. Recreated entire compose stack and it doesn't work again. Rebooted only NPM and there are logs spamming every one second that "create table migrations, can't create table, errno 13 permission denied" and repeated reboots cause the errors to show up, NPM doesn't work again.

Rolling back to previous version.

jc21 commented 1 year ago

I've updated the docker image that might fix some user/group creation issues above and will highlight which folder is causing the hangs for permissions.

This image will also require an environment variable DEBUG=true to be set in the docker-compose or command.

services:
  npm:
    image: jc21/nginx-proxy-manager:github-s6-verbose
    environment:
      DEBUG: "true"
   // ...
jc21 commented 1 year ago

@Sungray I've spun up an Unraid server on amd64 and using your exact docker run command, things spin up just fine for me.

Pull the new build of the github-s6-verbose tag and try again. It show the chown command you're getting stuck on.

jc21 commented 1 year ago

@MaciejGorczyca your issue doesn't seem related to this, however let me know if you're using Sqlite or Mysql for your db engine

jc21 commented 1 year ago

@janaxhell pull the new build of the github-s6-verbose tag and try again and let me know how that goes

MaciejGorczyca commented 1 year ago

@MaciejGorczyca your issue doesn't seem related to this, however let me know if you're using Sqlite or Mysql for your db engine

I'm using jc21/mariadb-aria:latest and I updated from latest NPM which was at the time NPM BUILD VERSION 2.9.21 and 095bc8f commit from 2023-03-18 06:13:48 UTC. I'm using Win10 on server and run Docker in WSL.

I will try to update once again after a week or so and if issue persists I will create separate issue or let you know somehow.

Don't waste your time for this right now, might be fixed when current issue is resolved.

jc21 commented 1 year ago

@MaciejGorczyca yeah sounds like the database connection params might not be configured correctly for 2.10. I deprecated reading from config files and instead they need to be defined as env vars as per the docs

Sungray commented 1 year ago

@Sungray I've spun up an Unraid server on amd64 and using your exact docker run command, things spin up just fine for me.

Pull the new build of the github-s6-verbose tag and try again. It show the chown command you're getting stuck on.

Here's the new log, nothing much to show.

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service prepare: starting
s6-rc: fatal: timed out
s6-sudoc: fatal: unable to get exit status from server: Operation timed out
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
❯ Configuring npm user ...
❯ Configuring npm group ...
❯ Checking paths ...
❯ Setting ownership ...
jc21 commented 1 year ago

Ah yep can you add DEBUG=true to the docker environment variables?

janaxhell commented 1 year ago

@janaxhell pull the new build of the github-s6-verbose tag and try again and let me know how that goes

Ok, Orange Pi 3 LTS here, done. After deploy of stack with new compose lines, NPM started:

2023-05-04T09:18:43.096821845Z s6-rc: info: service s6rc-oneshot-runner: starting
2023-05-04T09:18:43.137312486Z s6-rc: info: service s6rc-oneshot-runner successfully started
2023-05-04T09:18:43.137871281Z s6-rc: info: service fix-attrs: starting
2023-05-04T09:18:43.157402868Z s6-rc: info: service fix-attrs successfully started
2023-05-04T09:18:43.157513952Z s6-rc: info: service legacy-cont-init: starting
2023-05-04T09:18:43.172619968Z s6-rc: info: service legacy-cont-init successfully started
2023-05-04T09:18:43.173138805Z s6-rc: info: service prepare: starting
2023-05-04T09:18:43.314444816Z + . /etc/s6-overlay/s6-rc.d/prepare/10-usergroup.sh
2023-05-04T09:18:43.317597920Z ++ set -e
2023-05-04T09:18:43.317685254Z ++ log_info 'Configuring npm user ...'
2023-05-04T09:18:43.317704921Z ++ echo -e '\E[1;34m? \E[1;36mConfiguring npm user ...\E[0m'
2023-05-04T09:18:43.317787380Z ? Configuring npm user ...
2023-05-04T09:18:43.317902089Z ++ id -u npm
2023-05-04T09:18:43.322571369Z ++ useradd -o -u 0 -U -d /tmp/npmuserhome -s /bin/false npm
2023-05-04T09:18:43.968932197Z ? Configuring npm group ...
2023-05-04T09:18:43.968932197Z ++ log_info 'Configuring npm group ...'
2023-05-04T09:18:43.969084115Z ++ echo -e '\E[1;34m? \E[1;36mConfiguring npm group ...\E[0m'
2023-05-04T09:18:43.970108830Z +++ get_group_id npm
2023-05-04T09:18:43.970238747Z +++ '[' npm '!=' '' ']'
2023-05-04T09:18:43.971294338Z +++ getent group npm
2023-05-04T09:18:43.971702049Z +++ cut -d: -f3
2023-05-04T09:18:43.989435874Z ++ '[' 1000 = '' ']'
2023-05-04T09:18:43.989531832Z ++ groupmod -o -g 0 npm
2023-05-04T09:18:44.106981020Z ++ groupmod -o -g 0 npm
2023-05-04T09:18:44.156457637Z +++ get_group_id npm
2023-05-04T09:18:44.156601555Z +++ '[' npm '!=' '' ']'
2023-05-04T09:18:44.157713354Z +++ getent group npm
2023-05-04T09:18:44.157888896Z +++ cut -d: -f3
2023-05-04T09:18:44.161834131Z ++ '[' 0 '!=' 0 ']'
2023-05-04T09:18:44.162319259Z ++ usermod -G 0 npm
2023-05-04T09:18:44.279925198Z +++ id -g npm
2023-05-04T09:18:44.283528430Z ++ '[' 0 '!=' 0 ']'
2023-05-04T09:18:44.283628264Z ++ mkdir -p /tmp/npmuserhome
2023-05-04T09:18:44.300129664Z ++ chown -R 0:0 /tmp/npmuserhome
2023-05-04T09:18:44.318470534Z + . /etc/s6-overlay/s6-rc.d/prepare/20-paths.sh
2023-05-04T09:18:44.319504666Z ++ set -e
2023-05-04T09:18:44.319580500Z ++ log_info 'Checking paths ...'
2023-05-04T09:18:44.319622917Z ? Checking paths ...
2023-05-04T09:18:44.319624958Z ++ echo -e '\E[1;34m? \E[1;36mChecking paths ...\E[0m'
2023-05-04T09:18:44.319732209Z ++ '[' '!' -d /data ']'
2023-05-04T09:18:44.319889960Z ++ '[' '!' -d /etc/letsencrypt ']'
2023-05-04T09:18:44.320191379Z ++ mkdir -p /data/nginx /data/custom_ssl /data/logs /data/access /data/nginx/default_host /data/nginx/default_www /data/nginx/proxy_host /data/nginx/redirection_host /data/nginx/stream /data/nginx/dead_host /data/nginx/temp /data/letsencrypt-acme-challenge /run/nginx /tmp/nginx/body /var/log/nginx /var/lib/nginx/cache/public /var/lib/nginx/cache/private /var/cache/nginx/proxy_temp
2023-05-04T09:18:44.326755130Z ++ touch /var/log/nginx/error.log
2023-05-04T09:18:44.336053650Z ++ chmod 777 /var/log/nginx/error.log
2023-05-04T09:18:44.345439045Z ++ chmod -R 777 /var/cache/nginx
2023-05-04T09:18:44.348098854Z ++ chmod 644 /etc/logrotate.d/nginx-proxy-manager
2023-05-04T09:18:44.383273751Z + . /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh
2023-05-04T09:18:44.386861108Z ++ set -e
2023-05-04T09:18:44.386970192Z ++ log_info 'Setting ownership ...'
2023-05-04T09:18:44.386998693Z ++ echo -e '\E[1;34m? \E[1;36mSetting ownership ...\E[0m'
2023-05-04T09:18:44.387019901Z ++ chown root /tmp/nginx
2023-05-04T09:18:44.386967026Z ? Setting ownership ...
2023-05-04T09:18:44.390388048Z ++ chown -R 0:0 /data
2023-05-04T09:18:44.403340050Z ++ chown -R 0:0 /etc/letsencrypt
2023-05-04T09:18:44.411539062Z ++ chown -R 0:0 /run/nginx
2023-05-04T09:18:44.415157461Z ++ chown -R 0:0 /tmp/nginx
2023-05-04T09:18:44.419180154Z ++ chown -R 0:0 /var/cache/nginx
2023-05-04T09:18:44.422785636Z ++ chown -R 0:0 /var/lib/logrotate
2023-05-04T09:18:44.429816140Z ++ chown -R 0:0 /var/lib/nginx
2023-05-04T09:18:44.434390420Z ++ chown -R 0:0 /var/log/nginx
2023-05-04T09:18:44.439064701Z ++ chown -R 0:0 /etc/nginx/nginx
2023-05-04T09:18:44.476191487Z ++ chown -R 0:0 /etc/nginx/nginx.conf
2023-05-04T09:18:44.493216098Z ++ chown -R 0:0 /etc/nginx/conf.d
2023-05-04T09:18:44.579592332Z + . /etc/s6-overlay/s6-rc.d/prepare/40-dynamic.sh
2023-05-04T09:18:44.580560797Z ++ set -e
2023-05-04T09:18:44.580622631Z ++ log_info 'Dynamic resolvers ...'
2023-05-04T09:18:44.580667923Z ++ echo -e '\E[1;34m? \E[1;36mDynamic resolvers ...\E[0m'
2023-05-04T09:18:44.580709048Z ? Dynamic resolvers ...
2023-05-04T09:18:44.582670186Z +++ echo ''
2023-05-04T09:18:44.582922438Z +++ tr '[:upper:]' '[:lower:]'
2023-05-04T09:18:44.590861823Z ++ DISABLE_IPV6=
2023-05-04T09:18:44.591395368Z ++ '[' '' == true ']'
2023-05-04T09:18:44.592414000Z ++ '[' '' == on ']'
2023-05-04T09:18:44.592586793Z ++ '[' '' == 1 ']'
2023-05-04T09:18:44.592613626Z ++ '[' '' == yes ']'
2023-05-04T09:18:44.594116053Z +++ awk 'BEGIN{ORS=" "} $1=="nameserver" { sub(/%.*$/,"",$2); print ($2 ~ ":")? "["$2"]": $2}' /etc/resolv.conf
2023-05-04T09:18:44.609210819Z ++ echo resolver '127.0.0.11  valid=10s;'
2023-05-04T09:18:44.609934490Z + . /etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh
2023-05-04T09:18:44.610554119Z ++ set -e
2023-05-04T09:18:44.610840829Z ++ log_info 'IPv6 ...'
2023-05-04T09:18:44.610965913Z ? IPv6 ...
2023-05-04T09:18:44.611004539Z ++ echo -e '\E[1;34m? \E[1;36mIPv6 ...\E[0m'
2023-05-04T09:18:44.617077245Z +++ echo ''
2023-05-04T09:18:44.617183788Z +++ tr '[:upper:]' '[:lower:]'
2023-05-04T09:18:44.619167509Z ++ DISABLE_IPV6=
2023-05-04T09:18:44.619615095Z ++ process_folder /etc/nginx/conf.d
2023-05-04T09:18:44.620763019Z +++ find /etc/nginx/conf.d -type f -name '*.conf'
2023-05-04T09:18:44.640286773Z ++ FILES='/etc/nginx/conf.d/include/proxy.conf
2023-05-04T09:18:44.640392857Z /etc/nginx/conf.d/include/block-exploits.conf
2023-05-04T09:18:44.640414065Z /etc/nginx/conf.d/include/ip_ranges.conf
2023-05-04T09:18:44.640428565Z /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
2023-05-04T09:18:44.640442440Z /etc/nginx/conf.d/include/force-ssl.conf
2023-05-04T09:18:44.640455315Z /etc/nginx/conf.d/include/assets.conf
2023-05-04T09:18:44.640468399Z /etc/nginx/conf.d/include/ssl-ciphers.conf
2023-05-04T09:18:44.640482024Z /etc/nginx/conf.d/include/resolvers.conf
2023-05-04T09:18:44.640495649Z /etc/nginx/conf.d/default.conf
2023-05-04T09:18:44.640508316Z /etc/nginx/conf.d/production.conf'
2023-05-04T09:18:44.640521024Z ++ SED_REGEX=
2023-05-04T09:18:44.640533858Z ++ '[' '' == true ']'
2023-05-04T09:18:44.640562149Z ++ '[' '' == on ']'
2023-05-04T09:18:44.640574899Z ++ '[' '' == 1 ']'
2023-05-04T09:18:44.640662650Z Enabling IPV6 in hosts in: /etc/nginx/conf.d
2023-05-04T09:18:44.640695192Z - /etc/nginx/conf.d/include/proxy.conf
2023-05-04T09:18:44.640676567Z ++ '[' '' == yes ']'
2023-05-04T09:18:44.640721650Z ++ echo 'Enabling IPV6 in hosts in: /etc/nginx/conf.d'
2023-05-04T09:18:44.640735151Z ++ SED_REGEX='s/^(\s*)#listen \[::\]/\1listen [::]/g'
2023-05-04T09:18:44.640748817Z ++ for FILE in $FILES
2023-05-04T09:18:44.640761192Z ++ echo '- /etc/nginx/conf.d/include/proxy.conf'
2023-05-04T09:18:44.640773817Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/proxy.conf
2023-05-04T09:18:44.656118627Z ++ for FILE in $FILES
2023-05-04T09:18:44.656224002Z ++ echo '- /etc/nginx/conf.d/include/block-exploits.conf'
2023-05-04T09:18:44.656242169Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/block-exploits.conf
2023-05-04T09:18:44.656386503Z - /etc/nginx/conf.d/include/block-exploits.conf
2023-05-04T09:18:44.661982748Z ++ for FILE in $FILES
2023-05-04T09:18:44.662095916Z ++ echo '- /etc/nginx/conf.d/include/ip_ranges.conf'
2023-05-04T09:18:44.662111833Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/ip_ranges.conf
2023-05-04T09:18:44.662014874Z - /etc/nginx/conf.d/include/ip_ranges.conf
2023-05-04T09:18:44.667502410Z ++ for FILE in $FILES
2023-05-04T09:18:44.667618119Z ++ echo '- /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf'
2023-05-04T09:18:44.667634285Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
2023-05-04T09:18:44.667593577Z - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
2023-05-04T09:18:44.672393650Z ++ for FILE in $FILES
2023-05-04T09:18:44.672497859Z ++ echo '- /etc/nginx/conf.d/include/force-ssl.conf'
2023-05-04T09:18:44.672513484Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/force-ssl.conf
2023-05-04T09:18:44.672424067Z - /etc/nginx/conf.d/include/force-ssl.conf
2023-05-04T09:18:44.677290474Z ++ for FILE in $FILES
2023-05-04T09:18:44.677397641Z ++ echo '- /etc/nginx/conf.d/include/assets.conf'
2023-05-04T09:18:44.677412600Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/assets.conf
2023-05-04T09:18:44.677459600Z - /etc/nginx/conf.d/include/assets.conf
2023-05-04T09:18:44.682245173Z ++ for FILE in $FILES
2023-05-04T09:18:44.682332215Z ++ echo '- /etc/nginx/conf.d/include/ssl-ciphers.conf'
2023-05-04T09:18:44.682348007Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/ssl-ciphers.conf
2023-05-04T09:18:44.682391799Z - /etc/nginx/conf.d/include/ssl-ciphers.conf
2023-05-04T09:18:44.687282123Z ++ for FILE in $FILES
2023-05-04T09:18:44.687411957Z ++ echo '- /etc/nginx/conf.d/include/resolvers.conf'
2023-05-04T09:18:44.687428207Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/resolvers.conf
2023-05-04T09:18:44.687339123Z - /etc/nginx/conf.d/include/resolvers.conf
2023-05-04T09:18:44.692216405Z ++ for FILE in $FILES
2023-05-04T09:18:44.692320989Z ++ echo '- /etc/nginx/conf.d/default.conf'
2023-05-04T09:18:44.692336864Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/default.conf
2023-05-04T09:18:44.692244947Z - /etc/nginx/conf.d/default.conf
2023-05-04T09:18:44.697193146Z ++ for FILE in $FILES
2023-05-04T09:18:44.697313105Z ++ echo '- /etc/nginx/conf.d/production.conf'
2023-05-04T09:18:44.697328606Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/production.conf
2023-05-04T09:18:44.697203480Z - /etc/nginx/conf.d/production.conf
2023-05-04T09:18:44.702298888Z ++ chown -R 0:0 /etc/nginx/conf.d
2023-05-04T09:18:44.706252456Z ++ process_folder /data/nginx
2023-05-04T09:18:44.707230254Z +++ find /data/nginx -type f -name '*.conf'
2023-05-04T09:18:44.711650075Z ++ FILES='/data/nginx/proxy_host/7.conf
2023-05-04T09:18:44.711747117Z /data/nginx/proxy_host/14.conf
2023-05-04T09:18:44.711797076Z /data/nginx/proxy_host/4.conf
2023-05-04T09:18:44.711813034Z /data/nginx/proxy_host/6.conf
2023-05-04T09:18:44.711826451Z /data/nginx/proxy_host/21.conf
2023-05-04T09:18:44.711839492Z /data/nginx/proxy_host/20.conf
2023-05-04T09:18:44.711852451Z /data/nginx/proxy_host/1.conf
2023-05-04T09:18:44.711865243Z /data/nginx/proxy_host/19.conf
2023-05-04T09:18:44.711877993Z /data/nginx/proxy_host/3.conf
2023-05-04T09:18:44.711890576Z /data/nginx/proxy_host/15.conf
2023-05-04T09:18:44.711904576Z /data/nginx/proxy_host/5.conf
2023-05-04T09:18:44.711917493Z /data/nginx/proxy_host/12.conf
2023-05-04T09:18:44.711930368Z /data/nginx/proxy_host/9.conf
2023-05-04T09:18:44.711943326Z /data/nginx/proxy_host/2.conf
2023-05-04T09:18:44.711956243Z /data/nginx/proxy_host/8.conf
2023-05-04T09:18:44.711968952Z /data/nginx/proxy_host/24.conf
2023-05-04T09:18:44.711989993Z /data/nginx/proxy_host/11.conf
2023-05-04T09:18:44.712005244Z /data/nginx/proxy_host/13.conf
2023-05-04T09:18:44.712018244Z /data/nginx/proxy_host/16.conf
2023-05-04T09:18:44.712030785Z /data/nginx/proxy_host/22.conf
2023-05-04T09:18:44.712043535Z /data/nginx/proxy_host/23.conf
2023-05-04T09:18:44.712057369Z /data/nginx/proxy_host/18.conf
2023-05-04T09:18:44.712071619Z /data/nginx/proxy_host/10.conf
2023-05-04T09:18:44.712084536Z /data/nginx/proxy_host/17.conf'
2023-05-04T09:18:44.712096952Z ++ SED_REGEX=
2023-05-04T09:18:44.712109786Z ++ '[' '' == true ']'
2023-05-04T09:18:44.712123119Z ++ '[' '' == on ']'
2023-05-04T09:18:44.712152328Z ++ '[' '' == 1 ']'
2023-05-04T09:18:44.712166620Z ++ '[' '' == yes ']'
2023-05-04T09:18:44.712179411Z ++ echo 'Enabling IPV6 in hosts in: /data/nginx'
2023-05-04T09:18:44.712194370Z ++ SED_REGEX='s/^(\s*)#listen \[::\]/\1listen [::]/g'
2023-05-04T09:18:44.712212620Z ++ for FILE in $FILES
2023-05-04T09:18:44.712227037Z ++ echo '- /data/nginx/proxy_host/7.conf'
2023-05-04T09:18:44.712240037Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/7.conf
2023-05-04T09:18:44.711749992Z Enabling IPV6 in hosts in: /data/nginx
2023-05-04T09:18:44.712269495Z - /data/nginx/proxy_host/7.conf
2023-05-04T09:18:44.717462113Z ++ for FILE in $FILES
2023-05-04T09:18:44.717637156Z ++ echo '- /data/nginx/proxy_host/14.conf'
2023-05-04T09:18:44.717655947Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/14.conf
2023-05-04T09:18:44.717560447Z - /data/nginx/proxy_host/14.conf
2023-05-04T09:18:44.722855606Z - /data/nginx/proxy_host/4.conf
2023-05-04T09:18:44.722836648Z ++ for FILE in $FILES
2023-05-04T09:18:44.723579236Z ++ echo '- /data/nginx/proxy_host/4.conf'
2023-05-04T09:18:44.723620070Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/4.conf
2023-05-04T09:18:44.728364559Z - /data/nginx/proxy_host/6.conf
2023-05-04T09:18:44.728346976Z ++ for FILE in $FILES
2023-05-04T09:18:44.728488227Z ++ echo '- /data/nginx/proxy_host/6.conf'
2023-05-04T09:18:44.728503602Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/6.conf
2023-05-04T09:18:44.733728386Z ++ for FILE in $FILES
2023-05-04T09:18:44.733858720Z ++ echo '- /data/nginx/proxy_host/21.conf'
2023-05-04T09:18:44.733874845Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/21.conf
2023-05-04T09:18:44.733785720Z - /data/nginx/proxy_host/21.conf
2023-05-04T09:18:44.739061338Z ++ for FILE in $FILES
2023-05-04T09:18:44.739187964Z ++ echo '- /data/nginx/proxy_host/20.conf'
2023-05-04T09:18:44.739101171Z - /data/nginx/proxy_host/20.conf
2023-05-04T09:18:44.739204755Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/20.conf
2023-05-04T09:18:44.744364873Z ++ for FILE in $FILES
2023-05-04T09:18:44.744485790Z ++ echo '- /data/nginx/proxy_host/1.conf'
2023-05-04T09:18:44.744501540Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/1.conf
2023-05-04T09:18:44.744392415Z - /data/nginx/proxy_host/1.conf
2023-05-04T09:18:44.749695241Z ++ for FILE in $FILES
2023-05-04T09:18:44.749821950Z ++ echo '- /data/nginx/proxy_host/19.conf'
2023-05-04T09:18:44.749837825Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/19.conf
2023-05-04T09:18:44.749733033Z - /data/nginx/proxy_host/19.conf
2023-05-04T09:18:44.754982942Z - /data/nginx/proxy_host/3.conf
2023-05-04T09:18:44.754969151Z ++ for FILE in $FILES
2023-05-04T09:18:44.755111110Z ++ echo '- /data/nginx/proxy_host/3.conf'
2023-05-04T09:18:44.755126027Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/3.conf
2023-05-04T09:18:44.760356269Z ++ for FILE in $FILES
2023-05-04T09:18:44.760478479Z ++ echo '- /data/nginx/proxy_host/15.conf'
2023-05-04T09:18:44.760397020Z - /data/nginx/proxy_host/15.conf
2023-05-04T09:18:44.760495104Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/15.conf
2023-05-04T09:18:44.765730430Z ++ for FILE in $FILES
2023-05-04T09:18:44.765847347Z ++ echo '- /data/nginx/proxy_host/5.conf'
2023-05-04T09:18:44.765765472Z - /data/nginx/proxy_host/5.conf
2023-05-04T09:18:44.765864264Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/5.conf
2023-05-04T09:18:44.771013589Z ++ for FILE in $FILES
2023-05-04T09:18:44.771136549Z ++ echo '- /data/nginx/proxy_host/12.conf'
2023-05-04T09:18:44.771152549Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/12.conf
2023-05-04T09:18:44.771037173Z - /data/nginx/proxy_host/12.conf
2023-05-04T09:18:44.776358166Z - /data/nginx/proxy_host/9.conf
2023-05-04T09:18:44.776343291Z ++ for FILE in $FILES
2023-05-04T09:18:44.776482792Z ++ echo '- /data/nginx/proxy_host/9.conf'
2023-05-04T09:18:44.776497625Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/9.conf
2023-05-04T09:18:44.781892036Z ++ for FILE in $FILES
2023-05-04T09:18:44.782015495Z ++ echo '- /data/nginx/proxy_host/2.conf'
2023-05-04T09:18:44.782032620Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/2.conf
2023-05-04T09:18:44.781917536Z - /data/nginx/proxy_host/2.conf
2023-05-04T09:18:44.787236946Z ++ for FILE in $FILES
2023-05-04T09:18:44.787366363Z ++ echo '- /data/nginx/proxy_host/8.conf'
2023-05-04T09:18:44.787382655Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/8.conf
2023-05-04T09:18:44.787303613Z - /data/nginx/proxy_host/8.conf
2023-05-04T09:18:44.792614940Z ++ for FILE in $FILES
2023-05-04T09:18:44.792745024Z ++ echo '- /data/nginx/proxy_host/24.conf'
2023-05-04T09:18:44.792760899Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/24.conf
2023-05-04T09:18:44.792659023Z - /data/nginx/proxy_host/24.conf
2023-05-04T09:18:44.797916974Z ++ for FILE in $FILES
2023-05-04T09:18:44.798042475Z ++ echo '- /data/nginx/proxy_host/11.conf'
2023-05-04T09:18:44.797949308Z - /data/nginx/proxy_host/11.conf
2023-05-04T09:18:44.798058309Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/11.conf
2023-05-04T09:18:44.803225384Z ++ for FILE in $FILES
2023-05-04T09:18:44.803342718Z ++ echo '- /data/nginx/proxy_host/13.conf'
2023-05-04T09:18:44.803271801Z - /data/nginx/proxy_host/13.conf
2023-05-04T09:18:44.803358760Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/13.conf
2023-05-04T09:18:44.808602336Z ++ for FILE in $FILES
2023-05-04T09:18:44.808731712Z ++ echo '- /data/nginx/proxy_host/16.conf'
2023-05-04T09:18:44.808749212Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/16.conf
2023-05-04T09:18:44.808688837Z - /data/nginx/proxy_host/16.conf
2023-05-04T09:18:44.814946503Z ++ for FILE in $FILES
2023-05-04T09:18:44.815069129Z ++ echo '- /data/nginx/proxy_host/22.conf'
2023-05-04T09:18:44.815084879Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/22.conf
2023-05-04T09:18:44.815028628Z - /data/nginx/proxy_host/22.conf
2023-05-04T09:18:44.823607726Z - /data/nginx/proxy_host/23.conf
2023-05-04T09:18:44.823817853Z ++ for FILE in $FILES
2023-05-04T09:18:44.823865103Z ++ echo '- /data/nginx/proxy_host/23.conf'
2023-05-04T09:18:44.823880478Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/23.conf
2023-05-04T09:18:44.833135872Z ++ for FILE in $FILES
2023-05-04T09:18:44.833266790Z ++ echo '- /data/nginx/proxy_host/18.conf'
2023-05-04T09:18:44.833284540Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/18.conf
2023-05-04T09:18:44.833063080Z - /data/nginx/proxy_host/18.conf
2023-05-04T09:18:44.845528579Z ++ for FILE in $FILES
2023-05-04T09:18:44.845660288Z ++ echo '- /data/nginx/proxy_host/10.conf'
2023-05-04T09:18:44.845676663Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/10.conf
2023-05-04T09:18:44.849002893Z - /data/nginx/proxy_host/10.conf
2023-05-04T09:18:44.856971737Z - /data/nginx/proxy_host/17.conf
2023-05-04T09:18:44.857151072Z ++ for FILE in $FILES
2023-05-04T09:18:44.857186947Z ++ echo '- /data/nginx/proxy_host/17.conf'
2023-05-04T09:18:44.857201697Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/17.conf
2023-05-04T09:18:44.861064764Z ++ chown -R 0:0 /data/nginx
2023-05-04T09:18:44.866426049Z + . /etc/s6-overlay/s6-rc.d/prepare/60-secrets.sh
2023-05-04T09:18:44.870998121Z ++ set -e
2023-05-04T09:18:44.871154164Z ++ log_info 'Docker secrets ...'
2023-05-04T09:18:44.871173580Z ++ echo -e '\E[1;34m? \E[1;36mDocker secrets ...\E[0m'
2023-05-04T09:18:44.870998163Z ? Docker secrets ...
2023-05-04T09:18:44.872723507Z +++ grep '__FILE$'
2023-05-04T09:18:44.872881633Z +++ find /var/run/s6/container_environment/
2023-05-04T09:18:44.893121141Z + . /etc/s6-overlay/s6-rc.d/prepare/90-banner.sh
2023-05-04T09:18:44.893267392Z ++ set -e
2023-05-04T09:18:44.893291434Z ++ set +x
2023-05-04T09:18:44.913142939Z 
2023-05-04T09:18:44.913268524Z -------------------------------------
2023-05-04T09:18:44.913287565Z  _   _ ____  __  __
2023-05-04T09:18:44.913301774Z | \ | |  _ \|  \/  |
2023-05-04T09:18:44.913315107Z |  \| | |_) | |\/| |
2023-05-04T09:18:44.913328107Z | |\  |  __/| |  | |
2023-05-04T09:18:44.913401566Z |_| \_|_|   |_|  |_|
2023-05-04T09:18:44.913415983Z -------------------------------------
2023-05-04T09:18:44.913431441Z User:  npm PUID:0 ID:0 GROUP:0
2023-05-04T09:18:44.913444858Z Group: npm PGID:0 ID:0
2023-05-04T09:18:44.913458025Z -------------------------------------
2023-05-04T09:18:44.913523900Z 
2023-05-04T09:18:44.918379307Z s6-rc: info: service prepare successfully started
2023-05-04T09:18:44.918501475Z s6-rc: info: service nginx: starting
2023-05-04T09:18:44.919560482Z s6-rc: info: service frontend: starting
2023-05-04T09:18:44.921502411Z s6-rc: info: service backend: starting
2023-05-04T09:18:44.929904591Z s6-rc: info: service nginx successfully started
2023-05-04T09:18:44.935372919Z s6-rc: info: service frontend successfully started
2023-05-04T09:18:44.937059096Z s6-rc: info: service backend successfully started
2023-05-04T09:18:44.945248025Z ? Starting nginx ...
2023-05-04T09:18:44.947579957Z s6-rc: info: service legacy-services: starting
2023-05-04T09:18:44.958180110Z ? Starting backend ...
2023-05-04T09:18:44.985879834Z s6-rc: info: service legacy-services successfully started
2023-05-04T09:18:46.687912386Z [5/4/2023] [9:18:46 AM] [Global   ] › ?  info      Using Sqlite: /data/database.sqlite
2023-05-04T09:18:46.690759030Z [5/4/2023] [9:18:46 AM] [Global   ] › ?  info      Keys file exists OK
2023-05-04T09:18:52.444943108Z [5/4/2023] [9:18:52 AM] [Migrate  ] › ?  info      Current database version: none
2023-05-04T09:18:52.544247177Z [5/4/2023] [9:18:52 AM] [Setup    ] › ?  info      Admin user setup not required
2023-05-04T09:18:52.553080110Z [5/4/2023] [9:18:52 AM] [Setup    ] › ?  info      Default setting setup not required
2023-05-04T09:18:52.562787841Z [5/4/2023] [9:18:52 AM] [Setup    ] › ?  info      Logrotate Timer initialized
2023-05-04T09:18:52.647828899Z [5/4/2023] [9:18:52 AM] [Setup    ] › ?  warning   Error: Command failed: logrotate /etc/logrotate.d/nginx-proxy-manager 
2023-05-04T09:18:52.647958275Z 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.
2023-05-04T09:18:52.647986567Z 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.
2023-05-04T09:18:52.648003525Z 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.
2023-05-04T09:18:52.648019609Z 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.
2023-05-04T09:18:52.648099442Z 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.
2023-05-04T09:18:52.648117443Z 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.
2023-05-04T09:18:52.648132818Z 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.
2023-05-04T09:18:52.648155443Z 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.
2023-05-04T09:18:52.648171526Z error: skipping "/data/logs/proxy-host-17_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.
2023-05-04T09:18:52.648187443Z error: skipping "/data/logs/proxy-host-18_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.
2023-05-04T09:18:52.648202693Z error: skipping "/data/logs/proxy-host-19_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.
2023-05-04T09:18:52.648217818Z 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.
2023-05-04T09:18:52.648233027Z error: skipping "/data/logs/proxy-host-20_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.
2023-05-04T09:18:52.648248235Z error: skipping "/data/logs/proxy-host-21_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.
2023-05-04T09:18:52.648263569Z error: skipping "/data/logs/proxy-host-22_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.
2023-05-04T09:18:52.648281694Z error: skipping "/data/logs/proxy-host-23_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.
2023-05-04T09:18:52.648321944Z error: skipping "/data/logs/proxy-host-24_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.
2023-05-04T09:18:52.648340277Z 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.
2023-05-04T09:18:52.648356236Z 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.
2023-05-04T09:18:52.648371528Z 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.
2023-05-04T09:18:52.648386653Z 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.
2023-05-04T09:18:52.648401986Z 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.
2023-05-04T09:18:52.648421236Z 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.
2023-05-04T09:18:52.648436986Z 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.
2023-05-04T09:18:52.648452236Z 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.
2023-05-04T09:18:52.648467653Z 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.
2023-05-04T09:18:52.648482862Z 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.
2023-05-04T09:18:52.648512153Z 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.
2023-05-04T09:18:52.648552362Z 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.
2023-05-04T09:18:52.648569779Z 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.
2023-05-04T09:18:52.648588446Z 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.
2023-05-04T09:18:52.648603987Z 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.
2023-05-04T09:18:52.648619404Z 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.
2023-05-04T09:18:52.648634821Z error: skipping "/data/logs/proxy-host-17_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.
2023-05-04T09:18:52.648650154Z error: skipping "/data/logs/proxy-host-18_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.
2023-05-04T09:18:52.648665696Z error: skipping "/data/logs/proxy-host-19_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.
2023-05-04T09:18:52.648680905Z 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.
2023-05-04T09:18:52.648695946Z error: skipping "/data/logs/proxy-host-20_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.
2023-05-04T09:18:52.648713821Z error: skipping "/data/logs/proxy-host-21_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.
2023-05-04T09:18:52.648729572Z error: skipping "/data/logs/proxy-host-22_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.
2023-05-04T09:18:52.648763822Z error: skipping "/data/logs/proxy-host-23_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.
2023-05-04T09:18:52.648780239Z error: skipping "/data/logs/proxy-host-24_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.
2023-05-04T09:18:52.648795489Z 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.
2023-05-04T09:18:52.648811155Z 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.
2023-05-04T09:18:52.648922698Z 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.
2023-05-04T09:18:52.648952698Z 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.
2023-05-04T09:18:52.648975073Z 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.
2023-05-04T09:18:52.648990532Z 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.
2023-05-04T09:18:52.649005740Z 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.
2023-05-04T09:18:52.649021532Z 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.
2023-05-04T09:18:52.649036782Z 
2023-05-04T09:18:52.649049615Z     at ChildProcess.exithandler (node:child_process:402:12)
2023-05-04T09:18:52.649062490Z     at ChildProcess.emit (node:events:513:28)
2023-05-04T09:18:52.649075491Z     at maybeClose (node:internal/child_process:1100:16)
2023-05-04T09:18:52.649088324Z     at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
2023-05-04T09:18:52.650686418Z [5/4/2023] [9:18:52 AM] [IP Ranges] › ?  info      Fetching IP Ranges from online services...
2023-05-04T09:18:52.652804182Z [5/4/2023] [9:18:52 AM] [IP Ranges] › ?  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
2023-05-04T09:18:52.982130219Z [5/4/2023] [9:18:52 AM] [IP Ranges] › ?  info      Fetching https://www.cloudflare.com/ips-v4
2023-05-04T09:18:53.071691057Z [5/4/2023] [9:18:53 AM] [IP Ranges] › ?  info      Fetching https://www.cloudflare.com/ips-v6
2023-05-04T09:18:53.211451642Z [5/4/2023] [9:18:53 AM] [SSL      ] › ?  info      Let's Encrypt Renewal Timer initialized
2023-05-04T09:18:53.213168028Z [5/4/2023] [9:18:53 AM] [SSL      ] › ?  info      Renewing SSL certs close to expiry...
2023-05-04T09:18:53.237430021Z [5/4/2023] [9:18:53 AM] [IP Ranges] › ?  info      IP Ranges Renewal Timer initialized
2023-05-04T09:18:53.251137694Z [5/4/2023] [9:18:53 AM] [Global   ] › ?  info      Backend PID 184 listening on port 3000 ...
2023-05-04T09:18:56.343420626Z [5/4/2023] [9:18:56 AM] [Nginx    ] › ?  info      Testing Nginx configuration
2023-05-04T09:18:56.871849679Z [5/4/2023] [9:18:56 AM] [Nginx    ] › ?  info      Reloading Nginx
2023-05-04T09:18:57.322415555Z [5/4/2023] [9:18:57 AM] [SSL      ] › ?  info      Renew Complete
2023-05-04T09:19:06.114704085Z [5/4/2023] [9:19:06 AM] [Express  ] › ?  debug     AuthError: Token has expired
2023-05-04T09:19:06.114874502Z     at /app/models/token.js:69:17
2023-05-04T09:19:06.114915628Z     at /app/node_modules/jsonwebtoken/verify.js:190:16
2023-05-04T09:19:06.114950878Z     at getSecret (/app/node_modules/jsonwebtoken/verify.js:97:14)
2023-05-04T09:19:06.114986128Z     at Object.module.exports [as verify] (/app/node_modules/jsonwebtoken/verify.js:101:10)
2023-05-04T09:19:06.115020253Z     at /app/models/token.js:65:11
2023-05-04T09:19:06.115053420Z     at new Promise (<anonymous>)
2023-05-04T09:19:06.115086837Z     at Object.load (/app/models/token.js:60:11)
2023-05-04T09:19:06.115120546Z     at /app/lib/access.js:228:20
2023-05-04T09:19:06.115153088Z     at new Promise (<anonymous>)
2023-05-04T09:19:06.115186088Z     at Object.load (/app/lib/access.js:226:11)

Then after REBOOT it did NOT start:

2023-05-04T09:20:32.540715094Z s6-rc: info: service legacy-services: stopping
2023-05-04T09:20:33.165367905Z s6-rc: info: service legacy-services successfully stopped
2023-05-04T09:20:33.218268335Z s6-rc: info: service nginx: stopping
2023-05-04T09:20:33.218690547Z s6-rc: info: service frontend: stopping
2023-05-04T09:20:33.219106424Z s6-rc: info: service backend: stopping
2023-05-04T09:20:33.265034893Z s6-rc: info: service frontend successfully stopped
2023-05-04T09:20:33.459589045Z s6-rc: info: service backend successfully stopped
2023-05-04T09:20:33.545357817Z s6-rc: info: service nginx successfully stopped
2023-05-04T09:20:33.545981613Z s6-rc: info: service prepare: stopping
2023-05-04T09:20:33.550438558Z s6-rc: info: service prepare successfully stopped
2023-05-04T09:20:33.551028312Z s6-rc: info: service legacy-cont-init: stopping
2023-05-04T09:20:33.692782368Z s6-rc: info: service legacy-cont-init successfully stopped
2023-05-04T09:20:33.693559165Z s6-rc: info: service fix-attrs: stopping
2023-05-04T09:20:34.377044528Z s6-rc: info: service fix-attrs successfully stopped
2023-05-04T09:20:34.377789992Z s6-rc: info: service s6rc-oneshot-runner: stopping
2023-05-04T09:20:34.563192126Z s6-rc: info: service s6rc-oneshot-runner successfully stopped
2023-05-04T09:20:34.567081401Z [5/4/2023] [9:20:34 AM] [Global   ] › ?  info      PID 184 received SIGTERM
2023-05-04T09:20:34.569679418Z [5/4/2023] [9:20:34 AM] [Global   ] › ?  info      Stopping.
2023-05-04T09:21:56.207510623Z s6-rc: info: service s6rc-oneshot-runner: starting
2023-05-04T09:21:56.716293447Z s6-rc: info: service s6rc-oneshot-runner successfully started
2023-05-04T09:21:56.737622553Z s6-rc: info: service fix-attrs: starting
2023-05-04T09:21:57.109247925Z s6-rc: info: service fix-attrs successfully started
2023-05-04T09:21:57.110361974Z s6-rc: info: service legacy-cont-init: starting
2023-05-04T09:21:57.183778651Z s6-rc: info: service legacy-cont-init successfully started
2023-05-04T09:21:57.184391572Z s6-rc: info: service prepare: starting
2023-05-04T09:21:59.667940480Z + . /etc/s6-overlay/s6-rc.d/prepare/10-usergroup.sh
2023-05-04T09:21:59.671168627Z ? Configuring npm user ...
2023-05-04T09:21:59.671578589Z ++ set -e
2023-05-04T09:21:59.672025300Z ++ log_info 'Configuring npm user ...'
2023-05-04T09:21:59.672074717Z ++ echo -e '\E[1;34m? \E[1;36mConfiguring npm user ...\E[0m'
2023-05-04T09:21:59.672091759Z ++ id -u npm
2023-05-04T09:21:59.677841674Z 0
2023-05-04T09:21:59.697822604Z ++ usermod -u 0 npm
2023-05-04T09:22:00.500955638Z usermod: no changes
2023-05-04T09:22:00.508150313Z ++ log_info 'Configuring npm group ...'
2023-05-04T09:22:00.508265897Z ++ echo -e '\E[1;34m? \E[1;36mConfiguring npm group ...\E[0m'
2023-05-04T09:22:00.508321814Z ? Configuring npm group ...
2023-05-04T09:22:00.508742525Z +++ get_group_id npm
2023-05-04T09:22:00.508830359Z +++ '[' npm '!=' '' ']'
2023-05-04T09:22:00.508848110Z +++ getent group npm
2023-05-04T09:22:00.508862110Z +++ cut -d: -f3
2023-05-04T09:22:00.554559969Z ++ '[' 0 = '' ']'
2023-05-04T09:22:00.555678268Z ++ groupmod -o -g 0 npm
2023-05-04T09:22:01.187650739Z s6-sudoc: fatal: unable to get exit status from server: Operation timed out
2023-05-04T09:22:01.187873740Z s6-rc: warning: unable to start service prepare: command exited 111
2023-05-04T09:22:01.301473237Z /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

Then after container RESTART it started:

2023-05-04T09:23:25.660699419Z s6-rc: info: service legacy-cont-init: stopping
2023-05-04T09:23:25.700683771Z s6-rc: info: service legacy-cont-init successfully stopped
2023-05-04T09:23:25.701204815Z s6-rc: info: service fix-attrs: stopping
2023-05-04T09:23:25.704959920Z s6-rc: info: service fix-attrs successfully stopped
2023-05-04T09:23:25.709526196Z s6-rc: info: service s6rc-oneshot-runner: stopping
2023-05-04T09:23:25.728874555Z s6-rc: info: service s6rc-oneshot-runner successfully stopped
2023-05-04T09:23:36.091033687Z s6-rc: info: service s6rc-oneshot-runner: starting
2023-05-04T09:23:36.109674349Z s6-rc: info: service s6rc-oneshot-runner successfully started
2023-05-04T09:23:36.114230872Z s6-rc: info: service fix-attrs: starting
2023-05-04T09:23:36.154542350Z s6-rc: info: service fix-attrs successfully started
2023-05-04T09:23:36.154970712Z s6-rc: info: service legacy-cont-init: starting
2023-05-04T09:23:36.165998322Z s6-rc: info: service legacy-cont-init successfully started
2023-05-04T09:23:36.166455808Z s6-rc: info: service prepare: starting
2023-05-04T09:23:36.287089253Z + . /etc/s6-overlay/s6-rc.d/prepare/10-usergroup.sh
2023-05-04T09:23:36.287972141Z ++ set -e
2023-05-04T09:23:36.288277965Z ++ log_info 'Configuring npm user ...'
2023-05-04T09:23:36.288681952Z ++ echo -e '\E[1;34m? \E[1;36mConfiguring npm user ...\E[0m'
2023-05-04T09:23:36.289032025Z ? Configuring npm user ...
2023-05-04T09:23:36.289695462Z ++ id -u npm
2023-05-04T09:23:36.294575808Z 0
2023-05-04T09:23:36.295420990Z ++ usermod -u 0 npm
2023-05-04T09:23:36.346806369Z usermod: no changes
2023-05-04T09:23:36.351603093Z ++ log_info 'Configuring npm group ...'
2023-05-04T09:23:36.351713172Z ++ echo -e '\E[1;34m? \E[1;36mConfiguring npm group ...\E[0m'
2023-05-04T09:23:36.351631633Z ? Configuring npm group ...
2023-05-04T09:23:36.352787972Z +++ get_group_id npm
2023-05-04T09:23:36.352896968Z +++ '[' npm '!=' '' ']'
2023-05-04T09:23:36.353864605Z +++ getent group npm
2023-05-04T09:23:36.354410171Z +++ cut -d: -f3
2023-05-04T09:23:36.361565112Z ++ '[' 0 = '' ']'
2023-05-04T09:23:36.361665442Z ++ groupmod -o -g 0 npm
2023-05-04T09:23:36.417607052Z ++ groupmod -o -g 0 npm
2023-05-04T09:23:36.451418611Z +++ get_group_id npm
2023-05-04T09:23:36.451573523Z +++ '[' npm '!=' '' ']'
2023-05-04T09:23:36.452542742Z +++ getent group npm
2023-05-04T09:23:36.453008602Z +++ cut -d: -f3
2023-05-04T09:23:36.456959269Z ++ '[' 0 '!=' 0 ']'
2023-05-04T09:23:36.457075266Z ++ usermod -G 0 npm
2023-05-04T09:23:36.469918736Z +++ id -g npm
2023-05-04T09:23:36.473382210Z ++ '[' 0 '!=' 0 ']'
2023-05-04T09:23:36.473556371Z ++ mkdir -p /tmp/npmuserhome
2023-05-04T09:23:36.590013697Z ++ chown -R 0:0 /tmp/npmuserhome
2023-05-04T09:23:36.598929249Z + . /etc/s6-overlay/s6-rc.d/prepare/20-paths.sh
2023-05-04T09:23:36.600311581Z ++ set -e
2023-05-04T09:23:36.600380829Z ++ log_info 'Checking paths ...'
2023-05-04T09:23:36.600454951Z ++ echo -e '\E[1;34m? \E[1;36mChecking paths ...\E[0m'
2023-05-04T09:23:36.600449785Z ? Checking paths ...
2023-05-04T09:23:36.600536282Z ++ '[' '!' -d /data ']'
2023-05-04T09:23:36.600682277Z ++ '[' '!' -d /etc/letsencrypt ']'
2023-05-04T09:23:36.600996351Z ++ mkdir -p /data/nginx /data/custom_ssl /data/logs /data/access /data/nginx/default_host /data/nginx/default_www /data/nginx/proxy_host /data/nginx/redirection_host /data/nginx/stream /data/nginx/dead_host /data/nginx/temp /data/letsencrypt-acme-challenge /run/nginx /tmp/nginx/body /var/log/nginx /var/lib/nginx/cache/public /var/lib/nginx/cache/private /var/cache/nginx/proxy_temp
2023-05-04T09:23:37.313970361Z ++ touch /var/log/nginx/error.log
2023-05-04T09:23:37.321694284Z ++ chmod 777 /var/log/nginx/error.log
2023-05-04T09:23:37.327929546Z ++ chmod -R 777 /var/cache/nginx
2023-05-04T09:23:37.338697540Z ++ chmod 644 /etc/logrotate.d/nginx-proxy-manager
2023-05-04T09:23:37.342207846Z + . /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh
2023-05-04T09:23:37.343029236Z ++ set -e
2023-05-04T09:23:37.343095984Z ++ log_info 'Setting ownership ...'
2023-05-04T09:23:37.343155107Z ++ echo -e '\E[1;34m? \E[1;36mSetting ownership ...\E[0m'
2023-05-04T09:23:37.343185440Z ? Setting ownership ...
2023-05-04T09:23:37.343239188Z ++ chown root /tmp/nginx
2023-05-04T09:23:37.346831325Z ++ chown -R 0:0 /data
2023-05-04T09:23:37.465105469Z ++ chown -R 0:0 /etc/letsencrypt
2023-05-04T09:23:37.477754070Z ++ chown -R 0:0 /run/nginx
2023-05-04T09:23:37.483434599Z ++ chown -R 0:0 /tmp/nginx
2023-05-04T09:23:37.490266050Z ++ chown -R 0:0 /var/cache/nginx
2023-05-04T09:23:37.494455918Z ++ chown -R 0:0 /var/lib/logrotate
2023-05-04T09:23:37.502879861Z ++ chown -R 0:0 /var/lib/nginx
2023-05-04T09:23:37.507762415Z ++ chown -R 0:0 /var/log/nginx
2023-05-04T09:23:37.511998365Z ++ chown -R 0:0 /etc/nginx/nginx
2023-05-04T09:23:37.531348213Z ++ chown -R 0:0 /etc/nginx/nginx.conf
2023-05-04T09:23:37.534891101Z ++ chown -R 0:0 /etc/nginx/conf.d
2023-05-04T09:23:37.562597810Z + . /etc/s6-overlay/s6-rc.d/prepare/40-dynamic.sh
2023-05-04T09:23:37.567873352Z ++ set -e
2023-05-04T09:23:37.567990557Z ++ log_info 'Dynamic resolvers ...'
2023-05-04T09:23:37.568020014Z ++ echo -e '\E[1;34m? \E[1;36mDynamic resolvers ...\E[0m'
2023-05-04T09:23:37.568018098Z ? Dynamic resolvers ...
2023-05-04T09:23:37.570781261Z +++ echo ''
2023-05-04T09:23:37.570912006Z +++ tr '[:upper:]' '[:lower:]'
2023-05-04T09:23:37.576271879Z ++ DISABLE_IPV6=
2023-05-04T09:23:37.576585702Z ++ '[' '' == true ']'
2023-05-04T09:23:37.576629201Z ++ '[' '' == on ']'
2023-05-04T09:23:37.576644284Z ++ '[' '' == 1 ']'
2023-05-04T09:23:37.576669617Z ++ '[' '' == yes ']'
2023-05-04T09:23:37.577922619Z +++ awk 'BEGIN{ORS=" "} $1=="nameserver" { sub(/%.*$/,"",$2); print ($2 ~ ":")? "["$2"]": $2}' /etc/resolv.conf
2023-05-04T09:23:37.613194714Z ++ echo resolver '127.0.0.11  valid=10s;'
2023-05-04T09:23:37.614047271Z + . /etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh
2023-05-04T09:23:37.616152829Z ++ set -e
2023-05-04T09:23:37.616266451Z ++ log_info 'IPv6 ...'
2023-05-04T09:23:37.616212786Z ? IPv6 ...
2023-05-04T09:23:37.616285159Z ++ echo -e '\E[1;34m? \E[1;36mIPv6 ...\E[0m'
2023-05-04T09:23:37.618249388Z +++ echo ''
2023-05-04T09:23:37.618396967Z +++ tr '[:upper:]' '[:lower:]'
2023-05-04T09:23:37.621813526Z ++ DISABLE_IPV6=
2023-05-04T09:23:37.622385258Z ++ process_folder /etc/nginx/conf.d
2023-05-04T09:23:37.623757965Z +++ find /etc/nginx/conf.d -type f -name '*.conf'
2023-05-04T09:23:37.642610287Z ++ FILES='/etc/nginx/conf.d/include/proxy.conf
2023-05-04T09:23:37.642708200Z /etc/nginx/conf.d/include/block-exploits.conf
2023-05-04T09:23:37.642725575Z /etc/nginx/conf.d/include/ip_ranges.conf
2023-05-04T09:23:37.642740282Z /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
2023-05-04T09:23:37.642753907Z /etc/nginx/conf.d/include/force-ssl.conf
2023-05-04T09:23:37.642766990Z /etc/nginx/conf.d/include/assets.conf
2023-05-04T09:23:37.642779740Z /etc/nginx/conf.d/include/ssl-ciphers.conf
2023-05-04T09:23:37.642792572Z /etc/nginx/conf.d/include/resolvers.conf
2023-05-04T09:23:37.642806864Z /etc/nginx/conf.d/default.conf
2023-05-04T09:23:37.642819488Z /etc/nginx/conf.d/production.conf'
2023-05-04T09:23:37.642832946Z ++ SED_REGEX=
2023-05-04T09:23:37.642848821Z ++ '[' '' == true ']'
2023-05-04T09:23:37.642828446Z Enabling IPV6 in hosts in: /etc/nginx/conf.d
2023-05-04T09:23:37.642862404Z ++ '[' '' == on ']'
2023-05-04T09:23:37.642987816Z ++ '[' '' == 1 ']'
2023-05-04T09:23:37.643007024Z ++ '[' '' == yes ']'
2023-05-04T09:23:37.643021232Z ++ echo 'Enabling IPV6 in hosts in: /etc/nginx/conf.d'
2023-05-04T09:23:37.643034481Z ++ SED_REGEX='s/^(\s*)#listen \[::\]/\1listen [::]/g'
2023-05-04T09:23:37.643226975Z ++ for FILE in $FILES
2023-05-04T09:23:37.643268974Z ++ echo '- /etc/nginx/conf.d/include/proxy.conf'
2023-05-04T09:23:37.643285849Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/proxy.conf
2023-05-04T09:23:37.643265933Z - /etc/nginx/conf.d/include/proxy.conf
2023-05-04T09:23:37.662778900Z ++ for FILE in $FILES
2023-05-04T09:23:37.662887605Z ++ echo '- /etc/nginx/conf.d/include/block-exploits.conf'
2023-05-04T09:23:37.662904521Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/block-exploits.conf
2023-05-04T09:23:37.662778859Z - /etc/nginx/conf.d/include/block-exploits.conf
2023-05-04T09:23:37.669046494Z ++ for FILE in $FILES
2023-05-04T09:23:37.669167782Z ++ echo '- /etc/nginx/conf.d/include/ip_ranges.conf'
2023-05-04T09:23:37.669184782Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/ip_ranges.conf
2023-05-04T09:23:37.669089826Z - /etc/nginx/conf.d/include/ip_ranges.conf
2023-05-04T09:23:37.675368545Z - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
2023-05-04T09:23:37.675342504Z ++ for FILE in $FILES
2023-05-04T09:23:37.675489374Z ++ echo '- /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf'
2023-05-04T09:23:37.675609996Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
2023-05-04T09:23:37.681723053Z ++ for FILE in $FILES
2023-05-04T09:23:37.681842716Z ++ echo '- /etc/nginx/conf.d/include/force-ssl.conf'
2023-05-04T09:23:37.681858465Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/force-ssl.conf
2023-05-04T09:23:37.681752135Z - /etc/nginx/conf.d/include/force-ssl.conf
2023-05-04T09:23:37.687759154Z - /etc/nginx/conf.d/include/assets.conf
2023-05-04T09:23:37.687732280Z ++ for FILE in $FILES
2023-05-04T09:23:37.687873734Z ++ echo '- /etc/nginx/conf.d/include/assets.conf'
2023-05-04T09:23:37.687888233Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/assets.conf
2023-05-04T09:23:37.693759340Z ++ for FILE in $FILES
2023-05-04T09:23:37.693889877Z ++ echo '- /etc/nginx/conf.d/include/ssl-ciphers.conf'
2023-05-04T09:23:37.693932168Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/ssl-ciphers.conf
2023-05-04T09:23:37.693824296Z - /etc/nginx/conf.d/include/ssl-ciphers.conf
2023-05-04T09:23:37.699476659Z ++ for FILE in $FILES
2023-05-04T09:23:37.699650321Z ++ echo '- /etc/nginx/conf.d/include/resolvers.conf'
2023-05-04T09:23:37.699668612Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/include/resolvers.conf
2023-05-04T09:23:37.699515408Z - /etc/nginx/conf.d/include/resolvers.conf
2023-05-04T09:23:37.704455336Z ++ for FILE in $FILES
2023-05-04T09:23:37.704567499Z ++ echo '- /etc/nginx/conf.d/default.conf'
2023-05-04T09:23:37.704582665Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/default.conf
2023-05-04T09:23:37.704483751Z - /etc/nginx/conf.d/default.conf
2023-05-04T09:23:37.710164656Z ++ for FILE in $FILES
2023-05-04T09:23:37.710284569Z ++ echo '- /etc/nginx/conf.d/production.conf'
2023-05-04T09:23:37.710301901Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /etc/nginx/conf.d/production.conf
2023-05-04T09:23:37.710205529Z - /etc/nginx/conf.d/production.conf
2023-05-04T09:23:37.715954973Z ++ chown -R 0:0 /etc/nginx/conf.d
2023-05-04T09:23:37.719720021Z ++ process_folder /data/nginx
2023-05-04T09:23:37.720711323Z +++ find /data/nginx -type f -name '*.conf'
2023-05-04T09:23:37.725083643Z ++ FILES='/data/nginx/proxy_host/7.conf
2023-05-04T09:23:37.725183807Z /data/nginx/proxy_host/14.conf
2023-05-04T09:23:37.725199056Z /data/nginx/proxy_host/4.conf
2023-05-04T09:23:37.725212598Z /data/nginx/proxy_host/6.conf
2023-05-04T09:23:37.725213889Z Enabling IPV6 in hosts in: /data/nginx
2023-05-04T09:23:37.725226472Z /data/nginx/proxy_host/21.conf
2023-05-04T09:23:37.725262179Z /data/nginx/proxy_host/20.conf
2023-05-04T09:23:37.725276304Z /data/nginx/proxy_host/1.conf
2023-05-04T09:23:37.725312553Z /data/nginx/proxy_host/19.conf
2023-05-04T09:23:37.725329802Z /data/nginx/proxy_host/3.conf
2023-05-04T09:23:37.725342927Z /data/nginx/proxy_host/15.conf
2023-05-04T09:23:37.725356051Z /data/nginx/proxy_host/5.conf
2023-05-04T09:23:37.725369301Z /data/nginx/proxy_host/12.conf
2023-05-04T09:23:37.725382217Z /data/nginx/proxy_host/9.conf
2023-05-04T09:23:37.725395217Z /data/nginx/proxy_host/2.conf
2023-05-04T09:23:37.725408050Z /data/nginx/proxy_host/8.conf
2023-05-04T09:23:37.725420591Z /data/nginx/proxy_host/24.conf
2023-05-04T09:23:37.725433299Z /data/nginx/proxy_host/11.conf
2023-05-04T09:23:37.725446174Z /data/nginx/proxy_host/13.conf
2023-05-04T09:23:37.725458840Z /data/nginx/proxy_host/16.conf
2023-05-04T09:23:37.725471881Z /data/nginx/proxy_host/22.conf
2023-05-04T09:23:37.725484589Z /data/nginx/proxy_host/23.conf
2023-05-04T09:23:37.725497589Z /data/nginx/proxy_host/18.conf
2023-05-04T09:23:37.725510297Z /data/nginx/proxy_host/10.conf
2023-05-04T09:23:37.725591627Z /data/nginx/proxy_host/17.conf'
2023-05-04T09:23:37.725504880Z - /data/nginx/proxy_host/7.conf
2023-05-04T09:23:37.725609877Z ++ SED_REGEX=
2023-05-04T09:23:37.725658000Z ++ '[' '' == true ']'
2023-05-04T09:23:37.725673208Z ++ '[' '' == on ']'
2023-05-04T09:23:37.725695374Z ++ '[' '' == 1 ']'
2023-05-04T09:23:37.725708665Z ++ '[' '' == yes ']'
2023-05-04T09:23:37.725721498Z ++ echo 'Enabling IPV6 in hosts in: /data/nginx'
2023-05-04T09:23:37.725734664Z ++ SED_REGEX='s/^(\s*)#listen \[::\]/\1listen [::]/g'
2023-05-04T09:23:37.725748081Z ++ for FILE in $FILES
2023-05-04T09:23:37.725760580Z ++ echo '- /data/nginx/proxy_host/7.conf'
2023-05-04T09:23:37.725773413Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/7.conf
2023-05-04T09:23:37.730919918Z ++ for FILE in $FILES
2023-05-04T09:23:37.730953500Z - /data/nginx/proxy_host/14.conf
2023-05-04T09:23:37.731031164Z ++ echo '- /data/nginx/proxy_host/14.conf'
2023-05-04T09:23:37.731078579Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/14.conf
2023-05-04T09:23:37.861576630Z ++ for FILE in $FILES
2023-05-04T09:23:37.861699959Z ++ echo '- /data/nginx/proxy_host/4.conf'
2023-05-04T09:23:37.861716250Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/4.conf
2023-05-04T09:23:37.861610337Z - /data/nginx/proxy_host/4.conf
2023-05-04T09:23:37.866887004Z ++ for FILE in $FILES
2023-05-04T09:23:37.866999750Z ++ echo '- /data/nginx/proxy_host/6.conf'
2023-05-04T09:23:37.866926461Z - /data/nginx/proxy_host/6.conf
2023-05-04T09:23:37.867015208Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/6.conf
2023-05-04T09:23:37.872254043Z ++ for FILE in $FILES
2023-05-04T09:23:37.872382330Z ++ echo '- /data/nginx/proxy_host/21.conf'
2023-05-04T09:23:37.872399372Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/21.conf
2023-05-04T09:23:37.872294583Z - /data/nginx/proxy_host/21.conf
2023-05-04T09:23:37.877953446Z - /data/nginx/proxy_host/20.conf
2023-05-04T09:23:37.877929947Z ++ for FILE in $FILES
2023-05-04T09:23:37.878079484Z ++ echo '- /data/nginx/proxy_host/20.conf'
2023-05-04T09:23:37.878094650Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/20.conf
2023-05-04T09:23:37.883596602Z ++ for FILE in $FILES
2023-05-04T09:23:37.883720639Z ++ echo '- /data/nginx/proxy_host/1.conf'
2023-05-04T09:23:37.883623601Z - /data/nginx/proxy_host/1.conf
2023-05-04T09:23:37.883738556Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/1.conf
2023-05-04T09:23:37.889008098Z ++ for FILE in $FILES
2023-05-04T09:23:37.889173176Z ++ echo '- /data/nginx/proxy_host/19.conf'
2023-05-04T09:23:37.889189217Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/19.conf
2023-05-04T09:23:37.889037638Z - /data/nginx/proxy_host/19.conf
2023-05-04T09:23:37.894420510Z ++ for FILE in $FILES
2023-05-04T09:23:37.894543798Z ++ echo '- /data/nginx/proxy_host/3.conf'
2023-05-04T09:23:37.894560089Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/3.conf
2023-05-04T09:23:37.894454842Z - /data/nginx/proxy_host/3.conf
2023-05-04T09:23:37.899969502Z ++ for FILE in $FILES
2023-05-04T09:23:37.900090998Z ++ echo '- /data/nginx/proxy_host/15.conf'
2023-05-04T09:23:37.900106998Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/15.conf
2023-05-04T09:23:37.899998543Z - /data/nginx/proxy_host/15.conf
2023-05-04T09:23:37.905441996Z - /data/nginx/proxy_host/5.conf
2023-05-04T09:23:37.905442038Z ++ for FILE in $FILES
2023-05-04T09:23:37.905571867Z ++ echo '- /data/nginx/proxy_host/5.conf'
2023-05-04T09:23:37.905587075Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/5.conf
2023-05-04T09:23:37.911195356Z - /data/nginx/proxy_host/12.conf
2023-05-04T09:23:37.911204189Z ++ for FILE in $FILES
2023-05-04T09:23:37.911348018Z ++ echo '- /data/nginx/proxy_host/12.conf'
2023-05-04T09:23:37.911363809Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/12.conf
2023-05-04T09:23:37.917258582Z ++ for FILE in $FILES
2023-05-04T09:23:37.917476866Z ++ echo '- /data/nginx/proxy_host/9.conf'
2023-05-04T09:23:37.917505615Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/9.conf
2023-05-04T09:23:37.917507032Z - /data/nginx/proxy_host/9.conf
2023-05-04T09:23:37.922996317Z ++ for FILE in $FILES
2023-05-04T09:23:37.923106897Z ++ echo '- /data/nginx/proxy_host/2.conf'
2023-05-04T09:23:37.923124105Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/2.conf
2023-05-04T09:23:37.923163479Z - /data/nginx/proxy_host/2.conf
2023-05-04T09:23:37.928785510Z ++ for FILE in $FILES
2023-05-04T09:23:37.928911256Z ++ echo '- /data/nginx/proxy_host/8.conf'
2023-05-04T09:23:37.928928422Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/8.conf
2023-05-04T09:23:37.928820050Z - /data/nginx/proxy_host/8.conf
2023-05-04T09:23:37.934904525Z - /data/nginx/proxy_host/24.conf
2023-05-04T09:23:37.934942357Z ++ for FILE in $FILES
2023-05-04T09:23:37.935055853Z ++ echo '- /data/nginx/proxy_host/24.conf'
2023-05-04T09:23:37.935071353Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/24.conf
2023-05-04T09:23:37.940954917Z ++ for FILE in $FILES
2023-05-04T09:23:37.941213701Z ++ echo '- /data/nginx/proxy_host/11.conf'
2023-05-04T09:23:37.941262158Z - /data/nginx/proxy_host/11.conf
2023-05-04T09:23:37.941452068Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/11.conf
2023-05-04T09:23:37.947225011Z ++ for FILE in $FILES
2023-05-04T09:23:37.947348341Z ++ echo '- /data/nginx/proxy_host/13.conf'
2023-05-04T09:23:37.947266843Z - /data/nginx/proxy_host/13.conf
2023-05-04T09:23:37.947364549Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/13.conf
2023-05-04T09:23:37.952550843Z ++ for FILE in $FILES
2023-05-04T09:23:37.952675673Z ++ echo '- /data/nginx/proxy_host/16.conf'
2023-05-04T09:23:37.952691797Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/16.conf
2023-05-04T09:23:37.952597175Z - /data/nginx/proxy_host/16.conf
2023-05-04T09:23:37.958319203Z ++ for FILE in $FILES
2023-05-04T09:23:37.958439699Z ++ echo '- /data/nginx/proxy_host/22.conf'
2023-05-04T09:23:37.958455824Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/22.conf
2023-05-04T09:23:37.958349910Z - /data/nginx/proxy_host/22.conf
2023-05-04T09:23:37.963675492Z ++ for FILE in $FILES
2023-05-04T09:23:37.963796780Z ++ echo '- /data/nginx/proxy_host/23.conf'
2023-05-04T09:23:37.963812530Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/23.conf
2023-05-04T09:23:37.963708408Z - /data/nginx/proxy_host/23.conf
2023-05-04T09:23:37.969021365Z - /data/nginx/proxy_host/18.conf
2023-05-04T09:23:37.968996408Z ++ for FILE in $FILES
2023-05-04T09:23:37.969136403Z ++ echo '- /data/nginx/proxy_host/18.conf'
2023-05-04T09:23:37.969151528Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/18.conf
2023-05-04T09:23:37.974301116Z ++ for FILE in $FILES
2023-05-04T09:23:37.974441528Z ++ echo '- /data/nginx/proxy_host/10.conf'
2023-05-04T09:23:37.974458319Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/10.conf
2023-05-04T09:23:37.974338031Z - /data/nginx/proxy_host/10.conf
2023-05-04T09:23:37.979709028Z ++ for FILE in $FILES
2023-05-04T09:23:37.979824608Z ++ echo '- /data/nginx/proxy_host/17.conf'
2023-05-04T09:23:37.979840482Z ++ sed -E -i 's/^(\s*)#listen \[::\]/\1listen [::]/g' /data/nginx/proxy_host/17.conf
2023-05-04T09:23:37.979739152Z - /data/nginx/proxy_host/17.conf
2023-05-04T09:23:37.985115483Z ++ chown -R 0:0 /data/nginx
2023-05-04T09:23:37.989188604Z + . /etc/s6-overlay/s6-rc.d/prepare/60-secrets.sh
2023-05-04T09:23:37.990715931Z ++ set -e
2023-05-04T09:23:37.990804345Z ++ log_info 'Docker secrets ...'
2023-05-04T09:23:37.990889801Z ++ echo -e '\E[1;34m? \E[1;36mDocker secrets ...\E[0m'
2023-05-04T09:23:37.990854552Z ? Docker secrets ...
2023-05-04T09:23:37.993035816Z +++ find /var/run/s6/container_environment/
2023-05-04T09:23:37.993391430Z +++ grep '__FILE$'
2023-05-04T09:23:38.006675303Z + . /etc/s6-overlay/s6-rc.d/prepare/90-banner.sh
2023-05-04T09:23:38.007552525Z ++ set -e
2023-05-04T09:23:38.007626064Z ++ set +x
2023-05-04T09:23:38.022085983Z 
2023-05-04T09:23:38.022186147Z -------------------------------------
2023-05-04T09:23:38.022200521Z  _   _ ____  __  __
2023-05-04T09:23:38.022213354Z | \ | |  _ \|  \/  |
2023-05-04T09:23:38.022226187Z |  \| | |_) | |\/| |
2023-05-04T09:23:38.022239187Z | |\  |  __/| |  | |
2023-05-04T09:23:38.022251686Z |_| \_|_|   |_|  |_|
2023-05-04T09:23:38.022264311Z -------------------------------------
2023-05-04T09:23:38.022276727Z User:  npm PUID:0 ID:0 GROUP:0
2023-05-04T09:23:38.022289060Z Group: npm PGID:0 ID:0
2023-05-04T09:23:38.022301393Z -------------------------------------
2023-05-04T09:23:38.022313809Z 
2023-05-04T09:23:38.023750931Z s6-rc: info: service prepare successfully started
2023-05-04T09:23:38.024315705Z s6-rc: info: service nginx: starting
2023-05-04T09:23:38.024843730Z s6-rc: info: service frontend: starting
2023-05-04T09:23:38.025645079Z s6-rc: info: service backend: starting
2023-05-04T09:23:38.034208143Z s6-rc: info: service nginx successfully started
2023-05-04T09:23:38.037834111Z ? Starting nginx ...
2023-05-04T09:23:38.038767999Z s6-rc: info: service frontend successfully started
2023-05-04T09:23:38.040271535Z s6-rc: info: service backend successfully started
2023-05-04T09:23:38.040409614Z ? Starting backend ...
2023-05-04T09:23:38.040815517Z s6-rc: info: service legacy-services: starting
2023-05-04T09:23:38.087354508Z s6-rc: info: service legacy-services successfully started
2023-05-04T09:23:43.204775004Z [5/4/2023] [9:23:43 AM] [Global   ] › ?  info      Using Sqlite: /data/database.sqlite
2023-05-04T09:23:43.208566801Z [5/4/2023] [9:23:43 AM] [Global   ] › ?  info      Keys file exists OK
2023-05-04T09:23:53.891046516Z [5/4/2023] [9:23:53 AM] [Migrate  ] › ?  info      Current database version: none
2023-05-04T09:23:54.016622762Z [5/4/2023] [9:23:54 AM] [Setup    ] › ?  info      Admin user setup not required
2023-05-04T09:23:54.026458289Z [5/4/2023] [9:23:54 AM] [Setup    ] › ?  info      Default setting setup not required
2023-05-04T09:23:54.039337545Z [5/4/2023] [9:23:54 AM] [Setup    ] › ?  info      Logrotate Timer initialized
2023-05-04T09:23:54.137071473Z [5/4/2023] [9:23:54 AM] [Setup    ] › ?  warning   Error: Command failed: logrotate /etc/logrotate.d/nginx-proxy-manager 
2023-05-04T09:23:54.137170391Z 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.
2023-05-04T09:23:54.137197308Z 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.
2023-05-04T09:23:54.137213183Z 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.
2023-05-04T09:23:54.137228725Z 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.
2023-05-04T09:23:54.137244391Z 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.
2023-05-04T09:23:54.137259683Z 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.
2023-05-04T09:23:54.137275225Z 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.
2023-05-04T09:23:54.137414684Z 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.
2023-05-04T09:23:54.137446851Z error: skipping "/data/logs/proxy-host-17_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.
2023-05-04T09:23:54.137463310Z error: skipping "/data/logs/proxy-host-18_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.
2023-05-04T09:23:54.137479393Z error: skipping "/data/logs/proxy-host-19_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.
2023-05-04T09:23:54.137494476Z 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.
2023-05-04T09:23:54.137552352Z error: skipping "/data/logs/proxy-host-20_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.
2023-05-04T09:23:54.137569310Z error: skipping "/data/logs/proxy-host-21_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.
2023-05-04T09:23:54.137584769Z error: skipping "/data/logs/proxy-host-22_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.
2023-05-04T09:23:54.137603977Z error: skipping "/data/logs/proxy-host-23_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.
2023-05-04T09:23:54.137619269Z error: skipping "/data/logs/proxy-host-24_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.
2023-05-04T09:23:54.137634561Z 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.
2023-05-04T09:23:54.137649602Z 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.
2023-05-04T09:23:54.137665061Z 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.
2023-05-04T09:23:54.137680186Z 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.
2023-05-04T09:23:54.137695186Z 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.
2023-05-04T09:23:54.137713978Z 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.
2023-05-04T09:23:54.137729895Z 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.
2023-05-04T09:23:54.137759603Z 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.
2023-05-04T09:23:54.137776228Z 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.
2023-05-04T09:23:54.137791978Z 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.
2023-05-04T09:23:54.137807854Z 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.
2023-05-04T09:23:54.137823187Z 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.
2023-05-04T09:23:54.137838604Z 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.
2023-05-04T09:23:54.137857312Z 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.
2023-05-04T09:23:54.137873646Z 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.
2023-05-04T09:23:54.137891021Z 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.
2023-05-04T09:23:54.137906313Z error: skipping "/data/logs/proxy-host-17_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.
2023-05-04T09:23:54.137921479Z error: skipping "/data/logs/proxy-host-18_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.
2023-05-04T09:23:54.137937188Z error: skipping "/data/logs/proxy-host-19_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.
2023-05-04T09:23:54.137964896Z 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.
2023-05-04T09:23:54.137981105Z error: skipping "/data/logs/proxy-host-20_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.
2023-05-04T09:23:54.137999105Z error: skipping "/data/logs/proxy-host-21_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.
2023-05-04T09:23:54.138015397Z error: skipping "/data/logs/proxy-host-22_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.
2023-05-04T09:23:54.138031313Z error: skipping "/data/logs/proxy-host-23_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.
2023-05-04T09:23:54.138046980Z error: skipping "/data/logs/proxy-host-24_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.
2023-05-04T09:23:54.138062439Z 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.
2023-05-04T09:23:54.138077605Z 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.
2023-05-04T09:23:54.138093189Z 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.
2023-05-04T09:23:54.138108481Z 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.
2023-05-04T09:23:54.138127356Z 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.
2023-05-04T09:23:54.138143398Z 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.
2023-05-04T09:23:54.138171648Z 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.
2023-05-04T09:23:54.138187523Z 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.
2023-05-04T09:23:54.138202398Z 
2023-05-04T09:23:54.138214606Z     at ChildProcess.exithandler (node:child_process:402:12)
2023-05-04T09:23:54.138227440Z     at ChildProcess.emit (node:events:513:28)
2023-05-04T09:23:54.138239857Z     at maybeClose (node:internal/child_process:1100:16)
2023-05-04T09:23:54.138252398Z     at Socket.<anonymous> (node:internal/child_process:458:11)
2023-05-04T09:23:54.138268273Z     at Socket.emit (node:events:513:28)
2023-05-04T09:23:54.138281399Z     at Pipe.<anonymous> (node:net:301:12)
2023-05-04T09:23:54.139219113Z [5/4/2023] [9:23:54 AM] [IP Ranges] › ?  info      Fetching IP Ranges from online services...
2023-05-04T09:23:54.142161925Z [5/4/2023] [9:23:54 AM] [IP Ranges] › ?  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
2023-05-04T09:23:55.313975060Z [5/4/2023] [9:23:55 AM] [IP Ranges] › ?  info      Fetching https://www.cloudflare.com/ips-v4
2023-05-04T09:23:55.415445806Z [5/4/2023] [9:23:55 AM] [IP Ranges] › ?  info      Fetching https://www.cloudflare.com/ips-v6
2023-05-04T09:23:55.583038678Z [5/4/2023] [9:23:55 AM] [SSL      ] › ?  info      Let's Encrypt Renewal Timer initialized
2023-05-04T09:23:55.585097401Z [5/4/2023] [9:23:55 AM] [SSL      ] › ?  info      Renewing SSL certs close to expiry...
2023-05-04T09:23:55.614173227Z [5/4/2023] [9:23:55 AM] [IP Ranges] › ?  info      IP Ranges Renewal Timer initialized
2023-05-04T09:23:55.631224762Z [5/4/2023] [9:23:55 AM] [Global   ] › ?  info      Backend PID 176 listening on port 3000 ...
2023-05-04T09:23:59.388446220Z [5/4/2023] [9:23:59 AM] [Nginx    ] › ?  info      Testing Nginx configuration
2023-05-04T09:24:07.597092412Z [5/4/2023] [9:24:07 AM] [Nginx    ] › ?  info      Reloading Nginx
2023-05-04T09:24:08.093741110Z [5/4/2023] [9:24:08 AM] [SSL      ] › ?  info      Renew Complete
rymancl commented 1 year ago

Ah yep can you add DEBUG=true to the docker environment variables?

I'm not who your comment was directed at, but even with DEBUG=true I don't get verbose logs on Synology. On-boot failure to start: image

    image: jc21/nginx-proxy-manager:github-s6-verbose
    container_name: nginx_proxy_manager
    profiles:
      - all
      - core
    network_mode: synobridge
    environment:
      - TZ=America/New_York
      - PUID=0
      - PGID=0
      - DEBUG=true
      # - S6_CMD_WAIT_FOR_SERVICES_MAXTIME=60000
    ports:
      - "8341:80"
      - "81:81"
      - "8766:443"
    volumes:
      - /volume1/docker/npm/config.json:/app/config/production.json
      - /volume1/docker/npm/data:/data
      - /volume1/docker/npm/letsencrypt:/etc/letsencrypt
    restart: unless-stopped
Sungray commented 1 year ago

Here's with DEBUG=true, the timeout happens on /etc/letsencrypt

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service prepare: starting
+ . /etc/s6-overlay/s6-rc.d/prepare/10-usergroup.sh
++ set -e
++ log_info 'Configuring npm user ...'
++ echo -e '\E[1;34m❯ \E[1;36mConfiguring npm user ...\E[0m'
++ id -u npm
++ useradd -o -u 99 -U -d /tmp/npmuserhome -s /bin/false npm
++ log_info 'Configuring npm group ...'
++ echo -e '\E[1;34m❯ \E[1;36mConfiguring npm group ...\E[0m'
+++ get_group_id npm
+++ '[' npm '!=' '' ']'
+++ getent group npm
+++ cut -d: -f3
++ '[' 1000 = '' ']'
++ groupmod -o -g 100 npm
++ groupmod -o -g 100 npm
+++ get_group_id npm
+++ '[' npm '!=' '' ']'
+++ getent group npm
+++ cut -d: -f3
++ '[' 100 '!=' 100 ']'
++ usermod -G 100 npm
+++ id -g npm
++ '[' 100 '!=' 100 ']'
++ mkdir -p /tmp/npmuserhome
++ chown -R 99:100 /tmp/npmuserhome
+ . /etc/s6-overlay/s6-rc.d/prepare/20-paths.sh
++ set -e
++ log_info 'Checking paths ...'
++ echo -e '\E[1;34m❯ \E[1;36mChecking paths ...\E[0m'
++ '[' '!' -d /data ']'
++ '[' '!' -d /etc/letsencrypt ']'
++ mkdir -p /data/nginx /data/custom_ssl /data/logs /data/access /data/nginx/default_host /data/nginx/default_www /data/nginx/proxy_host /data/nginx/redirection_host /data/nginx/stream /data/nginx/dead_host /data/nginx/temp /data/letsencrypt-acme-challenge /run/nginx /tmp/nginx/body /var/log/nginx /var/lib/nginx/cache/public /var/lib/nginx/cache/private /var/cache/nginx/proxy_temp
++ touch /var/log/nginx/error.log
++ chmod 777 /var/log/nginx/error.log
++ chmod -R 777 /var/cache/nginx
++ chmod 644 /etc/logrotate.d/nginx-proxy-manager
+ . /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh
++ set -e
++ log_info 'Setting ownership ...'
++ echo -e '\E[1;34m❯ \E[1;36mSetting ownership ...\E[0m'
++ chown root /tmp/nginx
++ chown -R 99:100 /data
++ chown -R 99:100 /etc/letsencrypt
s6-rc: fatal: timed out
s6-sudoc: fatal: unable to get exit status from server: Operation timed out
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
❯ Configuring npm user ...
❯ Configuring npm group ...
❯ Checking paths ...
❯ Setting ownership ...
Sungray commented 1 year ago

I noticed that there are 23.398 files in both the /etc/letsencrypt/csr folder and /etc/letsencrypt/keys folder. I'm guessing the chown isn't fast enough and has a set timeout of around 1000ms which isn't enough for the buttload of files there. How can I clean these folders safely?

jc21 commented 1 year ago

@rymancl in fact yes I am seeing more information in your output as expected.

@Sungray you can run cert-prune inside the docker container to clean up those archived files. Just be sure to back up your letsencrypt folder first.

Sungray commented 1 year ago

@Sungray you can run cert-prune inside the docker container to clean up those archived files. Just be sure to back up your letsencrypt folder first.

Yes, cert-prune fixed the problem for me. It deleted around 500 stale certificates, 23k csr and 23k keys. There must have been a big issue at some point that went unnoticed, and the change to 2.10.0 introduced new timeouts on chown which were not handled fast enough.

Now all is good. Thank you!

rymancl commented 1 year ago

Cross-posting this from #2750

With v2.10.3, npm is now working perfectly again on my Synology. 🎉 I removed

- PUID=0
- PGID=0

from my env vars and that's it.

I tested a fresh install and several server reboots and npm didn't have any issues starting up anymore.

janaxhell commented 1 year ago

@jc21

@janaxhell pull the new build of the github-s6-verbose tag and try again and let me know how that goes

Hi, looks to me that 2.10.3 is working fine now on Orange Pi 3 LTS. After reboot it starts normally. Unfortunately I see that with :github-s6-verbose logs have grown up huge, 4Gb+ and my whole internal storage is 8Gb. How do I get rid of those huge logs? I am on :latest now.

anto294 commented 1 year ago

Hello, I have a strange issue. My npm stuck at setting ownership, exactly on "chown -R 1000:1000 /opt/certbot". The OS is TrueNAS scale, but I use direct docker :latest image (not ix-sys version).

In fact, if I run that command from the shell, it never ends.

If I do quickly after deploy these commands, npm start well.

rm -rf /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh
touch /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh
chown -R "1000:1000" /data
chown -R "1000:1000" /etc/letsencrypt
chown -R "1000:1000" /run/nginx
chown -R "1000:1000" /tmp/nginx
chown -R "1000:1000" /var/cache/nginx
chown -R "1000:1000" /var/lib/logrotate
chown -R "1000:1000" /var/lib/nginx
chown -R "1000:1000" /var/log/nginx
chown -R "1000:1000" /etc/nginx/nginx
chown -R "1000:1000" /etc/nginx/nginx.conf
chown -R "1000:1000" /etc/nginx/conf.d

EDIT

chown -R  1000:1000  /opt/certbot -v

logs 1 file per second, so the deploy go timeout.

TristanHarms commented 1 year ago

Hello, I have a strange issue. My npm stuck at setting ownership, exactly on "chown -R 1000:1000 /opt/certbot". The OS is TrueNAS scale, but I use direct docker :latest image (not ix-sys version).

In fact, if I run that command from the shell, it never ends.

If I do quickly after deploy this commands, npm start well. rm -rf /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh touch /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh chown -R "1000:1000" /data chown -R "1000:1000" /etc/letsencrypt chown -R "1000:1000" /run/nginx chown -R "1000:1000" /tmp/nginx chown -R "1000:1000" /var/cache/nginx chown -R "1000:1000" /var/lib/logrotate chown -R "1000:1000" /var/lib/nginx chown -R "1000:1000" /var/log/nginx chown -R "1000:1000" /etc/nginx/nginx chown -R "1000:1000" /etc/nginx/nginx.conf chown -R "1000:1000" /etc/nginx/conf.d

EDIT "chown -R 1000:1000 /opt/certbot -v" log 1 file per second, so the deploy go timeout

I can confirm that this is exactly the same issue I've been seeing from my side as well. Also running TrueNAS Scale, broken since 2.10.x.

Sungray commented 1 year ago

@anto294 @TristanHarms did you guys try the cert-prune command in the container? For me it was a problem of letsencrypt, thousands of junk files kept for a long time causing a timeout. Fixed the problem instantly.

TristanHarms commented 1 year ago

@anto294 @TristanHarms did you guys try the cert-prune command in the container? For me it was a problem of letsencrypt, thousands of junk files kept for a long time causing a timeout. Fixed the problem instantly.

I did, it only removed 12 entries in my case and didn't fix the issue. It also didn't change the issue as indicated by @anto294 where chowning files seems to be extremely slow, leading to a timeout on deploy.

blaine07 commented 1 year ago

@anto294 @TristanHarms did you guys try the cert-prune command in the container? For me it was a problem of letsencrypt, thousands of junk files kept for a long time causing a timeout. Fixed the problem instantly.

Does certprune commands work now; at one point they were defunct?

anto294 commented 1 year ago

@anto294 @TristanHarms did you guys try the cert-prune command in the container? For me it was a problem of letsencrypt, thousands of junk files kept for a long time causing a timeout. Fixed the problem instantly.

Of course, I have also tested with fresh containers.

JBake130 commented 1 year ago

Im running unraid, and get this if I use :latest, but if i use :2.10.2 or now .3 it starts up fine.

just deleted the containers and images and started fresh. still get permission denied with :latest

DcR-NL commented 1 year ago

Im running unraid, and get this if I use :latest, but if i use :2.10.2 or now .3 it starts up fine.

You must be using an old "latest" than. Currently tag "latest", "2.10.3" and "v2" are the same image.

JBake130 commented 1 year ago

Im running unraid, and get this if I use :latest, but if i use :2.10.2 or now .3 it starts up fine.

You must be using an old "latest" than. Currently tag "latest", "2.10.3" and "v2" are the same image.

Ya it’s a fresh install, v2 just removed my container completely since it failed. Latest and 2.10.3 should be exact same thing, but only works if I define the version

also to add just jc21/nginx-proxy-manager (default on install) fails to start too. Only works when I specify a version. Weird

SHASHWATAA commented 1 year ago

I was having the exact same issue @JBake130. Thanks that fixed it.

ljpaff commented 1 year ago

Is there any update for Rpi ecosystem?

IgnatBeresnev commented 1 year ago

Can confirm, I have the same issue in TrueNAS Scale with the container getting stuck at chown -R xx:xx /opt/certbot, exactly as in https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2753#issuecomment-1556126836. Very annoying

I ended up mounting /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh to a script I created on the host, with all of the same contents, but with the modified chown line that causes the issue (just let it run in the background):

...
# Prevents errors when installing python certbot plugins when non-root
nohup chown -R "$PUID:$PGID" /opt/certbot -v &
carsten-walther commented 1 year ago

I had trouble installing Nginx Proxy Manager on Proxmox in LXC container.

The install script (https://github.com/ej52/proxmox-scripts/blob/main/lxc/nginx-proxy-manager/install/alpine.sh) was telling me:

nginx: [emerg] getpwnam("npm") failed ....

Solution was create a new user npm:

This fixed it for me.

thisisnotfez commented 1 year ago

This is the only log item I am receiving with the github-s6 image and with debug enabled.

s6-rc-compile: fatal: unable to read /etc/s6-overlay/s6-rc.d/prepare/type: No such file or directory
deftdawg commented 1 year ago

I gave up trying to get this to run as npm user properly on v2.10.2 and v2.10.3... Instead I needed to hack the following into my home-asssistant addon fork's Dockerfile to get the container to start and run certbot. Maybe this will help someone, but I don't recommend it.

# trying to start as user: npm fails, borked s6 overlay stuff; so delete the the user
#  and just run as root to get going -- NOTE: running as root IS BAD
RUN  sed -i '/user npm;/d' /etc/nginx/nginx.conf 

# create the missing certbot in /opt and set include-system-site-packages true 
# so --user doesn't cause the certbot command to fail
RUN \
  cd /opt \
  && python -m venv certbot \
  && sed -i 's/include-system-site-packages = false/include-system-site-packages = true/' /opt/certbot/pyvenv.cfg
heisian commented 1 year ago

This is how to fix it: https://github.com/truenas/charts/issues/1212#issuecomment-1568518666

S6_STAGE2_HOOK=sed -i $d /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh

This will remove the last line that was added in version 2.10+ chown -R "$PUID:$PGID" /opt/certbot with takes a long time on HDD pools

Or you can just wait for 5-10mins like I did...

anto294 commented 1 year ago

This is how to fix it: truenas/charts#1212 (comment)

S6_STAGE2_HOOK=sed -i $d /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh This will remove the last line that was added in version 2.10+ chown -R "$PUID:$PGID" /opt/certbot with takes a long time on HDD pools

Or you can just wait for 5-10mins like I did...

Mine won't even start after one night. HDD pool.

Thanks for the ENV, they work :)

github-actions[bot] commented 5 months ago

Issue is now considered stale. If you want to keep it open, please comment :+1:

Spokeek commented 3 weeks ago

This is how to fix it: truenas/charts#1212 (comment)

S6_STAGE2_HOOK=sed -i $d /etc/s6-overlay/s6-rc.d/prepare/30-ownership.sh This will remove the last line that was added in version 2.10+ chown -R "$PUID:$PGID" /opt/certbot with takes a long time on HDD pools

Or you can just wait for 5-10mins like I did...

This does indeed skips the steps and allows the app to start (i tried it on the container version too). Hopefully this can be fixed in a more proper way.