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 #728] 2.7.0 not starting #618

New issue

Closed

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

kerem commented

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

Owner

Originally created by @rlogiacco on GitHub (Nov 18, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/728

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Are you sure you're not using someone else's docker image?
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?

Describe the bug
Container doesn't start reporting:

[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.,
❯ Enabling 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,
❯ Enabling IPV6 in hosts: /data/nginx,
  ❯ /data/nginx/proxy_host/2.conf,
  ❯ /data/nginx/proxy_host/1.conf,
finish: applet not found,
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.,
[s6-finish] sending all processes the TERM signal.,
[s6-finish] sending all processes the KILL signal and exiting.,

Unable to access on the login page, but I'm starting image tagged 2.7.0

To Reproduce
Steps to reproduce the behavior:

Change a stack happily running 2.6.2 to 2.7.0

Expected behavior
Container starting

Screenshots
Not applicable

Operating System
RedHat EL 7.9

Additional context
Deploying as a stack containing both this container image and mariadb, using NFS mounted volumes ina 3 nodes swarm

Originally created by @rlogiacco on GitHub (Nov 18, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/728 **Checklist** - [x] Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - [x] Are you sure you're not using someone else's docker image? - [x] If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? **Describe the bug** Container doesn't start reporting: ```[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., ❯ Enabling 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, ❯ Enabling IPV6 in hosts: /data/nginx, ❯ /data/nginx/proxy_host/2.conf, ❯ /data/nginx/proxy_host/1.conf, finish: applet not found, 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., [s6-finish] sending all processes the TERM signal., [s6-finish] sending all processes the KILL signal and exiting., ``` - Unable to access on the login page, but I'm starting image tagged `2.7.0` **To Reproduce** Steps to reproduce the behavior: 1. Change a stack happily running `2.6.2` to `2.7.0` **Expected behavior** Container starting **Screenshots** Not applicable **Operating System** RedHat EL 7.9 **Additional context** Deploying as a stack containing both this container image and mariadb, using NFS mounted volumes ina 3 nodes swarm

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@rlogiacco commented on GitHub (Nov 18, 2020):

Switching back to 2.6.2 (nothing else changes other than the image tag) fixes the issue

@rlogiacco commented on GitHub (Nov 18, 2020): Switching back to 2.6.2 (nothing else changes other than the image tag) fixes the issue

kerem commented

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

Author

Owner

@jc21 commented on GitHub (Nov 18, 2020):

Hmm yes I can definitely reproduce this problem in one of my deployments. How embarrassing...

@jc21 commented on GitHub (Nov 18, 2020): Hmm yes I can definitely reproduce this problem in one of my deployments. How embarrassing...

kerem commented

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

Author

Owner

@themreza commented on GitHub (Nov 18, 2020):

Just out of curiosity, are there any build checks (e.g. unit tests, e2e tests) in place before releasing a version?

@themreza commented on GitHub (Nov 18, 2020): Just out of curiosity, are there any build checks (e.g. unit tests, e2e tests) in place before releasing a version?

kerem commented

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

Author

Owner

@rlogiacco commented on GitHub (Nov 18, 2020):

Hmm yes I can definitely reproduce this problem in one of my deployments. How embarrassing...

Sorry @jc21 for doing this, but I'm blocked on 2.6.2 by #594 and #717 : will 2.7.* fix that or can you give me instructions on how to get around the issue? I'm currently looking into the source files to verify if I can get any progress on that as that's blocking for me

@rlogiacco commented on GitHub (Nov 18, 2020): > Hmm yes I can definitely reproduce this problem in one of my deployments. How embarrassing... Sorry @jc21 for doing this, but I'm blocked on `2.6.2` by #594 and #717 : will `2.7.*` fix that or can you give me instructions on how to get around the issue? I'm currently looking into the source files to verify if I can get any progress on that as that's blocking for me

kerem commented

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

Author

Owner

@jc21 commented on GitHub (Nov 18, 2020):

v2.7.1 is released now to fix non-starts.

As for the custom cert issue, I'll bump it to the top of my todo list

@jc21 commented on GitHub (Nov 18, 2020): v2.7.1 is released now to fix non-starts. As for the custom cert issue, I'll bump it to the top of my todo list

kerem commented

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

Author

Owner

@JSH32 commented on GitHub (Dec 2, 2020):

This still happens to me. Docker stack file below.

version: "3.4"
services:
  app:
    image: 'jc21/nginx-proxy-manager:v2.7.1'
    restart: always
    ports:
      # Public HTTP Port:
      - 8081:8081
      # Public HTTPS Port:
      - 8443:8443
      # Admin Web Port:
      - 8080:8080
    environment:
      DB_SQLITE_FILE: "/data/database.sqlite"
      DISABLE_IPV6: 'true'
    volumes:
      - nginx_proxy_data:/data
      - nginx_proxy_letsencrypt:/etc/letsencrypt

volumes:
  nginx_proxy_data:
    name: nginx_proxy_data
  nginx_proxy_letsencrypt:
    name: nginx_proxy_letsencrypt

networks:
  default:
    external:
      name: main

@JSH32 commented on GitHub (Dec 2, 2020): This still happens to me. Docker stack file below. ```yml version: "3.4" services: app: image: 'jc21/nginx-proxy-manager:v2.7.1' restart: always ports: # Public HTTP Port: - 8081:8081 # Public HTTPS Port: - 8443:8443 # Admin Web Port: - 8080:8080 environment: DB_SQLITE_FILE: "/data/database.sqlite" DISABLE_IPV6: 'true' volumes: - nginx_proxy_data:/data - nginx_proxy_letsencrypt:/etc/letsencrypt volumes: nginx_proxy_data: name: nginx_proxy_data nginx_proxy_letsencrypt: name: nginx_proxy_letsencrypt networks: default: external: name: main ```

kerem commented

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

Author

Owner

@gesirdek commented on GitHub (Apr 4, 2021):

this is repeated at 2.8.1

@gesirdek commented on GitHub (Apr 4, 2021): this is repeated at 2.8.1

kerem commented

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

Author

Owner

@julesrulez96 commented on GitHub (Apr 21, 2021):

confirm it is repeated in 2.8.1

@julesrulez96 commented on GitHub (Apr 21, 2021): confirm it is repeated in 2.8.1

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

No description provided.

Rows
Columns