[GH-ISSUE #2015] Not Able To Open Nginx Proxy Manager Admin Panel #1458

New issue

Open

opened 2026-02-26 07:31:08 +03:00 by kerem · 34 comments

kerem commented 2026-02-26 07:31:08 +03:00

Owner

Copy link

Originally created by @Rajeshsahoo12 on GitHub (Apr 19, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2015

I have deployed nginx proxy manager on docker containers. But recently I am not able to access admin panel of the NPM. When I open my remote host at port 81. It gives me below error.

Here I have attached logs from portainer for nginx app. Kindly suggest how to access. As I am not able to any access any external website hosted on server ip.

_nginx_app_1_logs.txt

Only able to access portainer at 9000 port.

Not able to access jellyfin at port 8096 & npm admin panel page at port 81.

Thanks.

Originally created by @Rajeshsahoo12 on GitHub (Apr 19, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2015 I have deployed nginx proxy manager on docker containers. But recently I am not able to access admin panel of the NPM. When I open my remote host at port 81. It gives me below error.  Here I have attached logs from portainer for nginx app. Kindly suggest how to access. As I am not able to any access any external website hosted on server ip. [_nginx_app_1_logs.txt](https://github.com/NginxProxyManager/nginx-proxy-manager/files/8516131/_nginx_app_1_logs.txt) Only able to access portainer at 9000 port. Not able to access jellyfin at port 8096 & npm admin panel page at port 81. Thanks.

kerem added the

stale

label 2026-02-26 07:31:08 +03:00

kerem commented 2026-02-26 07:31:08 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

Have you forwarded port 81 on iptables and on Oracle subnet security list?

<!-- gh-comment-id:1104991979 --> @itsKV commented on GitHub (Apr 21, 2022): Have you forwarded port 81 on iptables and on Oracle subnet security list?

kerem commented 2026-02-26 07:31:08 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

@itsKV Yeah on oracle cloud infrastructure website under compute --> instance --> subnet security list. I have opened port 81 as per below. And it was working fine before 10-15 days. With the same port opened settings. Nothing I have changed. Aprt from my internet connectivity pattern.

But now I am not able to access admin panel of NPM & jellyfin which is my personal media server.

Note : Internet connectivity pattern got changed as earlier I was using fibernet bb connection. Which I have terminated now due to service issues. Currently I am using mobile hotspot.

<!-- gh-comment-id:1105637628 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): @itsKV Yeah on oracle cloud infrastructure website under compute --> instance --> subnet security list. I have opened port 81 as per below. And it was working fine before 10-15 days. With the same port opened settings. Nothing I have changed. Aprt from my internet connectivity pattern.  But now I am not able to access admin panel of NPM & jellyfin which is my personal media server. Note : Internet connectivity pattern got changed as earlier I was using fibernet bb connection. Which I have terminated now due to service issues. Currently I am using mobile hotspot.

kerem commented 2026-02-26 07:31:08 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

But now I am not able to access admin panel of NPM & jellyf

What about iptables rules? Have you checked them? They might have modified meanwhile..

Note : Internet connectivity pattern got changed as earlier I was using fibernet bb con

Your vps service managed by Oracle is same as it was previously. Your mobile device, being client, it doesn't matter how you were/are accessing the vps; let it be cellular or fiber.

<!-- gh-comment-id:1105645156 --> @itsKV commented on GitHub (Apr 21, 2022): > But now I am not able to access admin panel of NPM & jellyf What about iptables rules? Have you checked them? They might have modified meanwhile.. > Note : Internet connectivity pattern got changed as earlier I was using fibernet bb con Your vps service managed by Oracle is same as it was previously. Your mobile device, being client, it doesn't matter how you were/are accessing the vps; let it be cellular or fiber.

kerem commented 2026-02-26 07:31:08 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

What about iptables rules? Have you checked them? They might have modified meanwhile..

Ip table rules is related to oracle cloud vps or anything else..? No I haven't checked them..

<!-- gh-comment-id:1105647891 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): > What about iptables rules? Have you checked them? They might have modified meanwhile.. Ip table rules is related to oracle cloud vps or anything else..? No I haven't checked them..

kerem commented 2026-02-26 07:31:08 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

Your vps service managed by Oracle is same as it was previously

Yup the same provider. I having nothing changed. Just left un-used for a few days. Thats it. What I have setup I was using it well.

Now it doesn't work..

<!-- gh-comment-id:1105649164 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): > Your vps service managed by Oracle is same as it was previously Yup the same provider. I having nothing changed. Just left un-used for a few days. Thats it. What I have setup I was using it well. Now it doesn't work..

kerem commented 2026-02-26 07:31:08 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

Try following command from your laptop/desktop and again on your vps's ssh session terminal. Paste the both responses here.
curl -is http://152.70.75.91:81

• remove the sensitive information, if any.

<!-- gh-comment-id:1105654386 --> @itsKV commented on GitHub (Apr 21, 2022): Try following command from your laptop/desktop and again on your vps's ssh session terminal. Paste the both responses here. `curl -is http://152.70.75.91:81` * remove the sensitive information, if any.

kerem commented 2026-02-26 07:31:08 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

Have tried on vps ssh session. Below is the output. Nothing happens.

And on local machine which is windows 10 based pc. Have tried on terminal. Here below is the output. Nothing happens.

<!-- gh-comment-id:1105659455 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): Have tried on vps ssh session. Below is the output. Nothing happens.  And on local machine which is windows 10 based pc. Have tried on terminal. Here below is the output. Nothing happens. 

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

