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

[GH-ISSUE #1442] Unable to login #1119

New issue
Open
opened 2026-02-26 06:35:50 +03:00 by kerem · 21 comments
kerem commented 2026-02-26 06:35:50 +03:00
Owner
Copy link

Originally created by @Marki-dev on GitHub (Sep 29, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1442

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
    • Yes
  • Are you sure you're not using someone else's docker image?
    • Yes
  • Have you searched for similar issues (both open and closed)?
    • Yes

Describe the bug

This is the second time it has happened to me, but i try to log into NPM ant it takes forever then (if) it lets me in, none of my proxies load, If I check the console i get this
[9/29/2021] [7:17:17 PM] [Express ] › ⚠ warning Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?

Nginx Proxy Manager Version

2.9.4

To Reproduce
Steps to reproduce the behavior:
Unable to show steps for reproduction as It happens randomly

Expected behavior

I should be allowed to login and see my stuff

Screenshots

https://thykeis.gay/i/aB8QcLlKQf

Operating System

Docker on Debian 10

Additional context

Originally created by @Marki-dev on GitHub (Sep 29, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1442 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** <!-- A clear and concise description of what the bug is. --> This is the second time it has happened to me, but i try to log into NPM ant it takes forever then (if) it lets me in, none of my proxies load, If I check the console i get this ` [9/29/2021] [7:17:17 PM] [Express ] › ⚠ warning Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?` **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? --> 2.9.4 **To Reproduce** Steps to reproduce the behavior: Unable to show steps for reproduction as It happens randomly **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> I should be allowed to login and see my stuff **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> https://thykeis.gay/i/aB8QcLlKQf **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> Docker on Debian 10 **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@johntdavis84 commented on GitHub (Sep 30, 2021):

Does restarting the docker container help at all? I realize it’s random and hard to reproduce, but when this happened to me and I got completely locked out, restarting the container always fixed it.

On Sep 29, 2021, at 2:24 PM, Thyke Adams @.***> wrote:

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Yes
Are you sure you're not using someone else's docker image?
Yes
Have you searched for similar issues (both open and closed)?
Yes
Describe the bug

This is the second time it has happened to me, but i try to log into NPM ant it takes forever then (if) it lets me in, none of my proxies load, If I check the console i get this
[9/29/2021] [7:17:17 PM] [Express ] › ⚠ warning Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?

Nginx Proxy Manager Version

2.9.4

To Reproduce
Steps to reproduce the behavior:
Unable to show steps for reproduction as It happens randomly

Expected behavior

I should be allowed to login and see my stuff

Screenshots

https://thykeis.gay/i/aB8QcLlKQf https://thykeis.gay/i/aB8QcLlKQf
Operating System

Docker on Debian 10

Additional context

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/jc21/nginx-proxy-manager/issues/1442, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGI5CYSE4GITT2CKHB2KMEDUENRYXANCNFSM5FAUHOZA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

<!-- gh-comment-id:930685663 --> @johntdavis84 commented on GitHub (Sep 30, 2021): Does restarting the docker container help at all? I realize it’s random and hard to reproduce, but when this happened to me and I got completely locked out, restarting the container always fixed it. > On Sep 29, 2021, at 2:24 PM, Thyke Adams ***@***.***> wrote: > > > Checklist > > Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? > Yes > Are you sure you're not using someone else's docker image? > Yes > Have you searched for similar issues (both open and closed)? > Yes > Describe the bug > > This is the second time it has happened to me, but i try to log into NPM ant it takes forever then (if) it lets me in, none of my proxies load, If I check the console i get this > [9/29/2021] [7:17:17 PM] [Express ] › ⚠ warning Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? > > Nginx Proxy Manager Version > > 2.9.4 > > To Reproduce > Steps to reproduce the behavior: > Unable to show steps for reproduction as It happens randomly > > Expected behavior > > I should be allowed to login and see my stuff > > Screenshots > > https://thykeis.gay/i/aB8QcLlKQf <https://thykeis.gay/i/aB8QcLlKQf> > Operating System > > Docker on Debian 10 > > Additional context > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub <https://github.com/jc21/nginx-proxy-manager/issues/1442>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGI5CYSE4GITT2CKHB2KMEDUENRYXANCNFSM5FAUHOZA>. > Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. >
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@Marki-dev commented on GitHub (Sep 30, 2021):

ill try that rn, last time it happened, I restarted and then the docker container refused to start at all

<!-- gh-comment-id:931526629 --> @Marki-dev commented on GitHub (Sep 30, 2021): ill try that rn, last time it happened, I restarted and then the docker container refused to start at all
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@JHeat commented on GitHub (Oct 5, 2021):

+1 docker restart helps but it's less than ideal. I really only see this impacting folks that are first configuring/triaging so it becomes more apparent? either way - if I can provide you with anything to investigate. Let me know. Thanks!

<!-- gh-comment-id:934049883 --> @JHeat commented on GitHub (Oct 5, 2021): +1 docker restart helps but it's less than ideal. I really only see this impacting folks that are first configuring/triaging so it becomes more apparent? either way - if I can provide you with anything to investigate. Let me know. Thanks!
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@Marki-dev commented on GitHub (Oct 5, 2021):

I just updated to the latest version and re-added all streams/proxies, I’ll update this if it happens again with the latest version

<!-- gh-comment-id:934345974 --> @Marki-dev commented on GitHub (Oct 5, 2021): I just updated to the latest version and re-added all streams/proxies, I’ll update this if it happens again with the latest version
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Oct 5, 2021):

Maybe it has to do with the database not being available yet or still being set up? We'll have to wait for more detailed reports

<!-- gh-comment-id:934802829 --> @chaptergy commented on GitHub (Oct 5, 2021): Maybe it has to do with the database not being available yet or still being set up? We'll have to wait for more detailed reports
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@merrychrishna commented on GitHub (Oct 17, 2021):

its my first time installing this image and its happenig to me too but restarting the container isnt fixing it even temporarily

<!-- gh-comment-id:945054203 --> @merrychrishna commented on GitHub (Oct 17, 2021): its my first time installing this image and its happenig to me too but restarting the container isnt fixing it even temporarily
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@merrychrishna commented on GitHub (Oct 17, 2021):

is this only a problem when installing the image in portainer? if so, whats the proper portainer configuration? maybe im missing a setting?

<!-- gh-comment-id:945055098 --> @merrychrishna commented on GitHub (Oct 17, 2021): is this only a problem when installing the image in portainer? if so, whats the proper portainer configuration? maybe im missing a setting?
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@merrychrishna commented on GitHub (Oct 17, 2021):

if i stop the container, i can still see the login page when i refresh.

another thing is if i start the container and open an incognito window in chrome i can not get the login page to be displayed

<!-- gh-comment-id:945058547 --> @merrychrishna commented on GitHub (Oct 17, 2021): if i stop the container, i can still see the login page when i refresh. another thing is if i start the container and open an incognito window in chrome i can not get the login page to be displayed
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@merrychrishna commented on GitHub (Oct 17, 2021):

here are my 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.


❯ Enabling IPV6 in hosts: /etc/nginx/conf.d


  ❯ /etc/nginx/conf.d/production.conf


  ❯ /etc/nginx/conf.d/default.conf


  ❯ /etc/nginx/conf.d/include/ip_ranges.conf


  ❯ /etc/nginx/conf.d/include/proxy.conf


  ❯ /etc/nginx/conf.d/include/block-exploits.conf


  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf


  ❯ /etc/nginx/conf.d/include/assets.conf


  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf


  ❯ /etc/nginx/conf.d/include/force-ssl.conf


  ❯ /etc/nginx/conf.d/include/resolvers.conf


❯ Enabling IPV6 in hosts: /data/nginx


  ❯ /data/nginx/proxy_host/2.conf


  ❯ /data/nginx/ip_ranges.conf


  ❯ /data/nginx/resolvers.conf


WARNING: NODE_ENV value of 'production' did not match any deployment config file names.


WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode


[10/17/2021] [7:06:10 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:06:21 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:06:32 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:06:43 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:06:54 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:07:05 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:07:16 AM] [Global   ] › ✖  error     getaddrinfo ENOTFOUND db


[10/17/2021] [7:07:27 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:07:38 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:07:49 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:08:00 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:08:11 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:08:22 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:08:33 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:08:44 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:08:55 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:09:06 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:09:17 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:09:28 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:09:39 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:09:50 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:10:01 AM] [Global   ] › ✖  error     connect ETIMEDOUT


[10/17/2021] [7:10:12 AM] [Global   ] › ✖  error     connect ETIMEDOUT

something about the environment variable "production". i have not even set that env variable.

<!-- gh-comment-id:945063921 --> @merrychrishna commented on GitHub (Oct 17, 2021): here are my 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. ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/production.conf ❯ /etc/nginx/conf.d/default.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ Enabling IPV6 in hosts: /data/nginx ❯ /data/nginx/proxy_host/2.conf ❯ /data/nginx/ip_ranges.conf ❯ /data/nginx/resolvers.conf WARNING: NODE_ENV value of 'production' did not match any deployment config file names. WARNING: See https://github.com/lorenwest/node-config/wiki/Strict-Mode [10/17/2021] [7:06:10 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:06:21 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:06:32 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:06:43 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:06:54 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:07:05 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:07:16 AM] [Global ] › ✖ error getaddrinfo ENOTFOUND db [10/17/2021] [7:07:27 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:07:38 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:07:49 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:08:00 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:08:11 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:08:22 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:08:33 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:08:44 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:08:55 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:09:06 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:09:17 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:09:28 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:09:39 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:09:50 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:10:01 AM] [Global ] › ✖ error connect ETIMEDOUT [10/17/2021] [7:10:12 AM] [Global ] › ✖ error connect ETIMEDOUT ``` something about the environment variable "production". i have not even set that env variable.
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@merrychrishna commented on GitHub (Oct 17, 2021):

also related, if i create the container in portainer then refresh the page, my ip and ports disappear from the container list.

<!-- gh-comment-id:945146879 --> @merrychrishna commented on GitHub (Oct 17, 2021): also related, if i create the container in portainer then refresh the page, my ip and ports disappear from the container list.
kerem commented 2026-02-26 06:35:50 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Oct 17, 2021):

@merrychrishna You probably just don't have the database and npm in the same docker network. At least npm is not able to connect to the database container. Or maybe you gave your database container a different name and it is not resolvable under the name db?

<!-- gh-comment-id:945150564 --> @chaptergy commented on GitHub (Oct 17, 2021): @merrychrishna You probably just don't have the database and npm in the same docker network. At least npm is not able to connect to the database container. Or maybe you gave your database container a different name and it is not resolvable under the name `db`?
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@merrychrishna commented on GitHub (Oct 18, 2021):

@chaptergy i think youre right about it being a problem with npm. im a noob. is there a guide on setting everything up starting from installing npm on ubuntu then docker then portainer then nginx?

<!-- gh-comment-id:945230444 --> @merrychrishna commented on GitHub (Oct 18, 2021): @chaptergy i think youre right about it being a problem with npm. im a noob. is there a guide on setting everything up starting from installing npm on ubuntu then docker then portainer then nginx?
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Oct 18, 2021):

