starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 01:15:51 +03:00

[GH-ISSUE #1350] Internal Error - Letsencrypt new certificate #1070

New issue

Closed

opened 2026-02-26 06:35:38 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 06:35:38 +03:00

Owner

Originally created by @tauchvogel on GitHub (Aug 26, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1350

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
Using NPM on a fresh and new Raspi 4 with new DietPi and Docker and Docker-Compose. Everytime I try to receive a new letsencrypt certificate for one of the domains. But there is still an error

Nginx Proxy Manager Version
2.9.8

Expected behavior
This Error is displayed after trying to receive a new letsencrypt certificate:

Error: Command failed: certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-6" --agree-tos --authenticator webroot --email "xyz@gmail.com" --preferred-challenges "dns,http" --domains "xyz.duckdns.org"
Saving debug log to /var/log/letsencrypt/letsencrypt.log
An unexpected error occurred:
There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

at ChildProcess.exithandler (node:child_process:397:12)
at ChildProcess.emit (node:events:394:28)
at maybeClose (node:internal/child_process:1064:16)
at Socket. (node:internal/child_process:450:11)
at Socket.emit (node:events:394:28)
at Pipe. (node:net:672:12)

Operating System
DietPi ( new installation)

Originally created by @tauchvogel on GitHub (Aug 26, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1350 **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** Using NPM on a fresh and new Raspi 4 with new DietPi and Docker and Docker-Compose. Everytime I try to receive a new letsencrypt certificate for one of the domains. But there is still an error **Nginx Proxy Manager Version** 2.9.8 **Expected behavior** This Error is displayed after trying to receive a new letsencrypt certificate: Error: Command failed: certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-6" --agree-tos --authenticator webroot --email "xyz@gmail.com" --preferred-challenges "dns,http" --domains "xyz.duckdns.org" Saving debug log to /var/log/letsencrypt/letsencrypt.log An unexpected error occurred: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/ Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. at ChildProcess.exithandler (node:child_process:397:12) at ChildProcess.emit (node:events:394:28) at maybeClose (node:internal/child_process:1064:16) at Socket. (node:internal/child_process:450:11) at Socket.emit (node:events:394:28) at Pipe. (node:net:672:12) **Operating System** DietPi ( new installation)

kerem

2026-02-26 06:35:38 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:35:39 +03:00

Author

Owner

@chaptergy commented on GitHub (Aug 26, 2021):

This has nothing to do with NPM. As the error message says, certbot has a fair use limit. And it seems too many people have issued a certificate for a duckdns domain. As the linked letsencrypt docs say, you are only allowed 50 certificates per week per domain. And in your case your domain is duckdns.org. So you either need to wait and have more luck in a few days or get your own domain.

@chaptergy commented on GitHub (Aug 26, 2021): This has nothing to do with NPM. As the error message says, certbot has a fair use limit. And it seems too many people have issued a certificate for a duckdns domain. As the [linked letsencrypt docs](https://letsencrypt.org/docs/rate-limits/) say, you are only allowed 50 certificates per week per domain. And in your case your domain is duckdns.org. So you either need to wait and have more luck in a few days or get your own domain.

kerem referenced this issue

2026-02-26 07:38:59 +03:00

[PR #1070] [MERGED] Bump lodash from 4.17.19 to 4.17.21 in /docs #3354

kerem referenced this issue

2026-02-26 07:39:01 +03:00

[PR #1084] [MERGED] v2.9.2 #3363

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

No description provided.

Rows
Columns