r u sure docker is running?

<!-- gh-comment-id:1105667431 --> @itsKV commented on GitHub (Apr 21, 2022): r u sure docker is running?

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

Here I have attached the SS.

And logs from nginx app are here. I think here only some issues are there. Because nginx db logs are looking fine. They are here.

Nginx app logs : https://pastebin.com/GaEtBj14

Nginx db logs : https://pastebin.com/gWi1bYFW

<!-- gh-comment-id:1105672289 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): Here I have attached the SS.  And logs from nginx app are here. I think here only some issues are there. Because nginx db logs are looking fine. They are here. Nginx app logs : https://pastebin.com/GaEtBj14 Nginx db logs : https://pastebin.com/gWi1bYFW

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

Try running the following command on VPS's terminal.
curl -is http://172.19.0.3:81

<!-- gh-comment-id:1105678462 --> @itsKV commented on GitHub (Apr 21, 2022): Try running the following command on VPS's terminal. `curl -is http://172.19.0.3:81`

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

curl -is http://172.19.0.3:81

Nothing happens. Blank response.

<!-- gh-comment-id:1105680101 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): > curl -is http://172.19.0.3:81 Nothing happens. Blank response. 

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

there it is.
Your host is unable to reach your docker container. How could it serve the request on public interface then?

<!-- gh-comment-id:1105683785 --> @itsKV commented on GitHub (Apr 21, 2022): there it is. Your host is unable to reach your docker container. How could it serve the request on public interface then?

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

Try once this command in vps's terminal.
sudo docker exec -it nginx_app_1 curl -is http://172.19.0.3:81

<!-- gh-comment-id:1105685376 --> @itsKV commented on GitHub (Apr 21, 2022): Try once this command in vps's terminal. `sudo docker exec -it nginx_app_1 curl -is http://172.19.0.3:81`

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

there it is. Your host is unable to reach your docker container. How could it serve the request on public interface then?

Ohhh. Okay. So, do we have to fix it on portainer panel or elsewhere..?

<!-- gh-comment-id:1105687153 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): > there it is. Your host is unable to reach your docker container. How could it serve the request on public interface then? Ohhh. Okay. So, do we have to fix it on portainer panel or elsewhere..?

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

Try once this command in vps's terminal. sudo docker exec -it nginx_app_1 curl -is http://172.19.0.3:81

Tried now. Below is the result.

<!-- gh-comment-id:1105687369 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): > Try once this command in vps's terminal. `sudo docker exec -it nginx_app_1 curl -is http://172.19.0.3:81` Tried now. Below is the result. 

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

Is this a problem on portainer..? I have 2 volumes here.

<!-- gh-comment-id:1105696413 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): Is this a problem on portainer..? I have 2 volumes here. 

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