NginxProxyManager (NPM) requires docker, so docker is the first thing you have to install. There is no official documentation going that much into detail, but you should be able to find some articles when searching the web. If you want to deploy NPM via portainer, you'll need to install docker and portainer first, and could then use the app templates > custom templates to paste the docker-compose file into portainer and deploy it. Nginx is already bundled in NPM, so you shouldn't have to explicitly install it.

<!-- gh-comment-id:945639432 --> @chaptergy commented on GitHub (Oct 18, 2021): NginxProxyManager (NPM) requires docker, so docker is the first thing you have to install. There is no official documentation going that much into detail, but you should be able to find some articles when searching the web. If you want to deploy NPM via portainer, you'll need to install docker and portainer first, and could then use the app templates > custom templates to paste the docker-compose file into portainer and deploy it. Nginx is already bundled in NPM, so you shouldn't have to explicitly install it.
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@merrychrishna commented on GitHub (Oct 18, 2021):

@chaptergy i managed to find some help in the portainer discord. i will post my note at the end of this message. i just havent been able to check the letsencrypt certificates out yet because they are cooling down due to too many failed attempts at issueing renewing the certs. i dont know how long the cool down takes but i think i read it will take less than a week but thats not very much info that i could find about letsencrypt cooldowns.

heres my notes that got me all setup that might help someone else

