starred/nginx-proxy-manager-NginxProxyManager
1
0
Fork 0
mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00
Code Issues 937 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #3647] Could not delete file on 2.11.1 & 2.10.4 #2415

New issue
Open
opened 2026-02-26 07:35:28 +03:00 by kerem · 14 comments
kerem commented 2026-02-26 07:35:28 +03:00
Owner
Copy link

Originally created by @peterge-misoft on GitHub (Mar 22, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3647

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

Originally created by @peterge-misoft on GitHub (Mar 22, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3647 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **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** <!-- A clear and concise description of what the bug is. --> 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** <!-- What version of Nginx Proxy Manager is reported on the login page? --> 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** <!-- A clear and concise description of what you expected to happen. --> Add a new host and display its site. **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> debian 11 lxc **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@peterge-misoft commented on GitHub (Mar 22, 2024):

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

<!-- gh-comment-id:2015527525 --> @peterge-misoft commented on GitHub (Mar 22, 2024): 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
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@peterge-misoft commented on GitHub (Mar 26, 2024):

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

<!-- gh-comment-id:2020142637 --> @peterge-misoft commented on GitHub (Mar 26, 2024): Downgraded to 2.10.4 bc of could not delete file error :(
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@thebino commented on GitHub (Apr 12, 2024):

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
<!-- gh-comment-id:2051427095 --> @thebino commented on GitHub (Apr 12, 2024): 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 ```
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@peterge-misoft commented on GitHub (Apr 12, 2024):

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

<!-- gh-comment-id:2051526777 --> @peterge-misoft commented on GitHub (Apr 12, 2024): I already fount this. But the could not delete file error persited, thats why I downgraded to 2.10.4.
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@XiovV commented on GitHub (Apr 12, 2024):

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  | }
<!-- gh-comment-id:2052453896 --> @XiovV commented on GitHub (Apr 12, 2024): 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 | } ```
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@IUxp8xz9 commented on GitHub (Apr 14, 2024):

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.

<!-- gh-comment-id:2053941272 --> @IUxp8xz9 commented on GitHub (Apr 14, 2024): 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.
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@focher commented on GitHub (Apr 23, 2024):

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.

<!-- gh-comment-id:2071238684 --> @focher commented on GitHub (Apr 23, 2024): 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.
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

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

relates to #3678

<!-- gh-comment-id:2077140200 --> @s0mm3rb commented on GitHub (Apr 25, 2024): relates to #3678
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Oct 26, 2024):

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

<!-- gh-comment-id:2439175000 --> @github-actions[bot] commented on GitHub (Oct 26, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@wakawakaaa commented on GitHub (Nov 19, 2024):

same issue. nginx proxy manager is broken v2.12.1

<!-- gh-comment-id:2486680983 --> @wakawakaaa commented on GitHub (Nov 19, 2024): same issue. nginx proxy manager is broken v2.12.1
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@nnasirzada commented on GitHub (Nov 23, 2024):

+1 v2.12.1

<!-- gh-comment-id:2495497788 --> @nnasirzada commented on GitHub (Nov 23, 2024): +1 v2.12.1
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@JulesRenz commented on GitHub (Feb 10, 2025):

+1 v2.12.3

Edit: ok, I have the impression, that the error message is misleading. I was able to fix the issue for me but the error was unrelated:
I'm moving servers and forgot to update the DNS record, so I assume, that when NPM tried to get the certificate from Let'sEncrypt, it failed.

Here is the log of the failed run:

[2/10/2025] [7:48:50 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/5.conf
[2/10/2025] [7:48:50 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/5.conf.err
[2/10/2025] [7:48:50 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
  "errno": -2,
  "code": "ENOENT",
  "syscall": "unlink",
  "path": "/data/nginx/proxy_host/5.conf.err"
}
[2/10/2025] [7:48:50 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[2/10/2025] [7:48:50 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[2/10/2025] [7:48:50 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -s reload
[2/10/2025] [7:48:55 PM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #8: subdomain.domain.com
[2/10/2025] [7:48:55 PM] [SSL      ] › ℹ  info      Command: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-8" --agree-tos --authenticator webroot --email 'myuser@domain.com' --preferred-challenges "dns,http" --domains "subdomain.domain.com" 
[2/10/2025] [7:48:55 PM] [Global   ] › ⬤  debug     CMD: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-8" --agree-tos --authenticator webroot --email 'myuser@domain.com' --preferred-challenges "dns,http" --domains "subdomain.domain.com" 
[2/10/2025] [7:48:58 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/temp/letsencrypt_8.conf
[2/10/2025] [7:48:58 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[2/10/2025] [7:48:58 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[2/10/2025] [7:48:58 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -s reload
[2/10/2025] [7:48:58 PM] [Express  ] › ⚠  warning   Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

And here a couple of minutes later after changing the DNS settings at my provider:

[2/10/2025] [7:55:13 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/5.conf
[2/10/2025] [7:55:13 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/5.conf.err
[2/10/2025] [7:55:13 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
  "errno": -2,
  "code": "ENOENT",
  "syscall": "unlink",
  "path": "/data/nginx/proxy_host/5.conf.err"
}
[2/10/2025] [7:55:13 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[2/10/2025] [7:55:13 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[2/10/2025] [7:55:13 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -s reload
[2/10/2025] [7:55:18 PM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #9: subdomain.domain.com
[2/10/2025] [7:55:18 PM] [SSL      ] › ℹ  info      Command: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-9" --agree-tos --authenticator webroot --email 'myuser@domain.com' --preferred-challenges "dns,http" --domains "subdomain.domain.com" 
[2/10/2025] [7:55:18 PM] [Global   ] › ⬤  debug     CMD: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-9" --agree-tos --authenticator webroot --email 'myuser@domain.com' --preferred-challenges "dns,http" --domains "subdomain.domain.com" 
[2/10/2025] [7:55:28 PM] [SSL      ] › ✔  success   Requesting a certificate for subdomain.domain.com

Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/npm-9/fullchain.pem
Key is saved at:         /etc/letsencrypt/live/npm-9/privkey.pem
This certificate expires on 2025-05-11.
These files will be updated when the certificate renews.
NEXT STEPS:
- The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https://certbot.org/renewal-setup for instructions.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If you like Certbot, please consider supporting our work by:
 * Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
 * Donating to EFF:                    https://eff.org/donate-le
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[2/10/2025] [7:55:28 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/temp/letsencrypt_9.conf
[2/10/2025] [7:55:28 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[2/10/2025] [7:55:28 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[2/10/2025] [7:55:28 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -s reload
[2/10/2025] [7:55:28 PM] [Global   ] › ⬤  debug     CMD: openssl x509 -in /etc/letsencrypt/live/npm-9/fullchain.pem -subject -noout
[2/10/2025] [7:55:28 PM] [Global   ] › ⬤  debug     CMD: openssl x509 -in /etc/letsencrypt/live/npm-9/fullchain.pem -issuer -noout
[2/10/2025] [7:55:28 PM] [Global   ] › ⬤  debug     CMD: openssl x509 -in /etc/letsencrypt/live/npm-9/fullchain.pem -dates -noout
[2/10/2025] [7:55:28 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[2/10/2025] [7:55:28 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/5.conf
[2/10/2025] [7:55:28 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[2/10/2025] [7:55:28 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[2/10/2025] [7:55:28 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[2/10/2025] [7:55:28 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -s reload

In both cases, NPM complains that the file could not be deleted.

Maybe this helps somebody out there :)

<!-- gh-comment-id:2649089060 --> @JulesRenz commented on GitHub (Feb 10, 2025): +1 v2.12.3 **Edit:** ok, I have the impression, that the error message is misleading. I was able to fix the issue for me but the error was unrelated: I'm moving servers and forgot to update the DNS record, so I assume, that when NPM tried to get the certificate from Let'sEncrypt, it failed. Here is the log of the failed run: ``` [2/10/2025] [7:48:50 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/5.conf [2/10/2025] [7:48:50 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/5.conf.err [2/10/2025] [7:48:50 PM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/5.conf.err" } [2/10/2025] [7:48:50 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [2/10/2025] [7:48:50 PM] [Nginx ] › ℹ info Reloading Nginx [2/10/2025] [7:48:50 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [2/10/2025] [7:48:55 PM] [SSL ] › ℹ info Requesting Let'sEncrypt certificates for Cert #8: subdomain.domain.com [2/10/2025] [7:48:55 PM] [SSL ] › ℹ info Command: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-8" --agree-tos --authenticator webroot --email 'myuser@domain.com' --preferred-challenges "dns,http" --domains "subdomain.domain.com" [2/10/2025] [7:48:55 PM] [Global ] › ⬤ debug CMD: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-8" --agree-tos --authenticator webroot --email 'myuser@domain.com' --preferred-challenges "dns,http" --domains "subdomain.domain.com" [2/10/2025] [7:48:58 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/temp/letsencrypt_8.conf [2/10/2025] [7:48:58 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [2/10/2025] [7:48:58 PM] [Nginx ] › ℹ info Reloading Nginx [2/10/2025] [7:48:58 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [2/10/2025] [7:48:58 PM] [Express ] › ⚠ warning Saving debug log to /tmp/letsencrypt-log/letsencrypt.log Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details. ``` And here a couple of minutes later after changing the DNS settings at my provider: ``` [2/10/2025] [7:55:13 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/5.conf [2/10/2025] [7:55:13 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/5.conf.err [2/10/2025] [7:55:13 PM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/5.conf.err" } [2/10/2025] [7:55:13 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [2/10/2025] [7:55:13 PM] [Nginx ] › ℹ info Reloading Nginx [2/10/2025] [7:55:13 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [2/10/2025] [7:55:18 PM] [SSL ] › ℹ info Requesting Let'sEncrypt certificates for Cert #9: subdomain.domain.com [2/10/2025] [7:55:18 PM] [SSL ] › ℹ info Command: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-9" --agree-tos --authenticator webroot --email 'myuser@domain.com' --preferred-challenges "dns,http" --domains "subdomain.domain.com" [2/10/2025] [7:55:18 PM] [Global ] › ⬤ debug CMD: certbot certonly --config '/etc/letsencrypt.ini' --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-9" --agree-tos --authenticator webroot --email 'myuser@domain.com' --preferred-challenges "dns,http" --domains "subdomain.domain.com" [2/10/2025] [7:55:28 PM] [SSL ] › ✔ success Requesting a certificate for subdomain.domain.com Successfully received certificate. Certificate is saved at: /etc/letsencrypt/live/npm-9/fullchain.pem Key is saved at: /etc/letsencrypt/live/npm-9/privkey.pem This certificate expires on 2025-05-11. These files will be updated when the certificate renews. NEXT STEPS: - The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See https://certbot.org/renewal-setup for instructions. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - If you like Certbot, please consider supporting our work by: * Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate * Donating to EFF: https://eff.org/donate-le - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - [2/10/2025] [7:55:28 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/temp/letsencrypt_9.conf [2/10/2025] [7:55:28 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [2/10/2025] [7:55:28 PM] [Nginx ] › ℹ info Reloading Nginx [2/10/2025] [7:55:28 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [2/10/2025] [7:55:28 PM] [Global ] › ⬤ debug CMD: openssl x509 -in /etc/letsencrypt/live/npm-9/fullchain.pem -subject -noout [2/10/2025] [7:55:28 PM] [Global ] › ⬤ debug CMD: openssl x509 -in /etc/letsencrypt/live/npm-9/fullchain.pem -issuer -noout [2/10/2025] [7:55:28 PM] [Global ] › ⬤ debug CMD: openssl x509 -in /etc/letsencrypt/live/npm-9/fullchain.pem -dates -noout [2/10/2025] [7:55:28 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [2/10/2025] [7:55:28 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/5.conf [2/10/2025] [7:55:28 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [2/10/2025] [7:55:28 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [2/10/2025] [7:55:28 PM] [Nginx ] › ℹ info Reloading Nginx [2/10/2025] [7:55:28 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload ``` In both cases, NPM complains that the file could not be deleted. Maybe this helps somebody out there :)
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@isomeruk commented on GitHub (Mar 6, 2025):

In case this helps anyone else facing this issue - I was getting the same error and the status reporting as 'Offline'. In my case it ended up being a typo in the 'Advanced' section in the proxy config. Fix the typo, host back online!

My guess is that the "Could not delete" error is actually a non-event and the real problem is that because of the typo it never actually created the file in the first place which, if that is the case, could do with some better logging.

<!-- gh-comment-id:2703381803 --> @isomeruk commented on GitHub (Mar 6, 2025): In case this helps anyone else facing this issue - I was getting the same error and the status reporting as 'Offline'. In my case it ended up being a typo in the 'Advanced' section in the proxy config. Fix the typo, host back online! My guess is that the "Could not delete" error is actually a non-event and the real problem is that because of the typo it never actually created the file in the first place which, if that is the case, could do with some better logging.
kerem commented 2026-02-26 07:35:29 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Oct 4, 2025):

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

<!-- gh-comment-id:3367761283 --> @github-actions[bot] commented on GitHub (Oct 4, 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
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#2415
No description provided.