Try once this command in vps's terminal. sudo docker exec -it nginx_app_1 curl -is http://172.19.0.3:81

Tried now. Below is the result.

wait a minute..
This reply shows either there is issue in docker network running between host and containers OR Admin panel is not running on npm container.

Ohhh. Okay. So, do we have to fix it on portainer panel or elsewhere..?

I don't use portainer. So can't say about it. But that can be solved via terminal commands.

<!-- gh-comment-id:1105698919 --> @itsKV commented on GitHub (Apr 21, 2022): > > Try once this command in vps's terminal. `sudo docker exec -it nginx_app_1 curl -is http://172.19.0.3:81` > > Tried now. Below is the result. > >  wait a minute.. This reply shows either there is issue in docker network running between host and containers OR Admin panel is not running on npm container. > Ohhh. Okay. So, do we have to fix it on portainer panel or elsewhere..? I don't use portainer. So can't say about it. But that can be solved via terminal commands.

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

wait a minute..
This reply shows either there is issue in docker network running between host and containers OR Admin panel is not running on npm container.

As earlier I have attached logs for both npm app & db. By looking them, npm app logs are showing issues.

Nginx app logs : https://pastebin.com/GaEtBj14

Nginx db logs : https://pastebin.com/gWi1bYFW

Nginx app logs :-

  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /etc/nginx/conf.d/include/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
❯ Enabling IPV6 in hosts: /data/nginx
  ❯ /data/nginx/proxy_host/2.conf
[4/19/2022] [6:02:36 PM] [Global   ] › ℹ  info      No valid environment variables for database provided, using default SQLite file '/data/database.sqlite'
[4/19/2022] [6:02:37 PM] [Migrate  ] › ℹ  info      Current database version: none
[4/19/2022] [6:02:37 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[4/19/2022] [6:02:37 PM] [Setup    ] › ℹ  info      Logrotate completed.
[4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[4/19/2022] [6:02:37 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[4/19/2022] [6:02:37 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[4/19/2022] [6:02:37 PM] [Global   ] › ℹ  info      Backend PID 242 listening on port 3000 ...
[4/19/2022] [6:02:37 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[4/19/2022] [6:02:37 PM] [SSL      ] › ℹ  info      Renew Complete
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.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted
s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted
s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted
s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted
[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] 01_perms.sh: executing... 
foreground: warning: unable to spawn /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted
foreground: fatal: unable to wait for /var/run/s6/etc/cont-init.d/01_perms.sh: No child process

<!-- gh-comment-id:1105705895 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): > wait a minute.. > This reply shows either there is issue in docker network running between host and containers OR Admin panel is not running on npm container. As earlier I have attached logs for both npm app & db. By looking them, npm app logs are showing issues. Nginx app logs : https://pastebin.com/GaEtBj14 Nginx db logs : https://pastebin.com/gWi1bYFW ``` Nginx app logs :- ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ Enabling IPV6 in hosts: /data/nginx ❯ /data/nginx/proxy_host/2.conf [4/19/2022] [6:02:36 PM] [Global ] › ℹ info No valid environment variables for database provided, using default SQLite file '/data/database.sqlite' [4/19/2022] [6:02:37 PM] [Migrate ] › ℹ info Current database version: none [4/19/2022] [6:02:37 PM] [Setup ] › ℹ info Logrotate Timer initialized [4/19/2022] [6:02:37 PM] [Setup ] › ℹ info Logrotate completed. [4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services... [4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json [4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4 [4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6 [4/19/2022] [6:02:37 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized [4/19/2022] [6:02:37 PM] [SSL ] › ℹ info Renewing SSL certs close to expiry... [4/19/2022] [6:02:37 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized [4/19/2022] [6:02:37 PM] [Global ] › ℹ info Backend PID 242 listening on port 3000 ... [4/19/2022] [6:02:37 PM] [Nginx ] › ℹ info Reloading Nginx [4/19/2022] [6:02:37 PM] [SSL ] › ℹ info Renew Complete 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. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted [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] 01_perms.sh: executing... foreground: warning: unable to spawn /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted foreground: fatal: unable to wait for /var/run/s6/etc/cont-init.d/01_perms.sh: No child process ```

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

I don't use portainer. So can't say about it. But that can be solved via terminal commands.

Ohh. Okay.

<!-- gh-comment-id:1105707006 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): > I don't use portainer. So can't say about it. But that can be solved via terminal commands. Ohh. Okay.

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

The best way is to re-install the npm. That works most of the times.. ;)

<!-- gh-comment-id:1105707826 --> @itsKV commented on GitHub (Apr 21, 2022): The best way is to re-install the npm. That works most of the times.. ;)

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Rajeshsahoo12 commented on GitHub (Apr 21, 2022):

That is where the problem I am facing. I am unable to remove my deployed stacks. As they show limited control. This happened due to update of portainer.

<!-- gh-comment-id:1105709619 --> @Rajeshsahoo12 commented on GitHub (Apr 21, 2022): That is where the problem I am facing. I am unable to remove my deployed stacks. As they show limited control. This happened due to update of portainer. 

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 21, 2022):