delete any and all nginx containers

docker ps -a

docker stop 1d2687ed0a90
docker rm 1d2687ed0a90

create directories with mkdir ~/projects/npm/
cd ~/projects/npm/

nano -c docker-compose.yml

add this to nano

version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    container_name: npm2021
    restart: always
    ports:
      # HTTP port
      - '8080:80'
      # HTTPS Port:
      - '8443:443'
      # Admin UI
      - '8181:81'
    environment:
      DB_SQLITE_FILE: "/data/npm.sqlite"
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt






run this command

docker-compose up -d

login to nginx manager on port 8181

<!-- gh-comment-id:945713464 --> @merrychrishna commented on GitHub (Oct 18, 2021): @chaptergy i managed to find some help in the portainer discord. i will post my note at the end of this message. i just havent been able to check the letsencrypt certificates out yet because they are cooling down due to too many failed attempts at issueing renewing the certs. i dont know how long the cool down takes but i think i read it will take less than a week but thats not very much info that i could find about letsencrypt cooldowns. heres my notes that got me all setup that might help someone else ``` delete any and all nginx containers docker ps -a docker stop 1d2687ed0a90 docker rm 1d2687ed0a90 create directories with mkdir ~/projects/npm/ cd ~/projects/npm/ nano -c docker-compose.yml add this to nano version: "3" services: app: image: 'jc21/nginx-proxy-manager:latest' container_name: npm2021 restart: always ports: # HTTP port - '8080:80' # HTTPS Port: - '8443:443' # Admin UI - '8181:81' environment: DB_SQLITE_FILE: "/data/npm.sqlite" volumes: - ./data:/data - ./letsencrypt:/etc/letsencrypt run this command docker-compose up -d ``` login to nginx manager on port 8181
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@sharkaccident commented on GitHub (Jan 13, 2022):

