starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

npm-1` after restarting OR tearing down and recreating container #2740

New issue

Open

opened 2026-02-26 07:36:39 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:36:39 +03:00

Owner

Originally created by @jaysee260 on GitHub (Dec 16, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4239

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

I am setting up Nginx Proxy Manager for the very first time. I create my own SSL cert using LetsEncrypt.

The very first time I started the container, everything worked; I was able to login, register proxy hosts, etc.

However, whenever if I tear down and recreate the container, the process inside the container seems to be unable to access the cert files in /etc/letsencrypt/live/npm-1.

I am using docker compose on Debian 12, and here's what I see in the logs whenever I restart or recreate the container.

2024-12-16 18:48:51 ❯ Configuring npm user ...
2024-12-16 18:48:51 ❯ Configuring npm group ...
2024-12-16 18:48:51 ❯ Checking paths ...
2024-12-16 18:48:51 ❯ Setting ownership ...
2024-12-16 18:48:51 useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.
2024-12-16 18:48:51 chown: changing ownership of '/etc/letsencrypt/live/npm-1/chain.pem': Operation not permitted
2024-12-16 18:48:51 chown: changing ownership of '/etc/letsencrypt/live/npm-1/cert.pem': Operation not permitted
2024-12-16 18:48:51 chown: changing ownership of '/etc/letsencrypt/live/npm-1/fullchain.pem': Operation not permitted
2024-12-16 18:48:51 chown: changing ownership of '/etc/letsencrypt/live/npm-1/privkey.pem': Operation not permitted
2024-12-16 18:48:51 s6-rc: warning: unable to start service prepare: command exited 1
2024-12-16 18:48:51 /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 makes it so that I can't login to the admin page.

Here's my docker-compose config for the service:

networks:
  proxy-net:
    name: proxy-net
    external: true

services:
  nginx-manager:
    image: 'jc21/nginx-proxy-manager:latest'
    container_name: nginx-manager
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ${HOME}/docker-data/nginx/data:/data:rw
      - ${HOME}/docker-data/nginx/letsencrypt:/etc/letsencrypt:rw
    networks:
      - proxy-net

If I tear down EVERYTHING and start fresh, meaning... recreating an admin user, recreating an SSL cert, re-adding my proxy hosts, etc, then it works. But, of course, I'd like to avoid having to do this every time!

Is it something around the mounted volume's permissions? I've been scratching my head at this for a few hours, if anyone has any insight into what the problem might be, or how to fix it, I'd greatly appreciate it!

Nginx Proxy Manager Version

2.12.1

Expected behavior

Since I am using a mounted volume to store the nginx manager data and my SSL cert on my host machine, I would expected to be able to tear down the container and spin up a new one as many times, and still be able to login and re-use the cert I created.

Operating System

Debian 12

Originally created by @jaysee260 on GitHub (Dec 16, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4239  **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**  I am setting up Nginx Proxy Manager for the very first time. I create my own SSL cert using LetsEncrypt. The very first time I started the container, everything worked; I was able to login, register proxy hosts, etc. However, whenever if I tear down and recreate the container, the process inside the container seems to be unable to access the cert files in `/etc/letsencrypt/live/npm-1`. I am using docker compose on Debian 12, and here's what I see in the logs whenever I restart or recreate the container. ```sh 2024-12-16 18:48:51 ❯ Configuring npm user ... 2024-12-16 18:48:51 ❯ Configuring npm group ... 2024-12-16 18:48:51 ❯ Checking paths ... 2024-12-16 18:48:51 ❯ Setting ownership ... 2024-12-16 18:48:51 useradd warning: npm's uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range. 2024-12-16 18:48:51 chown: changing ownership of '/etc/letsencrypt/live/npm-1/chain.pem': Operation not permitted 2024-12-16 18:48:51 chown: changing ownership of '/etc/letsencrypt/live/npm-1/cert.pem': Operation not permitted 2024-12-16 18:48:51 chown: changing ownership of '/etc/letsencrypt/live/npm-1/fullchain.pem': Operation not permitted 2024-12-16 18:48:51 chown: changing ownership of '/etc/letsencrypt/live/npm-1/privkey.pem': Operation not permitted 2024-12-16 18:48:51 s6-rc: warning: unable to start service prepare: command exited 1 2024-12-16 18:48:51 /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 makes it so that I can't login to the admin page. Here's my docker-compose config for the service: ```yml networks: proxy-net: name: proxy-net external: true services: nginx-manager: image: 'jc21/nginx-proxy-manager:latest' container_name: nginx-manager restart: unless-stopped ports: - '80:80' - '81:81' - '443:443' volumes: - ${HOME}/docker-data/nginx/data:/data:rw - ${HOME}/docker-data/nginx/letsencrypt:/etc/letsencrypt:rw networks: - proxy-net ``` If I tear down EVERYTHING and start fresh, meaning... recreating an admin user, recreating an SSL cert, re-adding my proxy hosts, etc, then it works. But, of course, I'd like to avoid having to do this every time! Is it something around the mounted volume's permissions? I've been scratching my head at this for a few hours, if anyone has any insight into what the problem might be, or how to fix it, I'd greatly appreciate it! **Nginx Proxy Manager Version**  `2.12.1` **Expected behavior**  Since I am using a mounted volume to store the nginx manager data and my SSL cert on my host machine, I would expected to be able to tear down the container and spin up a new one as many times, and still be able to login and re-use the cert I created. **Operating System**  Debian 12

kerem added the

stale

bug

labels

2026-02-26 07:36:39 +03:00

kerem commented

2026-02-26 07:36:39 +03:00

Author

Owner

@jaysee260 commented on GitHub (Dec 17, 2024):

Can confirm than I don't even have to tear down the container for this to happen... simply stopping it and restarting causes the issue to start happening!

@jaysee260 commented on GitHub (Dec 17, 2024): Can confirm than I don't even have to tear down the container for this to happen... simply stopping it and restarting causes the issue to start happening!

kerem commented

2026-02-26 07:36:39 +03:00

Author

Owner

@sonpeter88 commented on GitHub (Dec 17, 2024):

having the same issue...
there's already an open issue
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4205

@sonpeter88 commented on GitHub (Dec 17, 2024): having the same issue... there's already an open issue https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4205

kerem commented

2026-02-26 07:36:39 +03:00

Author

Owner

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

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

@github-actions[bot] commented on GitHub (Jun 24, 2025): Issue is now considered stale. If you want to keep it open, please comment :+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#2740

No description provided.

Rows
Columns

[GH-ISSUE #4239] Cannot change ownership of files under /etc/letsencrypt/live/npm-1 after restarting OR tearing down and recreating container #2740

[GH-ISSUE #4239] Cannot change ownership of files under `/etc/letsencrypt/live/npm-1` after restarting OR tearing down and recreating container #2740