This Limited Control error usually occurs when you have deployed some of the containers outside portainer using docker-compose command.
Below command will delete the npm container. After that deploy the fresh npm container using portainer.

sudo docker kill nginx_app_1

Do the same for all the containers showing limited control error and re-deploy them via portainer.

<!-- gh-comment-id:1105715876 --> @itsKV commented on GitHub (Apr 21, 2022): This Limited Control error usually occurs when you have deployed some of the containers outside portainer using _docker-compose_ command. Below command will delete the npm container. After that deploy the fresh npm container using portainer. > sudo docker kill nginx_app_1 Do the same for all the containers showing limited control error and re-deploy them via portainer.

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@itsKV commented on GitHub (Apr 23, 2022):

What's the update?

<!-- gh-comment-id:1107454815 --> @itsKV commented on GitHub (Apr 23, 2022): What's the update?

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@ririko5834 commented on GitHub (May 28, 2022):

I have the same problem

<!-- gh-comment-id:1140257443 --> @ririko5834 commented on GitHub (May 28, 2022): I have the same problem

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@ririko5834 commented on GitHub (May 28, 2022):

Starting proxy-manager_app_1 ... done
Attaching to proxy-manager_app_1
app_1  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
app_1  | [s6-init] ensuring user provided files have correct perms...s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted
app_1  | s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted
app_1  | s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted
app_1  | s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted
app_1  | exited 0.
app_1  | [fix-attrs.d] applying ownership & permissions fixes...
app_1  | [fix-attrs.d] done.
app_1  | [cont-init.d] executing container initialization scripts...
app_1  | [cont-init.d] 01_perms.sh: executing...
app_1  | foreground: warning: unable to spawn /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted
app_1  | foreground: fatal: unable to wait for /var/run/s6/etc/cont-init.d/01_perms.sh: No child process
app_1  |
app_1  | !!!!!
app_1  |  init-stage2 failed.
app_1  | !!!!!

<!-- gh-comment-id:1140257534 --> @ririko5834 commented on GitHub (May 28, 2022): ```docker-compose up Starting proxy-manager_app_1 ... done Attaching to proxy-manager_app_1 app_1 | [s6-init] making user provided files available at /var/run/s6/etc...exited 0. app_1 | [s6-init] ensuring user provided files have correct perms...s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted app_1 | s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted app_1 | s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted app_1 | s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted app_1 | exited 0. app_1 | [fix-attrs.d] applying ownership & permissions fixes... app_1 | [fix-attrs.d] done. app_1 | [cont-init.d] executing container initialization scripts... app_1 | [cont-init.d] 01_perms.sh: executing... app_1 | foreground: warning: unable to spawn /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted app_1 | foreground: fatal: unable to wait for /var/run/s6/etc/cont-init.d/01_perms.sh: No child process app_1 | app_1 | !!!!! app_1 | init-stage2 failed. app_1 | !!!!! ```

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Joweran commented on GitHub (Jun 1, 2022):

