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 #3763] NPM Broken? Bad underlying tool sets? #2481

New issue

Closed

opened 2026-02-26 07:35:43 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:35:43 +03:00

Owner

Originally created by @sdh91 on GitHub (May 18, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3763

It appears that NPM is broken as a whole. I was on 2.10.3 and have been running it for a while with nearly no issues. My certificates stopped renewing. I have tried everything from upgrading to doing a full new instance and still cannot get certificates to be issued. Even with DNS challenge with Cloudflare. I'm not sure what is going on but as a whole this project appears to be broken and no one seems to be getting any real information. Work arounds are not working in my case.

Can we please get some sort of update on this? What has happened that has caused this to break? I feel this is more of a certbot issue but not sure if I'm being honest.

Originally created by @sdh91 on GitHub (May 18, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3763 It appears that NPM is broken as a whole. I was on 2.10.3 and have been running it for a while with nearly no issues. My certificates stopped renewing. I have tried everything from upgrading to doing a full new instance and still cannot get certificates to be issued. Even with DNS challenge with Cloudflare. I'm not sure what is going on but as a whole this project appears to be broken and no one seems to be getting any real information. Work arounds are not working in my case. Can we please get some sort of update on this? What has happened that has caused this to break? I feel this is more of a certbot issue but not sure if I'm being honest.

kerem

2026-02-26 07:35:43 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:35:44 +03:00

Author

Owner

@jc21 commented on GitHub (May 20, 2024):

No NPM is not broken, however as you've probably determined, the certbot for cloudflare was.

As you were using a NPM version over a year old, there have been significant upgrades to certbot since then. The CI tests that it can install the plugins but it doesn't test each one, it's just not feasible.

Please try using the github-develop docker image tag to get the fix from the PR, at least until 2.11.3 is released. Then feel free to close this issue if it works for you.

@jc21 commented on GitHub (May 20, 2024): No NPM is not broken, however as you've probably determined, the certbot for cloudflare was. As you were using a NPM version over a year old, there have been significant upgrades to certbot since then. The CI tests that it can install the plugins but it doesn't test each one, it's just not feasible. Please try using the `github-develop` docker image tag to get the fix from the PR, at least until `2.11.3` is released. Then feel free to close this issue if it works for you.

kerem commented

2026-02-26 07:35:44 +03:00

Author

Owner

@sdh91 commented on GitHub (May 20, 2024):

I wasn't using DNS API validation. I have used HTTP validation for as long as I've used NPM. I did try it as a testing function, but that was it.

I stayed on a version that was working. Didn't see any reason to move as there wasn't a compelling reason to upgrade. I had been burned before by upgrading and then losing all my configuration.

I'm not the only one that has suddenly had thier certificates stop renewing. Attempt to manually renew and the only message is "Internal Error". That is vague and not helpful to anyone.

@sdh91 commented on GitHub (May 20, 2024): I wasn't using DNS API validation. I have used HTTP validation for as long as I've used NPM. I did try it as a testing function, but that was it. I stayed on a version that was working. Didn't see any reason to move as there wasn't a compelling reason to upgrade. I had been burned before by upgrading and then losing all my configuration. I'm not the only one that has suddenly had thier certificates stop renewing. Attempt to manually renew and the only message is "Internal Error". That is vague and not helpful to anyone.

kerem commented

2026-02-26 07:35:44 +03:00

Author

Owner

@sdh91 commented on GitHub (May 28, 2024):

I believe my issue was compounded by a semi-recent LE change with Multi-Perceptual validation. I urge anyone that may be implementing a geo-block on their firewall to confirm if this is making it worse for them. While I did upgrade to the latest version my success with renewing was sporadic. I could renew a single cert, then not renew others. After finding this post, https://community.letsencrypt.org/t/unexpected-renewal-failures-since-april-2024-please-read-this/216830, I realized that my geo-block that I use to protect myself, may be interfering. This was indeed a cause of the rest of the sporadic issues it seems. I am closing my issue at this time.

@sdh91 commented on GitHub (May 28, 2024): I believe my issue was compounded by a semi-recent LE change with Multi-Perceptual validation. I urge anyone that may be implementing a geo-block on their firewall to confirm if this is making it worse for them. While I did upgrade to the latest version my success with renewing was sporadic. I could renew a single cert, then not renew others. After finding this post, https://community.letsencrypt.org/t/unexpected-renewal-failures-since-april-2024-please-read-this/216830, I realized that my geo-block that I use to protect myself, may be interfering. This was indeed a cause of the rest of the sporadic issues it seems. I am closing my issue at this time.

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

No description provided.

Rows
Columns