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

[GH-ISSUE #1250] v2.9.5 Breaks my Setup and constantly get HHTP 502 BadGateway when I try to login #1014

New issue
Closed
opened 2026-02-26 06:35:25 +03:00 by kerem · 11 comments
kerem commented 2026-02-26 06:35:25 +03:00
Owner
Copy link

Originally created by @tucker19 on GitHub (Jul 20, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1250

Overnight Watchtower upgraded me from 2.9.4 to 2.9.5 and starting seeing container marked as Unhealthy within Portainarr. I see under health checks this error parse error: Invalid numeric literal at line 1, column 7 NOT OK and within my logs I just see these errors

ENV:
OS - Ubuntu 20.4 LTS
Docker - 2.4
DB - ghcr.io/linuxserver/mariadb

[7/20/2021] [12:04:18 PM] [Global   ] › ✖  error     Command failed: logrotate /etc/logrotate.d/nginx-proxy-manager
error: skipping "/data/logs/fallback_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
error: skipping "/data/logs/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.
Originally created by @tucker19 on GitHub (Jul 20, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1250 Overnight Watchtower upgraded me from 2.9.4 to 2.9.5 and starting seeing container marked as Unhealthy within Portainarr. I see under health checks this error `parse error: Invalid numeric literal at line 1, column 7 NOT OK` and within my logs I just see these errors ``` ENV: OS - Ubuntu 20.4 LTS Docker - 2.4 DB - ghcr.io/linuxserver/mariadb ``` ``` [7/20/2021] [12:04:18 PM] [Global ] › ✖ error Command failed: logrotate /etc/logrotate.d/nginx-proxy-manager error: skipping "/data/logs/fallback_access.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/data/logs/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. ```
kerem 2026-02-26 06:35:25 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Jul 20, 2021):

See https://github.com/jc21/nginx-proxy-manager/issues/1249. Could you check what the owner of your files is?

<!-- gh-comment-id:883567612 --> @chaptergy commented on GitHub (Jul 20, 2021): See https://github.com/jc21/nginx-proxy-manager/issues/1249. Could you check what the owner of your files is?
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@tucker19 commented on GitHub (Jul 20, 2021):

The directory for nginx-proxy-manager when I ls -al shows drwxrwxrwx and is owned by the user I am running Docker within. Same userID and groupID as I pass in within my compose

<!-- gh-comment-id:883709108 --> @tucker19 commented on GitHub (Jul 20, 2021): The directory for `nginx-proxy-manager` when I `ls -al` shows `drwxrwxrwx` and is owned by the user I am running Docker within. Same userID and groupID as I pass in within my compose
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Jul 20, 2021):

I mean the owner of the /data/logs directory inside the container.

But I am confused about your errors. From what I can see you are talking about three very separate issues. In the title you mention a 502 error when trying to log in, which sounds like a database issue where the database is not available.
Then there is the unhealty information, which I can't exactly say what causes the issue, if the database is unavailable it could be because of that.
The last thing is the logrotate not working, but this is not a breaking error at all, just a minor inconvenience. I was just talking about that last issue when asking about the owner of the folders.

Here's what you could check about the first two errors:

  1. The healthcheck just checks what the api returns. So open your NPM frontend and change the url path to /api, e.g. http://domain.com:81/api and see what that returns.
  2. Check the log of your database container, to see if it might have any errors which prevents the database from starting
  3. If none of the above seem to contain any relevant information, please post the full log of your npm container, as logrotate is not the culprit here.
<!-- gh-comment-id:883717398 --> @chaptergy commented on GitHub (Jul 20, 2021): I mean the owner of the `/data/logs` directory inside the container. But I am confused about your errors. From what I can see you are talking about three very separate issues. In the title you mention a 502 error when trying to log in, which sounds like a database issue where the database is not available. Then there is the unhealty information, which I can't exactly say what causes the issue, if the database is unavailable it could be because of that. The last thing is the logrotate not working, but this is not a breaking error at all, just a minor inconvenience. I was just talking about that last issue when asking about the owner of the folders. Here's what you could check about the first two errors: 1. The healthcheck just checks what the api returns. So open your NPM frontend and change the url path to `/api`, e.g. `http://domain.com:81/api` and see what that returns. 2. Check the log of your database container, to see if it might have any errors which prevents the database from starting 3. If none of the above seem to contain any relevant information, please post the full log of your npm container, as logrotate is not the culprit here.
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@PlasmatikSteak commented on GitHub (Jul 22, 2021):

When I navigate to http://domain.com:81/api i am greeted with a 502 Bad Gateway message

Only the npm_app_1 is marked as unhealthy.

CONTAINER ID   IMAGE          COMMAND             CREATED          STATUS                      PORTS                                                                                  NAMES
81f22a38d81a   f4f8dac2255c   "/init"             22 minutes ago   Up 22 minutes (unhealthy)   0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp   npm_app_1
848b2d4772ea   174fbfd81bac   "/scripts/run.sh"   24 minutes ago   Up 24 minutes               3306/tcp                                                                               npm_db_1
<!-- gh-comment-id:884681474 --> @PlasmatikSteak commented on GitHub (Jul 22, 2021): When I navigate to `http://domain.com:81/api` i am greeted with a `502 Bad Gateway` message Only the npm_app_1 is marked as unhealthy. ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 81f22a38d81a f4f8dac2255c "/init" 22 minutes ago Up 22 minutes (unhealthy) 0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp npm_app_1 848b2d4772ea 174fbfd81bac "/scripts/run.sh" 24 minutes ago Up 24 minutes 3306/tcp npm_db_1 ```
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Jul 22, 2021):

Hm, maybe it is related to the logrotate. Could one of you please try the following:

  1. Open a shell on the docker container through docker exec -ti <CONTAINER_ID> bash or portainer
  2. Install the nano text editor by running apt update && apt install nano -y
  3. Open the setup.js file by running nano /app/setup.js
  4. Scroll to the very bottom and you should find 
    const runLogrotate = async () => {
    await utils.exec('logrotate /etc/logrotate.d/nginx-proxy-manager');
    logger.info('Logrotate completed.');
};
  5. Replace it with 
    const runLogrotate = async () => {
    try {
        await utils.exec('logrotate /etc/logrotate.d/nginx-proxy-manager');
        logger.info('Logrotate completed.');
    } catch (e) { logger.warn(e) }
};

See if that solves the problem.

<!-- gh-comment-id:884732710 --> @chaptergy commented on GitHub (Jul 22, 2021): Hm, maybe it is related to the logrotate. Could one of you please try the following: 1. Open a shell on the docker container through `docker exec -ti <CONTAINER_ID> bash` or portainer 2. Install the nano text editor by running `apt update && apt install nano -y` 3. Open the `setup.js` file by running `nano /app/setup.js` 4. Scroll to the very bottom and you should find ```js const runLogrotate = async () => { await utils.exec('logrotate /etc/logrotate.d/nginx-proxy-manager'); logger.info('Logrotate completed.'); }; ``` 5. Replace it with ```js const runLogrotate = async () => { try { await utils.exec('logrotate /etc/logrotate.d/nginx-proxy-manager'); logger.info('Logrotate completed.'); } catch (e) { logger.warn(e) } }; ``` See if that solves the problem.
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@PlasmatikSteak commented on GitHub (Jul 22, 2021):

That did it!

The api does not return 502 Bad Gateway and the container is now marked as healthy :D

CONTAINER ID   IMAGE          COMMAND             CREATED       STATUS                        PORTS                                                                                  NAMES
81f22a38d81a   f4f8dac2255c   "/init"             6 hours ago   Up About a minute (healthy)   0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp   npm_app_1
848b2d4772ea   174fbfd81bac   "/scripts/run.sh"   6 hours ago   Up 6 hours                    3306/tcp                                                                               npm_db_1

Thank you so much!

<!-- gh-comment-id:884856636 --> @PlasmatikSteak commented on GitHub (Jul 22, 2021): That did it! The api does not return `502 Bad Gateway` and the container is now marked as healthy :D ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 81f22a38d81a f4f8dac2255c "/init" 6 hours ago Up About a minute (healthy) 0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp npm_app_1 848b2d4772ea 174fbfd81bac "/scripts/run.sh" 6 hours ago Up 6 hours 3306/tcp npm_db_1 ``` Thank you so much!
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@tucker19 commented on GitHub (Jul 22, 2021):

I will try this as well when I get some downtime from work. Crazy few days.

<!-- gh-comment-id:884899076 --> @tucker19 commented on GitHub (Jul 22, 2021): I will try this as well when I get some downtime from work. Crazy few days.
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@tucker19 commented on GitHub (Jul 22, 2021):

Hm, maybe it is related to the logrotate. Could one of you please try the following:

1. Open a shell on the docker container through `docker exec -ti <CONTAINER_ID> bash` or portainer

2. Install the nano text editor by running `apt update && apt install nano -y`

3. Open the `setup.js` file by running `nano /app/setup.js`

4. Scroll to the very bottom and you should find
   ```js
   const runLogrotate = async () => {
       await utils.exec('logrotate /etc/logrotate.d/nginx-proxy-manager');
       logger.info('Logrotate completed.');
   };
   ```

5. Replace it with
   ```js
   const runLogrotate = async () => {
       try {
           await utils.exec('logrotate /etc/logrotate.d/nginx-proxy-manager');
           logger.info('Logrotate completed.');
       } catch (e) { logger.warn(e) }
   };
   ```

See if that solves the problem.

I can confirm this fixes it on my Docker as well but I am seeing these messages now in Portainer

❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
  ❯ /etc/nginx/conf.d/include/assets.conf
  ❯ /etc/nginx/conf.d/include/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /etc/nginx/conf.d/include/proxy.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
  ❯ /etc/nginx/conf.d/production.conf
  ❯ /etc/nginx/conf.d/default.conf
❯ Enabling IPV6 in hosts: /data/nginx
[7/22/2021] [10:14:16 AM] [Global   ] › ✖  error     connect ECONNREFUSED 172.30.0.19:3307
[7/22/2021] [10:14:17 AM] [Global   ] › ✖  error     connect ECONNREFUSED 172.30.0.19:3307
[7/22/2021] [10:14:18 AM] [Global   ] › ✖  error     connect ECONNREFUSED 172.30.0.19:3307
[7/22/2021] [10:14:19 AM] [Global   ] › ✖  error     connect ECONNREFUSED 172.30.0.19:3307
[7/22/2021] [10:14:20 AM] [Global   ] › ✖  error     connect ECONNREFUSED 172.30.0.19:3307
[7/22/2021] [10:14:21 AM] [Global   ] › ✖  error     connect ECONNREFUSED 172.30.0.19:3307
[7/22/2021] [10:14:22 AM] [Global   ] › ✖  error     connect ECONNREFUSED 172.30.0.19:3307
[7/22/2021] [10:14:23 AM] [Global   ] › ✖  error     connect ECONNREFUSED 172.30.0.19:3307

I do have my ports mapped to 981:81 and then I try and do a <IP>:981/api it will redirect to <IP>:81/api and give me a HTTP 302. I still get the Bad Gateway when I just try and log in with the default admin@example.com and this is the initially setup of a new container.

<!-- gh-comment-id:884998991 --> @tucker19 commented on GitHub (Jul 22, 2021): > > > Hm, maybe it is related to the logrotate. Could one of you please try the following: > > 1. Open a shell on the docker container through `docker exec -ti <CONTAINER_ID> bash` or portainer > > 2. Install the nano text editor by running `apt update && apt install nano -y` > > 3. Open the `setup.js` file by running `nano /app/setup.js` > > 4. Scroll to the very bottom and you should find > ```js > const runLogrotate = async () => { > await utils.exec('logrotate /etc/logrotate.d/nginx-proxy-manager'); > logger.info('Logrotate completed.'); > }; > ``` > > 5. Replace it with > ```js > const runLogrotate = async () => { > try { > await utils.exec('logrotate /etc/logrotate.d/nginx-proxy-manager'); > logger.info('Logrotate completed.'); > } catch (e) { logger.warn(e) } > }; > ``` > > > See if that solves the problem. I can confirm this fixes it on my Docker as well but I am seeing these messages now in Portainer ``` ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ /etc/nginx/conf.d/production.conf ❯ /etc/nginx/conf.d/default.conf ❯ Enabling IPV6 in hosts: /data/nginx [7/22/2021] [10:14:16 AM] [Global ] › ✖ error connect ECONNREFUSED 172.30.0.19:3307 [7/22/2021] [10:14:17 AM] [Global ] › ✖ error connect ECONNREFUSED 172.30.0.19:3307 [7/22/2021] [10:14:18 AM] [Global ] › ✖ error connect ECONNREFUSED 172.30.0.19:3307 [7/22/2021] [10:14:19 AM] [Global ] › ✖ error connect ECONNREFUSED 172.30.0.19:3307 [7/22/2021] [10:14:20 AM] [Global ] › ✖ error connect ECONNREFUSED 172.30.0.19:3307 [7/22/2021] [10:14:21 AM] [Global ] › ✖ error connect ECONNREFUSED 172.30.0.19:3307 [7/22/2021] [10:14:22 AM] [Global ] › ✖ error connect ECONNREFUSED 172.30.0.19:3307 [7/22/2021] [10:14:23 AM] [Global ] › ✖ error connect ECONNREFUSED 172.30.0.19:3307 ``` I do have my ports mapped to `981:81` and then I try and do a `<IP>:981/api` it will redirect to `<IP>:81/api` and give me a HTTP 302. I still get the Bad Gateway when I just try and log in with the default `admin@example.com` and this is the initially setup of a new container.
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Jul 22, 2021):

Your remaining issue is definitely a database issue. The database does not respond. You need to check why your database is not running.

<!-- gh-comment-id:885078050 --> @chaptergy commented on GitHub (Jul 22, 2021): Your remaining issue is definitely a database issue. The database does not respond. You need to check why your database is not running.
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@tucker19 commented on GitHub (Jul 22, 2021):

Okay, thanks for that info. I suspected that.

<!-- gh-comment-id:885087130 --> @tucker19 commented on GitHub (Jul 22, 2021): Okay, thanks for that info. I suspected that.
kerem commented 2026-02-26 06:35:26 +03:00
Author
Owner
Copy link

@tucker19 commented on GitHub (Jul 22, 2021):

Your remaining issue is definitely a database issue. The database does not respond. You need to check why your database is not running.

Found my errors in db. I have confirmed all my stuff is working now. Thank you for all the help.

<!-- gh-comment-id:885132845 --> @tucker19 commented on GitHub (Jul 22, 2021): > > > Your remaining issue is definitely a database issue. The database does not respond. You need to check why your database is not running. Found my errors in db. I have confirmed all my stuff is working now. Thank you for all the help.
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#1014
No description provided.