NginxProxyManager / NginxProxyManager/nginx-proxy-manager

Could not delete file on 2.11.1 & 2.10.4

Open
#3,647 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug stale
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at Hosts > Add host and reproduce the Docker log's unlink ENOENT message, then compare the generated /data/nginx/proxy_host/84.conf with the resulting site behavior. Done means a newly added host displays its site without the 400/SSL problem or file-deletion error.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, nginx
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.