2.7.0 not starting

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:

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

[jc21]

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]

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