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

[GH-ISSUE #3091] Error restarting sed couldn't open temporary file permission denied #2096

New issue

Closed

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

kerem commented

2026-02-26 07:34:00 +03:00

Owner

Originally created by @codethought on GitHub (Jul 31, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3091

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

Error restarting sed couldn't open temporary file permission denied

Nginx Proxy Manager Version

2.10.3 (via Docker Compose)

To Reproduce
Steps to reproduce the behavior:

Go to main proxy page and login with the admin user
change the user and create new password, etc..
Select Hosts | Add Proxy Host
Create a proxy host with your domain to an machine in your network.
Click Save
Restart nginx-proxy-manager
Error

Expected behavior

To allow a restart and to create a proxy hosts successfully.

Screenshots

filerun8-proxy-1  | ❯ Configuring npm user ...
filerun8-proxy-1  | 0
filerun8-proxy-1  | usermod: no changes
filerun8-proxy-1  | ❯ Configuring npm group ...
filerun8-proxy-1  | ❯ Checking paths ...
filerun8-proxy-1  | ❯ Setting ownership ...
filerun8-proxy-1  | ❯ Dynamic resolvers ...
filerun8-proxy-1  | ❯ IPv6 ...
filerun8-proxy-1  | Enabling IPV6 in hosts in: /etc/nginx/conf.d
filerun8-proxy-1  | - /etc/nginx/conf.d/include/force-ssl.conf
filerun8-proxy-1  | - /etc/nginx/conf.d/include/proxy.conf
filerun8-proxy-1  | - /etc/nginx/conf.d/include/assets.conf
filerun8-proxy-1  | - /etc/nginx/conf.d/include/ssl-ciphers.conf
filerun8-proxy-1  | - /etc/nginx/conf.d/include/ip_ranges.conf
filerun8-proxy-1  | - /etc/nginx/conf.d/include/block-exploits.conf
filerun8-proxy-1  | - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
filerun8-proxy-1  | - /etc/nginx/conf.d/include/resolvers.conf
filerun8-proxy-1  | - /etc/nginx/conf.d/default.conf
filerun8-proxy-1  | - /etc/nginx/conf.d/production.conf
filerun8-proxy-1  | Enabling IPV6 in hosts in: /data/nginx
filerun8-proxy-1  | - /data/nginx/proxy_host/1.conf
filerun8-proxy-1  | sed: couldn't open temporary file /data/nginx/proxy_host/sedN25JQv: Permission denied
filerun8-proxy-1  | s6-rc: warning: unable to start service prepare: command exited 4
filerun8-proxy-1  | /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.

Operating System

Mac M1, Colima, Docker

Additional context

Originally created by @codethought on GitHub (Jul 31, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3091  **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** Error restarting sed couldn't open temporary file permission denied **Nginx Proxy Manager Version**  2.10.3 (via Docker Compose) **To Reproduce** Steps to reproduce the behavior: 1. Go to main proxy page and login with the admin user 2. change the user and create new password, etc.. 3. Select Hosts | Add Proxy Host 4. Create a proxy host with your domain to an machine in your network. 5. Click Save 6. Restart nginx-proxy-manager 7. Error **Expected behavior**  To allow a restart and to create a proxy hosts successfully. **Screenshots**  ``` filerun8-proxy-1 | ❯ Configuring npm user ... filerun8-proxy-1 | 0 filerun8-proxy-1 | usermod: no changes filerun8-proxy-1 | ❯ Configuring npm group ... filerun8-proxy-1 | ❯ Checking paths ... filerun8-proxy-1 | ❯ Setting ownership ... filerun8-proxy-1 | ❯ Dynamic resolvers ... filerun8-proxy-1 | ❯ IPv6 ... filerun8-proxy-1 | Enabling IPV6 in hosts in: /etc/nginx/conf.d filerun8-proxy-1 | - /etc/nginx/conf.d/include/force-ssl.conf filerun8-proxy-1 | - /etc/nginx/conf.d/include/proxy.conf filerun8-proxy-1 | - /etc/nginx/conf.d/include/assets.conf filerun8-proxy-1 | - /etc/nginx/conf.d/include/ssl-ciphers.conf filerun8-proxy-1 | - /etc/nginx/conf.d/include/ip_ranges.conf filerun8-proxy-1 | - /etc/nginx/conf.d/include/block-exploits.conf filerun8-proxy-1 | - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf filerun8-proxy-1 | - /etc/nginx/conf.d/include/resolvers.conf filerun8-proxy-1 | - /etc/nginx/conf.d/default.conf filerun8-proxy-1 | - /etc/nginx/conf.d/production.conf filerun8-proxy-1 | Enabling IPV6 in hosts in: /data/nginx filerun8-proxy-1 | - /data/nginx/proxy_host/1.conf filerun8-proxy-1 | sed: couldn't open temporary file /data/nginx/proxy_host/sedN25JQv: Permission denied filerun8-proxy-1 | s6-rc: warning: unable to start service prepare: command exited 4 filerun8-proxy-1 | /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. ``` **Operating System**  Mac M1, Colima, Docker **Additional context**

kerem

2026-02-26 07:34:00 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:34:00 +03:00

Author

Owner

@gotzlotz commented on GitHub (Aug 6, 2023):

Getting the same error when I restart.

@gotzlotz commented on GitHub (Aug 6, 2023): Getting the same error when I restart.

kerem commented

2026-02-26 07:34:00 +03:00

Author

Owner

@Antergosgeek commented on GitHub (Aug 25, 2023):

Any idea what it could be? I have the exact same thing happening. When I get lucky it runs but made the mistake to stop the container and now the issue is back and I can’t get it to start anymore

@Antergosgeek commented on GitHub (Aug 25, 2023): Any idea what it could be? I have the exact same thing happening. When I get lucky it runs but made the mistake to stop the container and now the issue is back and I can’t get it to start anymore

kerem commented

2026-02-26 07:34:01 +03:00

Author

Owner

@f1ynng8 commented on GitHub (Nov 22, 2023):

@Antergosgeek a temporary solution is change the file sharing from VirtioFS to gRPC FUSE in Docker Desktop for Mac. Details here: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3343

@f1ynng8 commented on GitHub (Nov 22, 2023): @Antergosgeek a temporary solution is change the file sharing from VirtioFS to gRPC FUSE in Docker Desktop for Mac. Details here: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3343

kerem commented

2026-02-26 07:34:01 +03:00

Author

Owner

@Antergosgeek commented on GitHub (Apr 25, 2024):

Thank you! Sorry been a while since I looked!

@Antergosgeek commented on GitHub (Apr 25, 2024): Thank you! Sorry been a while since I looked!

kerem commented

2026-02-26 07:34:01 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 5, 2024):

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

@github-actions[bot] commented on GitHub (Nov 5, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:34:01 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 28, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Nov 28, 2025): Issue was closed due to inactivity.

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

No description provided.

Rows
Columns