Could not delete file on 2.11.1 & 2.10.4

[peterge-misoft]

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

Everything worked just fine after i upgraded to 2.11.1 last week. But when I add a new host, this message shows up in docker logs -f:

[3/22/2024] [1:31:28 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
  "errno": -2,
  "syscall": "unlink",
  "code": "ENOENT",
  "path": "/data/nginx/proxy_host/84.conf"
}

I went down to 2.10.4 and the same thing happened.

cat data/nginx/proxy_host/84.conf 
# ------------------------------------------------------------
# hassio.misoft.local
# ------------------------------------------------------------

server {
  set $forward_scheme http;
  set $server         "172.16.1.64";
  set $port           8123;
...

The file does show the content that i just added as new host.
When I visit the site I just see 400: Bad Request on 2.11.1, a SSL warning shows up on 2.10.4 but the docker logs message is the same.

Nginx Proxy Manager Version

2.11.1

To Reproduce
Steps to reproduce the behavior:

1. Go to Hosts
2. Click on Add host
3. Enter details
4. See error in docker logs -f

Expected behavior

Add a new host and display its site.

Screenshots

Operating System

debian 11 lxc

Additional context

[peterge-misoft]

I was facing the same error as https://community.home-assistant.io/t/getting-400-when-accessing-home-assistant-through-a-reverse-proxy-dockerized-nginx/373526

[peterge-misoft]

Downgraded to 2.10.4 bc of could not delete file error :(

[thebino]

You need to add the reverse proxy to home-assistant in the configuration file.
https://www.home-assistant.io/integrations/http#reverse-proxies

http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 10.0.0.200      # Add the IP address of the proxy server

[peterge-misoft]

I already fount this. But the could not delete file error persited, thats why I downgraded to 2.10.4.

[XiovV]

Downgraded to 2.10.4, still getting the same issue:

nodeproxymanager-app-1  | [4/12/2024] [8:05:32 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
nodeproxymanager-app-1  |   "errno": -2,
nodeproxymanager-app-1  |   "syscall": "unlink",
nodeproxymanager-app-1  |   "code": "ENOENT",
nodeproxymanager-app-1  |   "path": "/data/nginx/proxy_host/1.conf"
nodeproxymanager-app-1  | }

[IUxp8xz9]

This hit me as well. As soon as I try to edit a proxy host, this error pops up and the host is no longer reachable.
I checked on the file system and the files are correctly being deleted, I even created some empty dummy files named according to the error and they are correctly deleted. Looks like NPM is not getting correct feedback on the deletion.

Reverting back to 2.10.4 did not make the error go away but did make my site come back online. Reverting back to 2.9.22 made everything work again.

[focher]

I got the same issue even after downgrading to 2.9.22

As a test, I completely rebuilt my nginx configuration. It's only a single proxy host that gets this error and won't go online. However, I removed all of the Custom Locations and saved. This allowed it to enter Enabled state. The delete error went away. I added four Custom Locations, adding them individually and saving before adding the next. Still no delete error and eventually it was running again.

[s0mm3rb]

relates to #3678

[github-actions]

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

[wakawakaaa]

same issue. nginx proxy manager is broken v2.12.1

[nnasirzada]

+1 v2.12.1