starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #699] Cannot start from Image 2.6.2 #589

New issue

Closed

opened 2026-02-26 06:33:33 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:33:33 +03:00

Owner

Originally created by @the-holger on GitHub (Nov 6, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/699

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Yes, I pulled jc21/nginx-proxy-manager:latest (as well as jc21/nginx-proxy-manager:2.6.2)
Are you sure you're not using someone else's docker image?
Yes
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
Seems unrelated to Lets Encrypt (plus: was working just fine with 2.6.1)

Describe the bug

A clear and concise description of what the bug is.
I had to restart my npm container and it didn't come back up. After way to much error checking I realized that when redeploying I pulled the latest image (2.6.2) and was not starting from 2.6.1 anymore.

[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] done.
[services.d] starting services
[services.d] done.
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.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/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/assets.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
  ❯ /etc/nginx/conf.d/production.conf
  ❯ /etc/nginx/conf.d/default.conf
Disabling IPV6 in hosts
❯ Disabling IPV6 in hosts: /data/nginx
  ❯ /data/nginx/default_host/site.conf
  ❯ /data/nginx/dead_host/1.conf
  ❯ /data/nginx/proxy_host/1.conf
  ❯ /data/nginx/proxy_host/5.conf
[...]
[11/6/2020] [11:01:49 PM] [Migrate  ] › ℹ  info      Current database version: none
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
finish: applet not found
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

This repeats until I restart the container.

What version of Nginx Proxy Manager is reported on the login page?
Don't know/haven't checked (as you only see it on the first start), 2.6.1 for the working version

To Reproduce
Steps to reproduce the behavior:

Deploy a container with version 2.6.2
I deployed manually following the setup instructions, using sqlite as my db and adding another network (used to communicate with the containers to be proxied)
Change user details/password
I added one 404 host to test
Restart container
Doesn't come up anymore

Expected behavior
Well, it should start as it did with 2.6.1

Screenshots
n/a

Operating System

deploying on a Debian system with Portainer as a frontend

Additional context

Server:
 Containers: 12
  Running: 12
  Paused: 0
  Stopped: 0
 Images: 16
 Server Version: 19.03.13
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 8fba4e9a7d01810a393d5d25a3621dc101981175
 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
 init version: fec3683
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.4.65-1-pve
 Operating System: Debian GNU/Linux 10 (buster)
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 15.59GiB
 Name: pm1
 ID: 
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Originally created by @the-holger on GitHub (Nov 6, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/699 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? Yes, I pulled jc21/nginx-proxy-manager:latest (as well as jc21/nginx-proxy-manager:2.6.2) - Are you sure you're not using someone else's docker image? Yes - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? Seems unrelated to Lets Encrypt (plus: was working just fine with 2.6.1) **Describe the bug** - A clear and concise description of what the bug is. I had to restart my npm container and it didn't come back up. After way to much error checking I realized that when redeploying I pulled the latest image (2.6.2) and was not starting from 2.6.1 anymore. ``` [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] done. [services.d] starting services [services.d] done. Disabling IPV6 in hosts ❯ Disabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/block-exploits.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/force-ssl.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ /etc/nginx/conf.d/production.conf ❯ /etc/nginx/conf.d/default.conf Disabling IPV6 in hosts ❯ Disabling IPV6 in hosts: /data/nginx ❯ /data/nginx/default_host/site.conf ❯ /data/nginx/dead_host/1.conf ❯ /data/nginx/proxy_host/1.conf ❯ /data/nginx/proxy_host/5.conf [...] [11/6/2020] [11:01:49 PM] [Migrate ] › ℹ info Current database version: none s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. finish: applet not found [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. ``` This repeats until I restart the container. - What version of Nginx Proxy Manager is reported on the login page? Don't know/haven't checked (as you only see it on the first start), 2.6.1 for the working version **To Reproduce** Steps to reproduce the behavior: - Deploy a container with version 2.6.2 - I deployed manually following the setup instructions, using sqlite as my db and adding another network (used to communicate with the containers to be proxied) - Change user details/password - I added one 404 host to test - Restart container - Doesn't come up anymore **Expected behavior** Well, it should start as it did with 2.6.1 **Screenshots** n/a **Operating System** - deploying on a Debian system with Portainer as a frontend **Additional context** ``` Server: Containers: 12 Running: 12 Paused: 0 Stopped: 0 Images: 16 Server Version: 19.03.13 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: 8fba4e9a7d01810a393d5d25a3621dc101981175 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd init version: fec3683 Security Options: apparmor seccomp Profile: default Kernel Version: 5.4.65-1-pve Operating System: Debian GNU/Linux 10 (buster) OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 15.59GiB Name: pm1 ID: Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false ```

kerem

2026-02-26 06:33:33 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:33:33 +03:00

Author

Owner

@alex20465 commented on GitHub (Dec 3, 2020):

Same here I tried almost all version, the same issue over and over again, I remember I fixed long time ago, forgot how.

@alex20465 commented on GitHub (Dec 3, 2020): Same here I tried almost all version, the same issue over and over again, I remember I fixed long time ago, forgot how.

kerem commented

2026-02-26 06:33:33 +03:00

Author

Owner

@alex20465 commented on GitHub (Dec 3, 2020):

OK, the issue is that I used docker swarm stead the classical standalone why docker-compose up.

@alex20465 commented on GitHub (Dec 3, 2020): OK, the issue is that I used docker swarm stead the classical standalone why `docker-compose up`.

No milestone

No project

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#589

No description provided.

Rows
Columns