nginx-proxy-manager: basically the application is broken.
I just wasted more than one hour trying to update my proxies.
I kept getting the same error again and again and again. Could not delete file. This is the absolutely basic functionality that should be offered by the nginx proxy manager right? I would expect a proxy manager to be able to edit the proxies.
But it basically can’t do this basic thing. This added to the even worse handling of the SSL certificates led me to the conclusion that I need a better solution.
So to anyone reading this: look for other solutions: caddy, traefik, whatever. Do not waste time here.
And to the developers, please do the world a favor and archive this project.
[1/24/2024] [5:07:50 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/14.conf
[1/24/2024] [5:07:50 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;"
[1/24/2024] [5:07:50 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/14.conf
[1/24/2024] [5:07:50 PM] [Nginx ] › ⬤ debug Could not delete file: {
"errno": -2,
"code": "ENOENT",
"syscall": "unlink",
"path": "/data/nginx/proxy_host/14.conf"
}
[1/24/2024] [5:07:50 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/14.conf.err
[1/24/2024] [5:07:50 PM] [Nginx ] › ⬤ debug Could not delete file: {
"errno": -2,
"code": "ENOENT",
"syscall": "unlink",
"path": "/data/nginx/proxy_host/14.conf.err"
}
[1/24/2024] [5:07:50 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;"
[1/24/2024] [5:07:51 PM] [Nginx ] › ℹ info Reloading Nginx
[1/24/2024] [5:07:51 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload
[1/24/2024] [5:07:57 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;"
[1/24/2024] [5:07:57 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/14.conf
[1/24/2024] [5:07:57 PM] [Nginx ] › ⬤ debug Could not delete file: {
"errno": -2,
"code": "ENOENT",
"syscall": "unlink",
"path": "/data/nginx/proxy_host/14.conf"
}
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?- Yes : image: jc21/nginx-proxy-manager:2.11.1
- Are you sure you’re not using someone else’s docker image?
- Yes
- Have you searched for similar issues (both open and closed)?
- Yes. There are open and it seems that the team does not care.
Describe the bug
try to edit a proxy. It is impossible. Check the logs, see the result above.
Nginx Proxy Manager Version
image: jc21/nginx-proxy-manager:2.11.1
To Reproduce Steps to reproduce the behavior:
- Go to ‘…’
- Click on ‘…’
- Scroll down to ‘…’
- See error
Expected behavior
Maybe it should work?
Screenshots
Operating System
Additional context
About this issue
- Original URL
- State: open
- Created 5 months ago
- Reactions: 12
- Comments: 27
i feel your pain. Lately I did some research for a replacement and I think this one looks promising. I just leave the link in case it might be an option for you guys.
Webseite: https://zoraxy.arozos.com/
Github: https://github.com/tobychui/zoraxy
Same experience, downgraded to
2.9.22. Seems to work better but I’m considering migrating away as NPM requires more maintenance than plain NGINX 😕Hello, I have the same error as the original post, but it seems to only affect hosts that have custom location in use. After deleting the custom locations the proxy host works fine again.
Despite that, it quite literally does not work on a single machine that any possible target user wants to put it on. Moreover, this is still the case 3 whole months after this application breaking issue has been opened. Worse yet is the fact that despite the developers ‘maintaining’ the project they haven’t responded to any of these issues. A project without support for its outstanding issues that make it unusable, is dead. A project that is unusable and has no plans to fix itself in the near future, is dead.
I get where you’re coming from, but the latest release is just from 2 months ago and the latest commits date back to 4 weeks ago. I think this project is just a victim of it’s own success, which is not manageable by a single person.
+1
@bkilinc have you noticed the last 50+ issues? many point to the same problem. One issue says that basically the last x Versions are not working. The application is simply not working and evidently the new commits are not fixing the issues, so yes, you can commit and commit, does not mean that it is a working or quality application. It just mean that someone is writing some sort of code. Could be an update to the README.
Pulls… I can pull easily 10 images a day. A k8s cluster will pull 100s if not 1000s a day…
I strongly recommend to look for other solutions. I also worked with traefik and never experience such horrible issues.
@jc21 can you archive the application? it is not maintained and is not working anymore.
though it has worked well for me but i too face the same problem hate to migrate though
Update: I could solve it through deleting the problematic entry and recreating it. From my (users) point of view nothing changed but it seems that something went corrupt under the hood.
Still it is very sad because when debugging is almost impossible, you can just hope to never encounter bugs.