[GH-ISSUE #2773] s6-rc: warning: unable to start service prepare #1907

New issue

Open

opened 2026-02-26 07:33:10 +03:00 by kerem · 18 comments

kerem commented 2026-02-26 07:33:10 +03:00

Owner

Copy link

Originally created by @techsolo12 on GitHub (Mar 29, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2773

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
After update to 2.10.1 i got a error, if i use a custom ssl-ciphers file.

Log:
[+] Running 1/1
✔ Container nginx-proxy-manager Recreated 0.2s
Attaching to nginx-proxy-manager
nginx-proxy-manager | s6-rc: info: service s6rc-oneshot-runner: starting
nginx-proxy-manager | s6-rc: info: service s6rc-oneshot-runner successfully started
nginx-proxy-manager | s6-rc: info: service fix-attrs: starting
nginx-proxy-manager | s6-rc: info: service fix-attrs successfully started
nginx-proxy-manager | s6-rc: info: service legacy-cont-init: starting
nginx-proxy-manager | s6-rc: info: service legacy-cont-init successfully started
nginx-proxy-manager | s6-rc: info: service prepare: starting
nginx-proxy-manager | ❯ Configuring npmuser ...
nginx-proxy-manager | id: 'npmuser': no such user
nginx-proxy-manager | ❯ Checking paths ...
nginx-proxy-manager | ❯ Setting ownership ...
nginx-proxy-manager | ❯ Dynamic resolvers ...
nginx-proxy-manager | ❯ IPv6 ...
nginx-proxy-manager | Enabling IPV6 in hosts in: /etc/nginx/conf.d
nginx-proxy-manager | - /etc/nginx/conf.d/production.conf
nginx-proxy-manager | - /etc/nginx/conf.d/include/ssl-ciphers.conf
nginx-proxy-manager | sed: cannot rename /etc/nginx/conf.d/include/sedXg1RRw: Device or resource busy
nginx-proxy-manager | s6-rc: warning: unable to start service prepare: command exited 4
nginx-proxy-manager | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

Nginx Proxy Manager Version
2.10.1

To Reproduce
Steps to reproduce the behavior:

1. Add ssl-ciphers.conf to docker-compose.yaml
2. Start Container
3. See error

Expected behavior
A clean start without an error.

Operating System
Debian 11.x

Originally created by @techsolo12 on GitHub (Mar 29, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2773 <!-- 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** After update to 2.10.1 i got a error, if i use a custom ssl-ciphers file. Log: [+] Running 1/1 ✔ Container nginx-proxy-manager Recreated 0.2s Attaching to nginx-proxy-manager nginx-proxy-manager | s6-rc: info: service s6rc-oneshot-runner: starting nginx-proxy-manager | s6-rc: info: service s6rc-oneshot-runner successfully started nginx-proxy-manager | s6-rc: info: service fix-attrs: starting nginx-proxy-manager | s6-rc: info: service fix-attrs successfully started nginx-proxy-manager | s6-rc: info: service legacy-cont-init: starting nginx-proxy-manager | s6-rc: info: service legacy-cont-init successfully started nginx-proxy-manager | s6-rc: info: service prepare: starting nginx-proxy-manager | ❯ Configuring npmuser ... nginx-proxy-manager | id: 'npmuser': no such user nginx-proxy-manager | ❯ Checking paths ... nginx-proxy-manager | ❯ Setting ownership ... nginx-proxy-manager | ❯ Dynamic resolvers ... nginx-proxy-manager | ❯ IPv6 ... nginx-proxy-manager | Enabling IPV6 in hosts in: /etc/nginx/conf.d nginx-proxy-manager | - /etc/nginx/conf.d/production.conf nginx-proxy-manager | - /etc/nginx/conf.d/include/ssl-ciphers.conf nginx-proxy-manager | sed: cannot rename /etc/nginx/conf.d/include/sedXg1RRw: Device or resource busy nginx-proxy-manager | s6-rc: warning: unable to start service prepare: command exited 4 nginx-proxy-manager | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. **Nginx Proxy Manager Version** 2.10.1 **To Reproduce** Steps to reproduce the behavior: 1. Add ssl-ciphers.conf to docker-compose.yaml 2. Start Container 3. See error **Expected behavior** A clean start without an error. **Operating System** Debian 11.x

kerem added the

stale

bug

labels 2026-02-26 07:33:10 +03:00

kerem commented 2026-02-26 07:33:10 +03:00

Author

Owner

Copy link

@ConTraXX commented on GitHub (Apr 1, 2023):

I had this issue and fixed it by downgrading the docker image to v2.9.22.
May or may not be the same as you, but for me I need to stop using watchtower. I believe it causes more problems than it could solve...and start pinning versions so that I can review changes and plan for them.

<!-- gh-comment-id:1492813826 --> @ConTraXX commented on GitHub (Apr 1, 2023): I had this issue and fixed it by downgrading the docker image to [v2.9.22](https://github.com/NginxProxyManager/nginx-proxy-manager/releases/tag/v2.9.22). May or may not be the same as you, but for me I need to stop using watchtower. I believe it causes more problems than it could solve...and start pinning versions so that I can review changes and plan for them.

kerem commented 2026-02-26 07:33:10 +03:00

Author

Owner

Copy link

@hugalafutro commented on GitHub (Apr 6, 2023):

@ConTraXX I wholeheartedly recommend https://github.com/crazy-max/diun/ I have it setup so that every few days I get list of updated images on telegram, can then review changes or just backup / snapshot and take the plunge with new image. Watchtower looks nice I know; set it and forget it; but having used it on a machine running ~50 containers it was no bueno.

<!-- gh-comment-id:1499153345 --> @hugalafutro commented on GitHub (Apr 6, 2023): @ConTraXX I wholeheartedly recommend https://github.com/crazy-max/diun/ I have it setup so that every few days I get list of updated images on telegram, can then review changes or just backup / snapshot and take the plunge with new image. Watchtower looks nice I know; set it and forget it; but having used it on a machine running ~50 containers it was no bueno.

kerem commented 2026-02-26 07:33:10 +03:00

Author

Owner

Copy link

@k3d3 commented on GitHub (Apr 9, 2023):

I was having the same issue, because I had also overridden ssl-ciphers.conf.

This occurs because sed in a startup script tries to modify (via copying+replacing) every file in /etc/nginx and /data/nginx. The script causing this issue is github.com/NginxProxyManager/nginx-proxy-manager@67208e43cc/docker/rootfs/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh

So what I did was, in my docker-compose file, I added the following line under volumes:

- /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh

It's not the greatest solution, but it's a workaround at least.

<!-- gh-comment-id:1501040392 --> @k3d3 commented on GitHub (Apr 9, 2023): I was having the same issue, because I had also overridden ssl-ciphers.conf. This occurs because sed in a startup script tries to modify (via copying+replacing) every file in /etc/nginx and /data/nginx. The script causing this issue is https://github.com/NginxProxyManager/nginx-proxy-manager/blob/67208e43cc41f659ae2e68baa58a181a4d5f465b/docker/rootfs/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh So what I did was, in my docker-compose file, I added the following line under volumes: ``` - /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh ``` It's not the greatest solution, but it's a workaround at least.

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@zthxxx commented on GitHub (Apr 17, 2023):

same problem here, and the workaround in @k3d3's comment work for me

<!-- gh-comment-id:1511701485 --> @zthxxx commented on GitHub (Apr 17, 2023): same problem here, and the workaround in @k3d3's comment work for me

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@elsternet commented on GitHub (May 5, 2023):

same problem here, same workaround worked.

<!-- gh-comment-id:1536188540 --> @elsternet commented on GitHub (May 5, 2023): same problem here, same workaround worked.

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@b3ni commented on GitHub (May 25, 2023):

Same problem, but not resolved.
Version: 2.9.22

version: "3.5"

services:
  proxy-manager:
    image: jc21/nginx-proxy-manager:${PROXY_MANAGER_VERSION}
    container_name: proxy-manager
    restart: always
    tty: true
    volumes:
      - ./volumes/proxy-manager/data:/data
      - ./volumes/proxy-manager/letsencrypt:/etc/letsencrypt
      - ./config/ip-forward.conf:/etc/nginx/conf.d/include/ip-forward.conf
    logging:
      driver: "json-file"
      options:
          max-file: "5"
          max-size: "20m"

Error at start:

proxy-manager  | Changing ownership of /data/logs to 0:0
proxy-manager  | ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
proxy-manager  |   ❯ /etc/nginx/conf.d/default.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/production.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/include/force-ssl.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/include/proxy.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/include/block-exploits.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/include/ip_ranges.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/include/assets.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/include/resolvers.conf
proxy-manager  |   ❯ /etc/nginx/conf.d/include/ip-forward.conf
proxy-manager  | sed: cannot rename /etc/nginx/conf.d/include/sedkt3Mbt: Device or resource busy
proxy-manager  | s6-rc: warning: unable to start service prepare: command exited 4
proxy-manager  | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

When comment volume line: ip-forward.conf start ok.

<!-- gh-comment-id:1562417281 --> @b3ni commented on GitHub (May 25, 2023): Same problem, but not resolved. Version: 2.9.22 ``` version: "3.5" services: proxy-manager: image: jc21/nginx-proxy-manager:${PROXY_MANAGER_VERSION} container_name: proxy-manager restart: always tty: true volumes: - ./volumes/proxy-manager/data:/data - ./volumes/proxy-manager/letsencrypt:/etc/letsencrypt - ./config/ip-forward.conf:/etc/nginx/conf.d/include/ip-forward.conf logging: driver: "json-file" options: max-file: "5" max-size: "20m" ``` Error at start: ``` proxy-manager | Changing ownership of /data/logs to 0:0 proxy-manager | ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d proxy-manager | ❯ /etc/nginx/conf.d/default.conf proxy-manager | ❯ /etc/nginx/conf.d/production.conf proxy-manager | ❯ /etc/nginx/conf.d/include/force-ssl.conf proxy-manager | ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf proxy-manager | ❯ /etc/nginx/conf.d/include/proxy.conf proxy-manager | ❯ /etc/nginx/conf.d/include/block-exploits.conf proxy-manager | ❯ /etc/nginx/conf.d/include/ip_ranges.conf proxy-manager | ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf proxy-manager | ❯ /etc/nginx/conf.d/include/assets.conf proxy-manager | ❯ /etc/nginx/conf.d/include/resolvers.conf proxy-manager | ❯ /etc/nginx/conf.d/include/ip-forward.conf proxy-manager | sed: cannot rename /etc/nginx/conf.d/include/sedkt3Mbt: Device or resource busy proxy-manager | s6-rc: warning: unable to start service prepare: command exited 4 proxy-manager | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. ``` When comment volume line: ip-forward.conf start ok.

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@alexunderboots commented on GitHub (May 25, 2023):

downgrade to Version: 2.9.22 - not helpfull for me (((

<!-- gh-comment-id:1562591929 --> @alexunderboots commented on GitHub (May 25, 2023): downgrade to Version: 2.9.22 - not helpfull for me (((

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@alexunderboots commented on GitHub (May 30, 2023):

• /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh
  It's work, thanks

<!-- gh-comment-id:1567776441 --> @alexunderboots commented on GitHub (May 30, 2023): - /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh It's work, thanks

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@jar87 commented on GitHub (Dec 14, 2023):

in my docker-compose file

Where did You do that? I can`t find file...:(

<!-- gh-comment-id:1855407732 --> @jar87 commented on GitHub (Dec 14, 2023): > in my docker-compose file Where did You do that? I can`t find file...:(

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@kodamaChameleon commented on GitHub (Feb 10, 2024):

Errors

npm    | ❯ Configuring npm user ...
npm    | 0
npm    | usermod: no changes
npm    | ❯ Configuring npm group ...
npm    | ❯ Checking paths ...
npm    | --------------------------------------
npm    | ERROR: /etc/letsencrypt is not mounted! Check your docker configuration.
npm    | --------------------------------------
npm    | s6-rc: warning: unable to start service prepare: command exited 1
npm    | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
compose.cli.verbose_proxy.proxy_callable: docker wait <- ('145322e9f9140800abd1ac5fe113c3286126c01e27a1b77cf6500c3bbfc0e6ba')
compose.cli.verbose_proxy.proxy_callable: docker wait -> {'StatusCode': 0}
npm exited with code 0
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('145322e9f9140800abd1ac5fe113c3286126c01e27a1b77cf6500c3bbfc0e6ba')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default',
 'Args': [],
 'Config': {'AttachStderr': False,
            'AttachStdin': False,
            'AttachStdout': False,
            'Cmd': None,
            'Domainname': '',
            'Entrypoint': ['/init'],
            'Env': ['PATH=/opt/certbot/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin',
                    'SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt',
...
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('145322e9f9140800abd1ac5fe113c3286126c01e27a1b77cf6500c3bbfc0e6ba')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default',
 'Args': [],
 'Config': {'AttachStderr': False,
            'AttachStdin': False,
            'AttachStdout': False,
            'Cmd': None,
            'Domainname': '',
            'Entrypoint': ['/init'],
            'Env': ['PATH=/opt/certbot/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin',
                    'SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt',
...
compose.cli.verbose_proxy.proxy_callable: docker attach <- ('145322e9f9140800abd1ac5fe113c3286126c01e27a1b77cf6500c3bbfc0e6ba', stdout=True, stderr=True, stream=True)

"Successful" Workaround

Having this same issue. Downgrading to version v2.10.4 solved the problem for me.

My docker-compose file:

version: '3.8'
services:
  app:
    image: jc21/nginx-proxy-manager:2.10.4
    hostname: npm.doroco.org
    container_name: npm
    networks:
      - docker-net
    restart: always
    ports:
      - '80:80'    # Public HTTP Port
      - '443:443'  # Public HTTPS Port
      - '81:81'    # Admin Web Port
    volumes:
      - npm_data:/app/data
      - npm_letsencrypt:/app/letsencrypt

volumes:
  npm_data:
  npm_letsencrypt:

networks:
  docker-net:
    driver: bridge

Failed Attempts

• Tried installing as 2.10.4 and then upgrading to latest
• Tried adding @k3d3's suggested - /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh to volumes

<!-- gh-comment-id:1937040016 --> @kodamaChameleon commented on GitHub (Feb 10, 2024): ### Errors  ``` npm | ❯ Configuring npm user ... npm | 0 npm | usermod: no changes npm | ❯ Configuring npm group ... npm | ❯ Checking paths ... npm | -------------------------------------- npm | ERROR: /etc/letsencrypt is not mounted! Check your docker configuration. npm | -------------------------------------- npm | s6-rc: warning: unable to start service prepare: command exited 1 npm | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. compose.cli.verbose_proxy.proxy_callable: docker wait <- ('145322e9f9140800abd1ac5fe113c3286126c01e27a1b77cf6500c3bbfc0e6ba') compose.cli.verbose_proxy.proxy_callable: docker wait -> {'StatusCode': 0} npm exited with code 0 compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('145322e9f9140800abd1ac5fe113c3286126c01e27a1b77cf6500c3bbfc0e6ba') compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default', 'Args': [], 'Config': {'AttachStderr': False, 'AttachStdin': False, 'AttachStdout': False, 'Cmd': None, 'Domainname': '', 'Entrypoint': ['/init'], 'Env': ['PATH=/opt/certbot/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin', 'SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt', ... compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('145322e9f9140800abd1ac5fe113c3286126c01e27a1b77cf6500c3bbfc0e6ba') compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default', 'Args': [], 'Config': {'AttachStderr': False, 'AttachStdin': False, 'AttachStdout': False, 'Cmd': None, 'Domainname': '', 'Entrypoint': ['/init'], 'Env': ['PATH=/opt/certbot/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin', 'SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt', ... compose.cli.verbose_proxy.proxy_callable: docker attach <- ('145322e9f9140800abd1ac5fe113c3286126c01e27a1b77cf6500c3bbfc0e6ba', stdout=True, stderr=True, stream=True) ``` ### "Successful" Workaround Having this same issue. Downgrading to version [v2.10.4](https://github.com/NginxProxyManager/nginx-proxy-manager/releases/tag/v2.10.4) solved the problem for me. My docker-compose file: ``` version: '3.8' services: app: image: jc21/nginx-proxy-manager:2.10.4 hostname: npm.doroco.org container_name: npm networks: - docker-net restart: always ports: - '80:80' # Public HTTP Port - '443:443' # Public HTTPS Port - '81:81' # Admin Web Port volumes: - npm_data:/app/data - npm_letsencrypt:/app/letsencrypt volumes: npm_data: npm_letsencrypt: networks: docker-net: driver: bridge ``` ### Failed Attempts - Tried installing as 2.10.4 and then upgrading to latest - Tried adding @k3d3's suggested `- /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh` to volumes

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@bobbywaz commented on GitHub (May 5, 2024):

thanks k3d3, fixed for me too!

<!-- gh-comment-id:2094948451 --> @bobbywaz commented on GitHub (May 5, 2024): thanks k3d3, fixed for me too!

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@kmanwar89 commented on GitHub (May 13, 2024):

I'm running into this issue on the v3 branch. Recognizing v3 isn't "released" yet, it's just interesting to note here because I (previously) was actually able to get v3 running, so this error seems to be "new" (I guess?). The /dev/null workaround did not work, unfortunately; logs below:

[+] Running 2/2
 ✔ Network npm_v3_default  Created                                                                                         0.1s
 ✔ Container npm_v3-app-1  Started                                                                                         0.6s
❯ logs
app-1  | 2024-05-13T00:14:48.376863917Z ❯ Configuring npm user ...
app-1  | 2024-05-13T00:14:48.394427393Z ❯ Configuring npm group ...
app-1  | 2024-05-13T00:14:48.419141375Z ❯ Checking paths ...
app-1  | 2024-05-13T00:14:48.424998615Z ❯ Setting ownership ...
app-1  | 2024-05-13T00:14:48.441409642Z ❯ Dynamic resolvers ...
app-1  | 2024-05-13T00:14:48.449219039Z s6-rc: warning: unable to start service prepare: command exited 127
app-1  | 2024-05-13T00:14:48.451035478Z /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

This is the compose file I'm using as a test:

---
services:
  app:
    image: 'jc21/nginx-proxy-manager:v3'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh

networks:
  npm_cf:
    name: npm_cf
    external: true
  npm_service:
    name: npm_service
    external: true

This may have to do with the fact the last release on Dockerhub for v3 was 9 months ago, so not raising a stink over it, just adding it as a data point in case it helps anyone else later down the line.

Edit: I haven't done anything with ssl-ciphers.conf, so my error appears to be a bit more "native" in nature. I also don't have a 50-ipv6.sh file in the error directory based on poking around inside the containers' terminal:

My "working" instance of NPM is currently v2.11.2, and I haven't faced this issue in that version.

<!-- gh-comment-id:2106426684 --> @kmanwar89 commented on GitHub (May 13, 2024): I'm running into this issue on the v3 branch. Recognizing v3 isn't "released" yet, it's just interesting to note here because I (previously) was actually able to get v3 running, so this error seems to be "new" (I guess?). The /dev/null workaround did not work, unfortunately; logs below: ``` [+] Running 2/2 ✔ Network npm_v3_default Created 0.1s ✔ Container npm_v3-app-1 Started 0.6s ❯ logs app-1 | 2024-05-13T00:14:48.376863917Z ❯ Configuring npm user ... app-1 | 2024-05-13T00:14:48.394427393Z ❯ Configuring npm group ... app-1 | 2024-05-13T00:14:48.419141375Z ❯ Checking paths ... app-1 | 2024-05-13T00:14:48.424998615Z ❯ Setting ownership ... app-1 | 2024-05-13T00:14:48.441409642Z ❯ Dynamic resolvers ... app-1 | 2024-05-13T00:14:48.449219039Z s6-rc: warning: unable to start service prepare: command exited 127 app-1 | 2024-05-13T00:14:48.451035478Z /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. ``` This is the compose file I'm using as a test: ``` --- services: app: image: 'jc21/nginx-proxy-manager:v3' restart: unless-stopped ports: - '80:80' - '81:81' - '443:443' volumes: - ./data:/data - /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh networks: npm_cf: name: npm_cf external: true npm_service: name: npm_service external: true ``` This may have to do with the fact the last release on Dockerhub for v3 was 9 months ago, so not raising a stink over it, just adding it as a data point in case it helps anyone else later down the line. **Edit**: I haven't done anything with ssl-ciphers.conf, so my error appears to be a bit more "native" in nature. I also don't have a 50-ipv6.sh file in the error directory based on poking around inside the containers' terminal:  My "working" instance of NPM is currently v2.11.2, and I haven't faced this issue in that version.

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@fuqiangleon commented on GitHub (May 17, 2024):

@kmanwar89 did you fix the error above?

<!-- gh-comment-id:2118481030 --> @fuqiangleon commented on GitHub (May 17, 2024): @kmanwar89 did you fix the error above?

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@kmanwar89 commented on GitHub (May 19, 2024):

@kmanwar89 did you fix the error above?

Nope - I'm instead switching back to v2, and have been writing a Python program for programmatically adding in proxy hosts using Python instead. I was hoping someone with more knowledge of the error would chime in.

<!-- gh-comment-id:2119211940 --> @kmanwar89 commented on GitHub (May 19, 2024): > @kmanwar89 did you fix the error above? Nope - I'm instead switching back to v2, and have been writing a Python program for programmatically adding in proxy hosts using Python instead. I was hoping someone with more knowledge of the error would chime in.

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@artenais commented on GitHub (Dec 3, 2024):

In v3 seems to happen on acme.sh :

❯ Dynamic resolvers ...
+++ is_true true
++++ echo true
++++ tr '[:upper:]' '[:lower:]'
+++ VAL=true
+++ '[' true == true ']'
+++ echo 1

++ echo resolver '10.43.0.10 ipv6=off valid=10s;'
++ acme.sh -h
s6-rc: warning: unable to start service prepare: command exited 127
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

WORKAROUND FOR LOCAL PATH :

1. start the docker with your localpath mounted to another direcotry like /tmpdata
2. cp -Rf /data/.acme.sh/ /tmpdata
3. re-map /tmpdata to /data.
4. profit?

<!-- gh-comment-id:2515702612 --> @artenais commented on GitHub (Dec 3, 2024): In v3 seems to happen on acme.sh : ❯ Dynamic resolvers ... +++ is_true true ++++ echo true ++++ tr '[:upper:]' '[:lower:]' +++ VAL=true +++ '[' true == true ']' +++ echo 1 ++ echo resolver '10.43.0.10 ipv6=off valid=10s;' ++ acme.sh -h s6-rc: warning: unable to start service prepare: command exited 127 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. WORKAROUND FOR LOCAL PATH : 1) start the docker with your localpath mounted to another direcotry like /tmpdata 2) cp -Rf /data/.acme.sh/ /tmpdata 3) re-map /tmpdata to /data. 4) profit?

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jun 11, 2025):

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

<!-- gh-comment-id:2961023939 --> @github-actions[bot] commented on GitHub (Jun 11, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@Whatchawnt commented on GitHub (Jun 16, 2025):

I'm getting this as well tried - /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh and downgrading to v2.10.4 to no avail, also tried @kodamaChameleon method as well still nothing. I'm running on TrueNAS so maybe that also might play a role in things?

<!-- gh-comment-id:2975170180 --> @Whatchawnt commented on GitHub (Jun 16, 2025): I'm getting this as well tried `- /dev/null:/etc/s6-overlay/s6-rc.d/prepare/50-ipv6.sh` and downgrading to v2.10.4 to no avail, also tried @kodamaChameleon method as well still nothing. I'm running on TrueNAS so maybe that also might play a role in things?

kerem commented 2026-02-26 07:33:11 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jan 25, 2026):

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

<!-- gh-comment-id:3795841576 --> @github-actions[bot] commented on GitHub (Jan 25, 2026): 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

Subscribe

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

No description provided.