I had the same problem, and i managed to get through by giving full permission access to the folder from which i was launching the docker-compose up -d command to run the nginx proxy manager stack : sudo chmod -R 777 ./

<!-- gh-comment-id:1143296193 --> @Joweran commented on GitHub (Jun 1, 2022): I had the same problem, and i managed to get through by giving full permission access to the folder from which i was launching the docker-compose up -d command to run the nginx proxy manager stack : sudo chmod -R 777 ./

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Amarildoo commented on GitHub (Jul 1, 2022):

I have the same problem, using Oracle Cloud, Ubuntu 20.04.
Updated using apt update && apt upgrade.
Rebooted the system, and nginx-proxy-manager was not working.

Container was started using:
docker run -d --name=nginx-proxy-manager --restart unless-stopped --network nginxproxymanager -p 80:80 -p 81:81 -p 443:443 -v "$PWD/data":/data -v "$PWD/letsencrypt":/etc/letsencrypt jc21/nginx-proxy-manager:latest

Firewall in Oracle Cloud and in Host (using iptables) is unchanged (ports are opened).

Error logs:

2022-07-01T13:46:20.225479708Z s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted
2022-07-01T13:46:20.225494388Z s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted
2022-07-01T13:46:20.226741067Z s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted
2022-07-01T13:46:20.226835467Z s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted
2022-07-01T13:46:20.241075344Z [s6-init] ensuring user provided files have correct perms...exited 0.
2022-07-01T13:46:20.242111744Z [fix-attrs.d] applying ownership & permissions fixes...
2022-07-01T13:46:20.243111904Z [fix-attrs.d] done.
2022-07-01T13:46:20.243740544Z [cont-init.d] executing container initialization scripts...
2022-07-01T13:46:20.244711223Z [cont-init.d] 01_perms.sh: executing...
2022-07-01T13:46:20.244981503Z foreground: warning: unable to spawn /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted
2022-07-01T13:46:20.244995543Z foreground: fatal: unable to wait for /var/run/s6/etc/cont-init.d/01_perms.sh: No child process
2022-07-01T13:46:20.247153503Z
2022-07-01T13:46:20.247166703Z !!!!!
2022-07-01T13:46:20.247169863Z init-stage2 failed.
2022-07-01T13:46:20.247172423Z !!!!!

---

'Fixed' by reinstalling N.P.M.
sudo docker rm -f nginx-proxy-manager
sudo docker image rm <image-id>
docker run -d --name=nginx-proxy-manager --restart unless-stopped --network nginxproxymanager -p 80:80 -p 81:81 -p 443:443 -v "$PWD/data":/data -v "$PWD/letsencrypt":/etc/letsencrypt jc21/nginx-proxy-manager:latest

<!-- gh-comment-id:1172374637 --> @Amarildoo commented on GitHub (Jul 1, 2022): I have the same problem, using Oracle Cloud, Ubuntu 20.04. Updated using `apt update && apt upgrade`. Rebooted the system, and nginx-proxy-manager was not working. Container was started using: `docker run -d --name=nginx-proxy-manager --restart unless-stopped --network nginxproxymanager -p 80:80 -p 81:81 -p 443:443 -v "$PWD/data":/data -v "$PWD/letsencrypt":/etc/letsencrypt jc21/nginx-proxy-manager:latest` Firewall in Oracle Cloud and in Host (using iptables) is unchanged (ports are opened). Error logs: > 2022-07-01T13:46:20.225479708Z s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted > 2022-07-01T13:46:20.225494388Z s6-chown: fatal: unable to chown /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted > 2022-07-01T13:46:20.226741067Z s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_s6-secret-init.sh: Operation not permitted > 2022-07-01T13:46:20.226835467Z s6-chmod: fatal: unable to change mode of /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted > 2022-07-01T13:46:20.241075344Z [s6-init] ensuring user provided files have correct perms...exited 0. > 2022-07-01T13:46:20.242111744Z [fix-attrs.d] applying ownership & permissions fixes... > 2022-07-01T13:46:20.243111904Z [fix-attrs.d] done. > 2022-07-01T13:46:20.243740544Z [cont-init.d] executing container initialization scripts... > 2022-07-01T13:46:20.244711223Z [cont-init.d] 01_perms.sh: executing... > 2022-07-01T13:46:20.244981503Z foreground: warning: unable to spawn /var/run/s6/etc/cont-init.d/01_perms.sh: Operation not permitted > 2022-07-01T13:46:20.244995543Z foreground: fatal: unable to wait for /var/run/s6/etc/cont-init.d/01_perms.sh: No child process > 2022-07-01T13:46:20.247153503Z > 2022-07-01T13:46:20.247166703Z !!!!! > 2022-07-01T13:46:20.247169863Z init-stage2 failed. > 2022-07-01T13:46:20.247172423Z !!!!! --- 'Fixed' by reinstalling N.P.M. `sudo docker rm -f nginx-proxy-manager` `sudo docker image rm <image-id>` `docker run -d --name=nginx-proxy-manager --restart unless-stopped --network nginxproxymanager -p 80:80 -p 81:81 -p 443:443 -v "$PWD/data":/data -v "$PWD/letsencrypt":/etc/letsencrypt jc21/nginx-proxy-manager:latest`

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@CyberAdmin97 commented on GitHub (Sep 29, 2022):

