NginxProxyManager/nginx-proxy-manager

Container long time to start /opt/certbot/lib/python3.11/site-packages

Closed this issue · 6 comments

Generate /opt/certbot/lib/python3.11/site-packages make about 10 minutes to DONE !

Version : latest

2025-09-26 07:30:18.123320+00:00�[1;34m❯ �[1;36mConfiguring npm user ...�[0m
2025-09-26 07:30:18.408916+00:00�[1;34m❯ �[1;36mConfiguring npm group ...�[0m
2025-09-26 07:30:18.461548+00:00�[1;34m❯ �[1;36mChecking paths ...�[0m
2025-09-26 07:30:18.479825+00:00�[1;34m❯ �[1;36mSetting ownership ...�[0m
2025-09-26 07:30:18.481767+00:00- /data ... 
2025-09-26 07:30:18.481789+00:00SKIPPED
2025-09-26 07:30:18.482768+00:00- /etc/letsencrypt ... 
2025-09-26 07:30:18.482787+00:00SKIPPED
2025-09-26 07:30:18.483736+00:00- /run/nginx ... 
2025-09-26 07:30:18.484565+00:00DONE
2025-09-26 07:30:18.485637+00:00- /tmp/nginx ... 
2025-09-26 07:30:18.486504+00:00DONE
2025-09-26 07:30:18.487490+00:00- /var/cache/nginx ... 
2025-09-26 07:30:18.488338+00:00DONE
2025-09-26 07:30:18.489382+00:00- /var/lib/logrotate ... 
2025-09-26 07:30:18.490346+00:00DONE
2025-09-26 07:30:18.491299+00:00- /var/lib/nginx ... 
2025-09-26 07:30:18.492216+00:00DONE
2025-09-26 07:30:18.493220+00:00- /var/log/nginx ... 
2025-09-26 07:30:18.494035+00:00DONE
2025-09-26 07:30:18.495068+00:00- /etc/nginx/nginx ... 
2025-09-26 07:30:18.525450+00:00DONE
2025-09-26 07:30:18.526615+00:00- /etc/nginx/nginx.conf ... 
2025-09-26 07:30:18.541893+00:00DONE
2025-09-26 07:30:18.543137+00:00- /etc/nginx/conf.d ... 
2025-09-26 07:30:18.928226+00:00DONE
2025-09-26 07:30:18.935644+00:00�[1;34m❯ �[1;36mChanging ownership of certbot directories, this may take some time ...�[0m
2025-09-26 07:30:18.939962+00:00- /opt/certbot ... 
2025-09-26 07:30:18.944578+00:00DONE
2025-09-26 07:30:18.949036+00:00- /opt/certbot/bin ... 
2025-09-26 07:30:18.952931+00:00DONE
2025-09-26 07:30:19.019142+00:00- /opt/certbot/lib/python3.11/site-packages ... 
2025-09-26 07:39:06.611115+00:00DONE
2025-09-26 07:39:06.612259+00:00�[1;34m❯ �[1;36mDynamic resolvers ...�[0m
2025-09-26 07:39:06.624751+00:00�[1;34m❯ �[1;36mIPv6 ...�[0m
2025-09-26 07:39:06.637431+00:00Enabling IPV6 in hosts in: /etc/nginx/conf.d
2025-09-26 07:39:06.637512+00:00- /etc/nginx/conf.d/default.conf
2025-09-26 07:39:06.643874+00:00- /etc/nginx/conf.d/include/ssl-ciphers.conf
2025-09-26 07:39:06.649704+00:00- /etc/nginx/conf.d/include/block-exploits.conf
2025-09-26 07:39:06.655869+00:00- /etc/nginx/conf.d/include/ip_ranges.conf
2025-09-26 07:39:06.661233+00:00- /etc/nginx/conf.d/include/proxy.conf
2025-09-26 07:39:06.667259+00:00- /etc/nginx/conf.d/include/force-ssl.conf
2025-09-26 07:39:06.672977+00:00- /etc/nginx/conf.d/include/ssl-cache-stream.conf
2025-09-26 07:39:06.678163+00:00- /etc/nginx/conf.d/include/assets.conf
2025-09-26 07:39:06.683851+00:00- /etc/nginx/conf.d/include/ssl-cache.conf
2025-09-26 07:39:06.689121+00:00- /etc/nginx/conf.d/include/log.conf
2025-09-26 07:39:06.694979+00:00- /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
2025-09-26 07:39:06.700663+00:00- /etc/nginx/conf.d/include/resolvers.conf
2025-09-26 07:39:06.705763+00:00- /etc/nginx/conf.d/production.conf
2025-09-26 07:39:06.729263+00:00Enabling IPV6 in hosts in: /data/nginx
2025-09-26 07:39:06.729348+00:00- /data/nginx/proxy_host/7.conf
2025-09-26 07:39:06.734630+00:00- /data/nginx/proxy_host/2.conf
2025-09-26 07:39:06.740210+00:00- /data/nginx/proxy_host/6.conf
2025-09-26 07:39:06.745504+00:00- /data/nginx/proxy_host/4.conf
2025-09-26 07:39:06.750757+00:00- /data/nginx/proxy_host/8.conf
2025-09-26 07:39:06.756026+00:00- /data/nginx/proxy_host/9.conf
2025-09-26 07:39:06.761345+00:00- /data/nginx/proxy_host/1.conf
2025-09-26 07:39:06.766564+00:00- /data/nginx/proxy_host/5.conf
2025-09-26 07:39:06.776877+00:00�[1;34m❯ �[1;36mDocker secrets ...�[0m
2025-09-26 07:39:06.798823+00:002025-09-26T07:39:06.798823038Z
2025-09-26 07:39:06.798922+00:00-------------------------------------
2025-09-26 07:39:06.798986+00:00_   _ ____  __  __
2025-09-26 07:39:06.799017+00:00| \ | |  _ \|  \/  |
2025-09-26 07:39:06.799043+00:00|  \| | |_) | |\/| |
2025-09-26 07:39:06.799068+00:00| |\  |  __/| |  | |
2025-09-26 07:39:06.799092+00:00|_| \_|_|   |_|  |_|
2025-09-26 07:39:06.799119+00:00-------------------------------------
2025-09-26 07:39:06.799160+00:00User:  npm PUID:1000 ID:1000 GROUP:1000
2025-09-26 07:39:06.799187+00:00Group: npm PGID:1000 ID:1000
2025-09-26 07:39:06.799212+00:00-------------------------------------
2025-09-26 07:39:06.799237+00:002025-09-26T07:39:06.799237135Z
2025-09-26 07:39:06.816283+00:00�[1;34m❯ �[1;36mStarting nginx ...�[0m
2025-09-26 07:39:06.816858+00:00�[1;34m❯ �[1;36mStarting backend ...�[0m
2025-09-26 07:39:06.830629+00:00nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:4
2025-09-26 07:39:06.943000+00:00[9/26/2025] [9:39:06 AM] [Global   ] › ℹ  info      Using Sqlite: /data/database.sqlite
2025-09-26 07:39:07.384193+00:00[9/26/2025] [9:39:07 AM] [Migrate  ] › ℹ  info      Current database version: none
2025-09-26 07:39:07.485609+00:00[9/26/2025] [9:39:07 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
2025-09-26 07:39:07.486244+00:00[9/26/2025] [9:39:07 AM] [Global   ] › ⬤  debug     CMD: logrotate /etc/logrotate.d/nginx-proxy-manager
2025-09-26 07:39:07.592421+00:00[9/26/2025] [9:39:07 AM] [Setup    ] › ℹ  info      Logrotate completed.
2025-09-26 07:39:07.666016+00:00[9/26/2025] [9:39:07 AM] [Global   ] › ℹ  info      IP Ranges fetch is enabled
2025-09-26 07:39:07.666265+00:00[9/26/2025] [9:39:07 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
2025-09-26 07:39:07.666435+00:00[9/26/2025] [9:39:07 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
2025-09-26 07:39:07.827333+00:00[9/26/2025] [9:39:07 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
2025-09-26 07:39:07.935753+00:00[9/26/2025] [9:39:07 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
2025-09-26 07:39:07.980517+00:00[9/26/2025] [9:39:07 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
2025-09-26 07:39:07.980636+00:00[9/26/2025] [9:39:07 AM] [SSL      ] › ℹ  info      Renewing SSL certs expiring within 30 days ...
2025-09-26 07:39:07.982533+00:00[9/26/2025] [9:39:07 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
2025-09-26 07:39:07.984848+00:00[9/26/2025] [9:39:07 AM] [Global   ] › ℹ  info      Backend PID 443 listening on port 3000 ...
2025-09-26 07:39:07.985992+00:00[9/26/2025] [9:39:07 AM] [SSL      ] › ℹ  info      Completed SSL cert renew process

It took the service ~24 mins to start in my environment.

Nginx Proxy Manager v2.12.6 (runs as app on TrueNAS 25.04)

I observed the same behaviour before, too. I suspect that the number of hosts affects the duration.

2025-10-02 14:04:32.752068+00:00- /opt/certbot/lib/python3.11/site-packages ...
2025-10-02 14:27:12.164866+00:00DONE

Fixed by created my own docker-compose.yml file for npm. Truenas apps are slow.

Hello @alexandrecorroy, what modification did you make in the docker-compose.yml?

same issue if you have any pointers

@alexandrecorroy could you please add the modification you did. Having the same issue here.

create dataset with app permission example : /mnt/ssd/proxy

Create 2 files in folder :

.env

TZ=Europe/Paris
NPM_IMAGE=jc21/nginx-proxy-manager:latest
NPM_UI_PORT=30020   # WebUI (or port 81)
NPM_HTTP_PORT=30021 # HTTP (or port 80)
NPM_HTTPS_PORT=30022 # HTTPS (or port 443)
NPM_DATA=/mnt/ssd/proxy # change with another mount volume folder
NPM_LETSENCRYPT=/mnt/ssd/proxy # change with another mount volume folder

docker-compose.yml

services:
  npm:
    image: ${NPM_IMAGE}
    container_name: npm
    restart: always
    privileged: false
    platform: linux/amd64
    security_opt:
      - no-new-privileges:true
    cap_add:
      - CHOWN
      - DAC_OVERRIDE
      - FOWNER
      - SETGID
      - SETUID
    cap_drop:
      - ALL

    environment:
      TZ: ${TZ}
      DB_SQLITE_FILE: /data/database.sqlite

    extra_hosts:
      - "host.docker.internal:host-gateway"

    ports:
      - "${NPM_UI_PORT}:81"
      - "${NPM_HTTP_PORT}:80"
      - "${NPM_HTTPS_PORT}:443"

    healthcheck:
      test: [ "CMD", "/bin/check-health" ]
      interval: 30s
      timeout: 5s
      retries: 5
      start_period: 15s

    volumes:
      - ${NPM_DATA}:/data
      - ${NPM_LETSENCRYPT}:/etc/letsencrypt

run :

docker compose up -d