starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #2533] No relevant user found #1770

New issue
Closed
opened 2026-02-26 07:32:23 +03:00 by kerem · 2 comments
kerem commented 2026-02-26 07:32:23 +03:00
Owner
Copy link

Originally created by @warlordattack on GitHub (Jan 10, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2533

Hello beautiful people,

I use this docker image : jc21/nginx-proxy-manager:latest 
NPM version : v2.9.19
Data stored in mariadb.

PROBLEM : 
Today i can not connect to NPM GUI. 
First when login page loads i see this message in the logs : [1/10/2023] [8:38:46 PM] [Express  ] › ⚠  warning   invalid signature
Next when connecting with my usual credentials (mail + password + Sign in button) a have this red message : No relevant user found.
On the mariadb side i don't see NPM mysql user process connected.
In the mysql user table i see my user i usually use to connect.
Looks like NPM is not connected to mariadb ? But i don't see anything related to mariadb connexion in the logs.

TRYED : 
-serched "No relevant user found" issues here
-reapired mysql database 
-tested mysql connexion via HeidiSQL and NPM mysql credentials 
-had * character inside NPM mysql password : changed to numbers and letters without * character
-verified mysql container IP
-recreated/restarted NPM and mariadb container 
-cleared all unused docker images
-restored docker appdata folder from yesturday
-restored synology nas config from yesturday
-verified synology nas firewall and router config
-disabled synology nas firewall and ip block list
-restarted synology nas
-verified internet box config
-verified NPM admin mail and password : no special caracters in mail password only lowercase letters and numbers
-cleared chrome cache
(nothing helped)
Interestingly all cloudflare+npm redirections work well except NPM url witch gives Bad getaway 502 error from web
WEB : https://my-npm-url.mydomain.ovh -> bad getaway 502 error
LAN : http://192.168.1.100:18581/login -> connexion page -> No relevant user found

DOCKER COMPOSE : 

version: '3'
services:
  srv_npm:
    container_name: ${C_NPM}
    image: ${C_NPM_IMG}
    restart: ${C_ALL_RESTART}
    hostname: ${C_NPM_HOST}
    ports:
      - ${C_NPM_80}:80
      - ${C_NPM_443}:443
      - ${C_NPM_81}:81
    volumes:
      - ${REP_APPDATA}/${C_NPM}/data:/data
      - ${REP_APPDATA}/${C_NPM}/letsencrypt:/etc/letsencrypt
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - UMASK=${UMASK}
      - TZ=${TZ}
      - DISABLE_IPV6=true
      - DB_MYSQL_HOST=${C_MDB_HOST}
      - DB_MYSQL_PORT=${C_MDB_3306}
      - DB_MYSQL_NAME=${C_MYSQL_NPM_DB}
      - DB_MYSQL_USER=${C_MYSQL_NPM_USER}
      - DB_MYSQL_PASSWORD=${C_MYSQL_NPM_PWD}
    labels:
      - 'com.centurylinklabs.watchtower.enable=${WATCHTOWER_LABEL_ENABLE}'
    networks:
      - web
networks: 
  web: 
    external: true


LOGS : 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01_perms.sh: executing... 
Changing ownership of /data/logs to 0:0
[cont-init.d] 01_perms.sh: exited 0.
[cont-init.d] 01_s6-secret-init.sh: executing... 
[cont-init.d] 01_s6-secret-init.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/default.conf
  ❯ /etc/nginx/conf.d/include/assets.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
  ❯ /etc/nginx/conf.d/include/proxy.conf
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
  ❯ /etc/nginx/conf.d/production.conf
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /data/nginx
  ❯ /data/nginx/proxy_host/3.conf
  ❯ /data/nginx/proxy_host/4.conf
  ❯ /data/nginx/proxy_host/63.conf
  ❯ /data/nginx/proxy_host/6.conf
  ❯ /data/nginx/proxy_host/54.conf
  ❯ /data/nginx/proxy_host/19.conf
  ❯ /data/nginx/proxy_host/57.conf
  ❯ /data/nginx/proxy_host/8.conf
  ❯ /data/nginx/proxy_host/48.conf
  ❯ /data/nginx/proxy_host/81.conf
  ❯ /data/nginx/proxy_host/49.conf
  ❯ /data/nginx/proxy_host/83.conf
  ❯ /data/nginx/proxy_host/84.conf
  ❯ /data/nginx/proxy_host/33.conf
  ❯ /data/nginx/proxy_host/29.conf
  ❯ /data/nginx/proxy_host/94.conf
  ❯ /data/nginx/proxy_host/25.conf
  ❯ /data/nginx/proxy_host/95.conf
  ❯ /data/nginx/proxy_host/20.conf
  ❯ /data/nginx/proxy_host/32.conf
  ❯ /data/nginx/proxy_host/18.conf
  ❯ /data/nginx/proxy_host/15.conf
  ❯ /data/nginx/proxy_host/104.conf
  ❯ /data/nginx/proxy_host/30.conf
  ❯ /data/nginx/proxy_host/38.conf
  ❯ /data/nginx/proxy_host/60.conf
  ❯ /data/nginx/proxy_host/85.conf
  ❯ /data/nginx/proxy_host/16.conf
  ❯ /data/nginx/proxy_host/24.conf
  ❯ /data/nginx/proxy_host/42.conf
  ❯ /data/nginx/proxy_host/22.conf
  ❯ /data/nginx/proxy_host/82.conf
  ❯ /data/nginx/proxy_host/23.conf
  ❯ /data/nginx/proxy_host/92.conf
  ❯ /data/nginx/proxy_host/21.conf
  ❯ /data/nginx/proxy_host/45.conf
  ❯ /data/nginx/proxy_host/96.conf
  ❯ /data/nginx/proxy_host/37.conf
  ❯ /data/nginx/proxy_host/90.conf
  ❯ /data/nginx/proxy_host/67.conf
  ❯ /data/nginx/proxy_host/70.conf
  ❯ /data/nginx/proxy_host/52.conf
  ❯ /data/nginx/proxy_host/51.conf
  ❯ /data/nginx/proxy_host/64.conf
  ❯ /data/nginx/proxy_host/55.conf
  ❯ /data/nginx/proxy_host/77.conf
  ❯ /data/nginx/proxy_host/76.conf
  ❯ /data/nginx/proxy_host/91.conf
  ❯ /data/nginx/proxy_host/99.conf
  ❯ /data/nginx/proxy_host/97.conf
  ❯ /data/nginx/proxy_host/71.conf
  ❯ /data/nginx/proxy_host/75.conf
  ❯ /data/nginx/proxy_host/36.conf
  ❯ /data/nginx/proxy_host/35.conf
  ❯ /data/nginx/proxy_host/106.conf
  ❯ /data/nginx/proxy_host/107.conf
  ❯ /data/nginx/proxy_host/108.conf
  ❯ /data/nginx/proxy_host/105.conf
  ❯ /data/nginx/proxy_host/109.conf
  ❯ /data/nginx/proxy_host/110.conf
  ❯ /data/nginx/proxy_host/34.conf
  ❯ /data/nginx/proxy_host/111.conf
[1/10/2023] [8:36:01 PM] [Global   ] › ℹ  info      Generating MySQL knex configuration from environment variables
[1/10/2023] [8:36:01 PM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
[1/10/2023] [8:36:04 PM] [Migrate  ] › ℹ  info      Current database version: 20211108145214
[1/10/2023] [8:36:04 PM] [Setup    ] › ℹ  info      Creating a new JWT key pair...
[1/10/2023] [8:36:11 PM] [Setup    ] › ℹ  info      Wrote JWT key pair to config file: /app/config/production.json
[1/10/2023] [8:36:11 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[1/10/2023] [8:36:11 PM] [Setup    ] › ℹ  info      Logrotate completed.
[1/10/2023] [8:36:11 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[1/10/2023] [8:36:11 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[1/10/2023] [8:36:11 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[1/10/2023] [8:36:11 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[1/10/2023] [8:36:12 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[1/10/2023] [8:36:12 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[1/10/2023] [8:36:12 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[1/10/2023] [8:36:12 PM] [Global   ] › ℹ  info      Backend PID 238 listening on port 3000 ...
[1/10/2023] [8:36:14 PM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation  
Renewal configuration file /etc/letsencrypt/renewal/npm-2.conf (cert: npm-2) produced an unexpected error: 'Namespace' object has no attribute 'dns_cloudflare_credentials'. Skipping.
0 renew failure(s), 1 parse failure(s)
    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Socket.<anonymous> (node:internal/child_process:458:11)
    at Socket.emit (node:events:513:28)
    at Pipe.<anonymous> (node:net:301:12)
[1/10/2023] [8:38:46 PM] [Express  ] › ⚠  warning   invalid signature

Help please,

Best regards :)

2023-01-10_205408

2023-01-10_210954

Originally created by @warlordattack on GitHub (Jan 10, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2533 ``` Hello beautiful people, I use this docker image : jc21/nginx-proxy-manager:latest NPM version : v2.9.19 Data stored in mariadb. PROBLEM : Today i can not connect to NPM GUI. First when login page loads i see this message in the logs : [1/10/2023] [8:38:46 PM] [Express ] › ⚠ warning invalid signature Next when connecting with my usual credentials (mail + password + Sign in button) a have this red message : No relevant user found. On the mariadb side i don't see NPM mysql user process connected. In the mysql user table i see my user i usually use to connect. Looks like NPM is not connected to mariadb ? But i don't see anything related to mariadb connexion in the logs. TRYED : -serched "No relevant user found" issues here -reapired mysql database -tested mysql connexion via HeidiSQL and NPM mysql credentials -had * character inside NPM mysql password : changed to numbers and letters without * character -verified mysql container IP -recreated/restarted NPM and mariadb container -cleared all unused docker images -restored docker appdata folder from yesturday -restored synology nas config from yesturday -verified synology nas firewall and router config -disabled synology nas firewall and ip block list -restarted synology nas -verified internet box config -verified NPM admin mail and password : no special caracters in mail password only lowercase letters and numbers -cleared chrome cache (nothing helped) Interestingly all cloudflare+npm redirections work well except NPM url witch gives Bad getaway 502 error from web WEB : https://my-npm-url.mydomain.ovh -> bad getaway 502 error LAN : http://192.168.1.100:18581/login -> connexion page -> No relevant user found DOCKER COMPOSE : version: '3' services: srv_npm: container_name: ${C_NPM} image: ${C_NPM_IMG} restart: ${C_ALL_RESTART} hostname: ${C_NPM_HOST} ports: - ${C_NPM_80}:80 - ${C_NPM_443}:443 - ${C_NPM_81}:81 volumes: - ${REP_APPDATA}/${C_NPM}/data:/data - ${REP_APPDATA}/${C_NPM}/letsencrypt:/etc/letsencrypt environment: - PUID=${PUID} - PGID=${PGID} - UMASK=${UMASK} - TZ=${TZ} - DISABLE_IPV6=true - DB_MYSQL_HOST=${C_MDB_HOST} - DB_MYSQL_PORT=${C_MDB_3306} - DB_MYSQL_NAME=${C_MYSQL_NPM_DB} - DB_MYSQL_USER=${C_MYSQL_NPM_USER} - DB_MYSQL_PASSWORD=${C_MYSQL_NPM_PWD} labels: - 'com.centurylinklabs.watchtower.enable=${WATCHTOWER_LABEL_ENABLE}' networks: - web networks: web: external: true LOGS : [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01_perms.sh: executing... Changing ownership of /data/logs to 0:0 [cont-init.d] 01_perms.sh: exited 0. [cont-init.d] 01_s6-secret-init.sh: executing... [cont-init.d] 01_s6-secret-init.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Disabling IPV6 in hosts ❯ Disabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/default.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ /etc/nginx/conf.d/production.conf Disabling IPV6 in hosts ❯ Disabling IPV6 in hosts: /data/nginx ❯ /data/nginx/proxy_host/3.conf ❯ /data/nginx/proxy_host/4.conf ❯ /data/nginx/proxy_host/63.conf ❯ /data/nginx/proxy_host/6.conf ❯ /data/nginx/proxy_host/54.conf ❯ /data/nginx/proxy_host/19.conf ❯ /data/nginx/proxy_host/57.conf ❯ /data/nginx/proxy_host/8.conf ❯ /data/nginx/proxy_host/48.conf ❯ /data/nginx/proxy_host/81.conf ❯ /data/nginx/proxy_host/49.conf ❯ /data/nginx/proxy_host/83.conf ❯ /data/nginx/proxy_host/84.conf ❯ /data/nginx/proxy_host/33.conf ❯ /data/nginx/proxy_host/29.conf ❯ /data/nginx/proxy_host/94.conf ❯ /data/nginx/proxy_host/25.conf ❯ /data/nginx/proxy_host/95.conf ❯ /data/nginx/proxy_host/20.conf ❯ /data/nginx/proxy_host/32.conf ❯ /data/nginx/proxy_host/18.conf ❯ /data/nginx/proxy_host/15.conf ❯ /data/nginx/proxy_host/104.conf ❯ /data/nginx/proxy_host/30.conf ❯ /data/nginx/proxy_host/38.conf ❯ /data/nginx/proxy_host/60.conf ❯ /data/nginx/proxy_host/85.conf ❯ /data/nginx/proxy_host/16.conf ❯ /data/nginx/proxy_host/24.conf ❯ /data/nginx/proxy_host/42.conf ❯ /data/nginx/proxy_host/22.conf ❯ /data/nginx/proxy_host/82.conf ❯ /data/nginx/proxy_host/23.conf ❯ /data/nginx/proxy_host/92.conf ❯ /data/nginx/proxy_host/21.conf ❯ /data/nginx/proxy_host/45.conf ❯ /data/nginx/proxy_host/96.conf ❯ /data/nginx/proxy_host/37.conf ❯ /data/nginx/proxy_host/90.conf ❯ /data/nginx/proxy_host/67.conf ❯ /data/nginx/proxy_host/70.conf ❯ /data/nginx/proxy_host/52.conf ❯ /data/nginx/proxy_host/51.conf ❯ /data/nginx/proxy_host/64.conf ❯ /data/nginx/proxy_host/55.conf ❯ /data/nginx/proxy_host/77.conf ❯ /data/nginx/proxy_host/76.conf ❯ /data/nginx/proxy_host/91.conf ❯ /data/nginx/proxy_host/99.conf ❯ /data/nginx/proxy_host/97.conf ❯ /data/nginx/proxy_host/71.conf ❯ /data/nginx/proxy_host/75.conf ❯ /data/nginx/proxy_host/36.conf ❯ /data/nginx/proxy_host/35.conf ❯ /data/nginx/proxy_host/106.conf ❯ /data/nginx/proxy_host/107.conf ❯ /data/nginx/proxy_host/108.conf ❯ /data/nginx/proxy_host/105.conf ❯ /data/nginx/proxy_host/109.conf ❯ /data/nginx/proxy_host/110.conf ❯ /data/nginx/proxy_host/34.conf ❯ /data/nginx/proxy_host/111.conf [1/10/2023] [8:36:01 PM] [Global ] › ℹ info Generating MySQL knex configuration from environment variables [1/10/2023] [8:36:01 PM] [Global ] › ⬤ debug Wrote db configuration to config file: ./config/production.json [1/10/2023] [8:36:04 PM] [Migrate ] › ℹ info Current database version: 20211108145214 [1/10/2023] [8:36:04 PM] [Setup ] › ℹ info Creating a new JWT key pair... [1/10/2023] [8:36:11 PM] [Setup ] › ℹ info Wrote JWT key pair to config file: /app/config/production.json [1/10/2023] [8:36:11 PM] [Setup ] › ℹ info Logrotate Timer initialized [1/10/2023] [8:36:11 PM] [Setup ] › ℹ info Logrotate completed. [1/10/2023] [8:36:11 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [1/10/2023] [8:36:11 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [1/10/2023] [8:36:11 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [1/10/2023] [8:36:11 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [1/10/2023] [8:36:12 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [1/10/2023] [8:36:12 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [1/10/2023] [8:36:12 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [1/10/2023] [8:36:12 PM] [Global ] › ℹ info Backend PID 238 listening on port 3000 ... [1/10/2023] [8:36:14 PM] [SSL ] › ✖ error Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation Renewal configuration file /etc/letsencrypt/renewal/npm-2.conf (cert: npm-2) produced an unexpected error: 'Namespace' object has no attribute 'dns_cloudflare_credentials'. Skipping. 0 renew failure(s), 1 parse failure(s) at ChildProcess.exithandler (node:child_process:402:12) at ChildProcess.emit (node:events:513:28) at maybeClose (node:internal/child_process:1100:16) at Socket.<anonymous> (node:internal/child_process:458:11) at Socket.emit (node:events:513:28) at Pipe.<anonymous> (node:net:301:12) [1/10/2023] [8:38:46 PM] [Express ] › ⚠ warning invalid signature Help please, Best regards :) ``` ![2023-01-10_205408](https://user-images.githubusercontent.com/3226486/211650591-8bc7ff49-c332-4151-99a9-9113b49a2c82.png) ![2023-01-10_210954](https://user-images.githubusercontent.com/3226486/211652155-a272f4c3-e3a1-4c89-8b6b-f39f76ff9dab.png)
kerem 2026-02-26 07:32:23 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 07:32:23 +03:00
Author
Owner
Copy link

@warlordattack commented on GitHub (Jan 11, 2023):

Because everything is stored into mariadb database, 
i renamed the appdata folder and started with new empty folder : 
    volumes:
      - ${REP_APPDATA}/${C_NPM}/data:/data
      - ${REP_APPDATA}/${C_NPM}/letsencrypt:/etc/letsencrypt

After recreating container same situayion, user not recognized, 
so i tested with the NPM default user : 
Manager username: admin@example.com. Default Proxy Manager password: changeme.

And guess what, i am connected now on an empty NPM : no data.
So it is definitly mariadb database connexion problem.
In the log below i see : 
[1/11/2023] [11:43:45 AM] [Global   ] › ℹ  info      Generating MySQL knex configuration from environment variables
[1/11/2023] [11:43:45 AM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
[1/11/2023] [11:43:47 AM] [Migrate  ] › ℹ  info      Current database version: 20211108145214

Looks like he generates mysql connexion file, 
but not connected to mysql, i suppose it uses new empty sqlite database instead.

FULL LOG : 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01_perms.sh: executing... 
Changing ownership of /data/logs to 0:0
[cont-init.d] 01_perms.sh: exited 0.
[cont-init.d] 01_s6-secret-init.sh: executing... 
[cont-init.d] 01_s6-secret-init.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Generating dummy SSL certificate...
Generating a RSA private key
........+++++
......................................................................+++++
writing new private key to '/data/nginx/dummykey.pem'
-----
Complete
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/default.conf
  ❯ /etc/nginx/conf.d/include/assets.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
  ❯ /etc/nginx/conf.d/include/proxy.conf
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
  ❯ /etc/nginx/conf.d/production.conf
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /data/nginx
[1/11/2023] [11:43:45 AM] [Global   ] › ℹ  info      Generating MySQL knex configuration from environment variables
[1/11/2023] [11:43:45 AM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
[1/11/2023] [11:43:47 AM] [Migrate  ] › ℹ  info      Current database version: 20211108145214
[1/11/2023] [11:43:48 AM] [Setup    ] › ℹ  info      Creating a new JWT key pair...
[1/11/2023] [11:43:52 AM] [Setup    ] › ℹ  info      Wrote JWT key pair to config file: /app/config/production.json
[1/11/2023] [11:43:52 AM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[1/11/2023] [11:43:53 AM] [Setup    ] › ℹ  info      Logrotate completed.
[1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[1/11/2023] [11:43:53 AM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[1/11/2023] [11:43:53 AM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[1/11/2023] [11:43:53 AM] [Global   ] › ℹ  info      Backend PID 242 listening on port 3000 ...
[1/11/2023] [11:43:56 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[1/11/2023] [11:43:56 AM] [SSL      ] › ℹ  info      Renew Complete
[1/11/2023] [11:44:38 AM] [Express  ] › ⚠  warning   invalid signature
`QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0
`QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0
QueryBuilder#omit is deprecated. This method will be removed in version 3.0
Model#$omit is deprected and will be removed in 3.0.
<!-- gh-comment-id:1378572640 --> @warlordattack commented on GitHub (Jan 11, 2023): ``` Because everything is stored into mariadb database, i renamed the appdata folder and started with new empty folder : volumes: - ${REP_APPDATA}/${C_NPM}/data:/data - ${REP_APPDATA}/${C_NPM}/letsencrypt:/etc/letsencrypt After recreating container same situayion, user not recognized, so i tested with the NPM default user : Manager username: admin@example.com. Default Proxy Manager password: changeme. And guess what, i am connected now on an empty NPM : no data. So it is definitly mariadb database connexion problem. In the log below i see : [1/11/2023] [11:43:45 AM] [Global ] › ℹ info Generating MySQL knex configuration from environment variables [1/11/2023] [11:43:45 AM] [Global ] › ⬤ debug Wrote db configuration to config file: ./config/production.json [1/11/2023] [11:43:47 AM] [Migrate ] › ℹ info Current database version: 20211108145214 Looks like he generates mysql connexion file, but not connected to mysql, i suppose it uses new empty sqlite database instead. FULL LOG : [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01_perms.sh: executing... Changing ownership of /data/logs to 0:0 [cont-init.d] 01_perms.sh: exited 0. [cont-init.d] 01_s6-secret-init.sh: executing... [cont-init.d] 01_s6-secret-init.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Generating dummy SSL certificate... Generating a RSA private key ........+++++ ......................................................................+++++ writing new private key to '/data/nginx/dummykey.pem' ----- Complete Disabling IPV6 in hosts ❯ Disabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/default.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ /etc/nginx/conf.d/production.conf Disabling IPV6 in hosts ❯ Disabling IPV6 in hosts: /data/nginx [1/11/2023] [11:43:45 AM] [Global ] › ℹ info Generating MySQL knex configuration from environment variables [1/11/2023] [11:43:45 AM] [Global ] › ⬤ debug Wrote db configuration to config file: ./config/production.json [1/11/2023] [11:43:47 AM] [Migrate ] › ℹ info Current database version: 20211108145214 [1/11/2023] [11:43:48 AM] [Setup ] › ℹ info Creating a new JWT key pair... [1/11/2023] [11:43:52 AM] [Setup ] › ℹ info Wrote JWT key pair to config file: /app/config/production.json [1/11/2023] [11:43:52 AM] [Setup ] › ℹ info Logrotate Timer initialized [1/11/2023] [11:43:53 AM] [Setup ] › ℹ info Logrotate completed. [1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [1/11/2023] [11:43:53 AM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [1/11/2023] [11:43:53 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [1/11/2023] [11:43:53 AM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [1/11/2023] [11:43:53 AM] [Global ] › ℹ info Backend PID 242 listening on port 3000 ... [1/11/2023] [11:43:56 AM] [Nginx ] › ℹ info Reloading Nginx [1/11/2023] [11:43:56 AM] [SSL ] › ℹ info Renew Complete [1/11/2023] [11:44:38 AM] [Express ] › ⚠ warning invalid signature `QueryBuilder#allowEager` method is deprecated. You should use `allowGraph` instead. `allowEager` method will be removed in 3.0 `QueryBuilder#eager` method is deprecated. You should use the `withGraphFetched` method instead. `eager` method will be removed in 3.0 QueryBuilder#omit is deprecated. This method will be removed in version 3.0 Model#$omit is deprected and will be removed in 3.0. ```
kerem commented 2026-02-26 07:32:23 +03:00
Author
Owner
Copy link

@warlordattack commented on GitHub (Jan 11, 2023):

Problem solved : 
I mapped /app/config/ inside docker compose file to check 
/app/config/production.json file, 
and found there wrong mysql connexion variables values 
that connect to my Ombi database instead of NPM database !

      - DB_MYSQL_NAME=${C_MYSQL_NPM_DB}
      - DB_MYSQL_USER=${C_MYSQL_NPM_USER}
      - DB_MYSQL_PASSWORD=${C_MYSQL_NPM_PWD}

when y tryed to connect ombi to mariadb, i copy-pasted NPM connexion variables,
and filled values for ombi connexion, 
but forgot to rename new variables for ombi : 

C_MYSQL_NPM_DB should have been renamed to C_MYSQL_OMBI_DB ... etc ...

So i had C_MYSQL_NPM_DB twice in my .env file with Ombi connexion values wich overcharged NPM connexion values :

# npm
C_MYSQL_NPM_DB=npm_db
C_MYSQL_NPM_USER=npm user
C_MYSQL_NPM_PWD=npm pwd
# ombi
C_MYSQL_NPM_DB=ombi_db
C_MYSQL_NPM_USER=ombi user
C_MYSQL_NPM_PWD=ombi pwd

So my NPM connected to Ombi database, created new empty tables, and started as new empty install with default user.
After renaming variables in the .env file and cleaning the mess in the Ombi database, 
recreated container, and everything back to normal.

Aditionally i had 502 error because i changed from jlesage to jc21 image and not same ports used with these images.
Corrected this in the NPM proxy host config.

:)
<!-- gh-comment-id:1378624906 --> @warlordattack commented on GitHub (Jan 11, 2023): ``` Problem solved : I mapped /app/config/ inside docker compose file to check /app/config/production.json file, and found there wrong mysql connexion variables values that connect to my Ombi database instead of NPM database ! - DB_MYSQL_NAME=${C_MYSQL_NPM_DB} - DB_MYSQL_USER=${C_MYSQL_NPM_USER} - DB_MYSQL_PASSWORD=${C_MYSQL_NPM_PWD} when y tryed to connect ombi to mariadb, i copy-pasted NPM connexion variables, and filled values for ombi connexion, but forgot to rename new variables for ombi : C_MYSQL_NPM_DB should have been renamed to C_MYSQL_OMBI_DB ... etc ... So i had C_MYSQL_NPM_DB twice in my .env file with Ombi connexion values wich overcharged NPM connexion values : # npm C_MYSQL_NPM_DB=npm_db C_MYSQL_NPM_USER=npm user C_MYSQL_NPM_PWD=npm pwd # ombi C_MYSQL_NPM_DB=ombi_db C_MYSQL_NPM_USER=ombi user C_MYSQL_NPM_PWD=ombi pwd So my NPM connected to Ombi database, created new empty tables, and started as new empty install with default user. After renaming variables in the .env file and cleaning the mess in the Ombi database, recreated container, and everything back to normal. Aditionally i had 502 error because i changed from jlesage to jc21 image and not same ports used with these images. Corrected this in the NPM proxy host config. :) ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
dependabot/npm_and_yarn/backend/liquidjs-10.25.7
dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987
dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41
dependabot/npm_and_yarn/backend/basic-ftp-5.3.0
dependabot/npm_and_yarn/test/follow-redirects-1.16.0
dependabot/npm_and_yarn/test/axios-1.15.0
dependabot/npm_and_yarn/frontend/lodash-4.18.1
dependabot/npm_and_yarn/backend/lodash-4.18.1
dependabot/npm_and_yarn/test/lodash-4.18.1
dependabot/npm_and_yarn/frontend/vite-7.3.2
dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21
dependabot/npm_and_yarn/frontend/lodash-es-4.18.1
dependabot/npm_and_yarn/frontend/happy-dom-20.8.9
dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0
dependabot/npm_and_yarn/frontend/picomatch-4.0.4
dependabot/npm_and_yarn/backend/picomatch-2.3.2
dependabot/npm_and_yarn/frontend/yaml-1.10.3
dependabot/npm_and_yarn/test/flatted-3.4.2
dependabot/npm_and_yarn/test/tar-7.5.11
dependabot/npm_and_yarn/frontend/immutable-5.1.5
master
dependabot/npm_and_yarn/test/glob-10.5.0
dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1
dependabot/npm_and_yarn/test/form-data-4.0.4
v3-abandoned
bump-freedns
openidc
ssl-passthrough-hosts
static-content
v2.14.0
v2.13.7
v2.13.6
v2.13.5
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.3
v2.11.2
v2.11.1
v2.11.0
v2.10.4
v2.10.3
v2.10.2
v2.10.1
v2.10.0
v2.9.22
v2.9.21
v2.9.20
v2.9.19
v2.9.18
v2.9.17
v2.9.16
v2.9.15
v2.9.14
v2.9.13
v2.9.12
v2.9.11
v2.9.10
v2.9.9
v2.9.8
v2.9.7
v2.9.6
v2.9.5
v2.9.4
v2.9.3
v2.9.2
v2.9.1
v2.9.0
v2.8.1
v2.8.0
v2.7.3
v2.7.2
v2.7.1
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.2
v2.1.1
v2.1.0
2.0.14
2.0.13
2.0.12
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.0
v2.0.0
1.1.2
1.1.1
1.0.1
Labels
Clear labels   
awaiting feedback

   
bug

   
cannot reproduce

   
dns provider request

   
duplicate

   
enhancement

   
enhancement

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
need more info

   
no certbot plugin available

   
product-support

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
stale

   
troll

   
upstream issue

   
v2

   
v2

   
v2

   
v3

   
wontfix
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1770
No description provided.