I am having the same issue when deploying the container through portainer in a docker swarm. I can see the log in screen but when I attempt to login with default credentials I get bad gateway error.

From monitoring the portainer logs it looks like NPM is unable to write to db.

[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.
❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/include/proxy.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /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/letsencrypt-acme-challenge.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
  ❯ /etc/nginx/conf.d/default.conf
  ❯ /etc/nginx/conf.d/production.conf

❯ Enabling IPV6 in hosts: /data/nginx
[1/13/2022] [4:54:25 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[1/13/2022] [4:54:25 AM] [Global   ] › ℹ  info      Generating SQLite knex configuration
[1/13/2022] [4:54:25 AM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
[1/13/2022] [4:54:29 AM] [Global   ] › ✖  error     create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked
[1/13/2022] [4:54:30 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[1/13/2022] [4:54:31 AM] [Global   ] › ✖  error     create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked
[1/13/2022] [4:54:32 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[1/13/2022] [4:54:33 AM] [Global   ] › ✖  error     create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked
[1/13/2022] [4:54:34 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[1/13/2022] [4:54:35 AM] [Global   ] › ✖  error     create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked
[1/13/2022] [4:54:36 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[1/13/2022] [4:54:37 AM] [Global   ] › ✖  error     create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked
[1/13/2022] [4:54:38 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[1/13/2022] [4:54:39 AM] [Global   ] › ✖  error     create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked
[1/13/2022] [4:54:40 AM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'

Portainer Config

<!-- gh-comment-id:1011796831 --> @sharkaccident commented on GitHub (Jan 13, 2022): I am having the same issue when deploying the container through portainer in a docker swarm. I can see the log in screen but when I attempt to login with default credentials I get bad gateway error. From monitoring the portainer logs it looks like NPM is unable to write to db. ``` [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. ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /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/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ /etc/nginx/conf.d/default.conf ❯ /etc/nginx/conf.d/production.conf ❯ Enabling IPV6 in hosts: /data/nginx [1/13/2022] [4:54:25 AM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' [1/13/2022] [4:54:25 AM] [Global ] › ℹ info Generating SQLite knex configuration [1/13/2022] [4:54:25 AM] [Global ] › ⬤ debug Wrote db configuration to config file: ./config/production.json [1/13/2022] [4:54:29 AM] [Global ] › ✖ error create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked [1/13/2022] [4:54:30 AM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' [1/13/2022] [4:54:31 AM] [Global ] › ✖ error create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked [1/13/2022] [4:54:32 AM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' [1/13/2022] [4:54:33 AM] [Global ] › ✖ error create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked [1/13/2022] [4:54:34 AM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' [1/13/2022] [4:54:35 AM] [Global ] › ✖ error create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked [1/13/2022] [4:54:36 AM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' [1/13/2022] [4:54:37 AM] [Global ] › ✖ error create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked [1/13/2022] [4:54:38 AM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' [1/13/2022] [4:54:39 AM] [Global ] › ✖ error create table `knex_migrations` (`id` integer not null primary key autoincrement, `name` varchar(255), `batch` integer, `migration_time` datetime) - SQLITE_BUSY: database is locked [1/13/2022] [4:54:40 AM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' ``` [Portainer Config](https://i.postimg.cc/Yq0HHKYr/npm.jpg)
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@chaptergy commented on GitHub (Jan 13, 2022):

@sharkaccident Have a look at https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1678, maybe that helps. I'm not familiar with docker swarm, could it also be that multiple instances of the same docker container try to access the database file and somehow block each other?

<!-- gh-comment-id:1012025180 --> @chaptergy commented on GitHub (Jan 13, 2022): @sharkaccident Have a look at https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1678, maybe that helps. I'm not familiar with docker swarm, could it also be that multiple instances of the same docker container try to access the database file and somehow block each other?
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@sharkaccident commented on GitHub (Jan 13, 2022):

@chaptergy . Changing fstab to in include nolock:
//myserver /mymount cifs username=*,password=*,nolock,uid=1000,gid=1000
worked!

<!-- gh-comment-id:1012077162 --> @sharkaccident commented on GitHub (Jan 13, 2022): @chaptergy . Changing fstab to in include nolock: `//myserver /mymount cifs username=*,password=*,nolock,uid=1000,gid=1000` worked!
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@kt-solutions commented on GitHub (Feb 10, 2022):

For me it worked to have this db-image instead of the latest:

jc21/mariadb-aria:10.4.15-innodb

<!-- gh-comment-id:1034876461 --> @kt-solutions commented on GitHub (Feb 10, 2022): For me it worked to have this db-image instead of the latest: `jc21/mariadb-aria:10.4.15-innodb`
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Mar 3, 2024):

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

<!-- gh-comment-id:1974976703 --> @github-actions[bot] commented on GitHub (Mar 3, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@rightsaidfred99 commented on GitHub (Sep 29, 2024):

Still open this issue

<!-- gh-comment-id:2381106033 --> @rightsaidfred99 commented on GitHub (Sep 29, 2024): Still open this issue
kerem commented 2026-02-26 06:35:51 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Apr 16, 2025):

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

<!-- gh-comment-id:2808021552 --> @github-actions[bot] commented on GitHub (Apr 16, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
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#1119
No description provided.