any updates ?
i have the same issue on AWS

<!-- gh-comment-id:1262182500 --> @CyberAdmin97 commented on GitHub (Sep 29, 2022): any updates ? i have the same issue on AWS

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@0x10-z commented on GitHub (Dec 20, 2022):

Same issue on AWS Linux 2 machine

<!-- gh-comment-id:1359423513 --> @0x10-z commented on GitHub (Dec 20, 2022): Same issue on AWS Linux 2 machine

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@ChildLearningClub commented on GitHub (Mar 29, 2023):

Make sure your Nginx Proxy Manager image is current:

docker run -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once.

This was my issue.
Note: the code snippet above will update everything not only your Nginx Proxy Manager.

EDIT: Okay, looks like there is actually two issue that people might be having. Initially I was not able to even reach the login interface, that was solved with updating the image as mentioned above. Once the image was updated and the login interface was showing I was unable to login without as @Joweran says changing the folders permissions to 777.

Version 2.10.1

<!-- gh-comment-id:1487785669 --> @ChildLearningClub commented on GitHub (Mar 29, 2023): Make sure your Nginx Proxy Manager image is current: `docker run -v /var/run/docker.sock:/var/run/docker.sock containrrr/watchtower --run-once`. This was my issue. Note: the code snippet above will update everything not only your Nginx Proxy Manager. EDIT: Okay, looks like there is actually two issue that people might be having. Initially I was not able to even reach the login interface, that was solved with updating the image as mentioned above. Once the image was updated and the login interface was showing I was unable to login without as @Joweran says changing the folders permissions to 777. Version 2.10.1

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@parthdevloper commented on GitHub (Oct 7, 2023):

If you are using AWS Lightsail , you need to go to:

IPv4 networking

& then add a new rule to enable port 81:

<!-- gh-comment-id:1751818395 --> @parthdevloper commented on GitHub (Oct 7, 2023): If you are using AWS Lightsail , you need to go to: > IPv4 networking & then add a new rule to enable port `81`: <img width="798" alt="image" src="https://github.com/NginxProxyManager/nginx-proxy-manager/assets/58413215/8eabacaa-e078-4801-8e2e-d5b99bb060eb"> <img width="1049" alt="image" src="https://github.com/NginxProxyManager/nginx-proxy-manager/assets/58413215/14e0c78c-5305-4fbb-96c4-ddc3d62ee15a">

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Apr 30, 2024):

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

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

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@Nightwalker83 commented on GitHub (Dec 2, 2024):

I am having the same problem too both through localhost and the servers actual ip.
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4197

<!-- gh-comment-id:2510386388 --> @Nightwalker83 commented on GitHub (Dec 2, 2024): I am having the same problem too both through localhost and the servers actual ip. https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4197

kerem commented 2026-02-26 07:31:09 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Aug 16, 2025):

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

<!-- gh-comment-id:3193215678 --> @github-actions[bot] commented on GitHub (Aug 16, 2025): 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#1458

No description provided.