mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1492] Error creating certificate #1146
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1146
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @talesam on GitHub (Oct 17, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1492
Version NPM: 2.9.1
@talesam commented on GitHub (Oct 17, 2021):
Ports 80 and 443 released, DNS active on server. Does anybody know how to solve this?
@marieldejesus12 commented on GitHub (Oct 17, 2021):
my log...
version 2.9.9
all firewall ports ok
@chaptergy commented on GitHub (Oct 17, 2021):
The ACME server returns a 500 error, which means there was an error on their side, so there isn't anything we could do about it. Maybe asking over in letsencrypt forums might yield more information. It could also have something to do with their rate limit.
@talesam commented on GitHub (Oct 17, 2021):
This rate limit is related to email, correct? Do you know where I see the limit? I didn't create many certificates, I don't think that's it, but I'll see it on their forum.
I wanted to put the cloudflare certificate to work, but whenever I tried it gave an error, is there somewhere explaining how to do it correctly?
@chaptergy commented on GitHub (Oct 17, 2021):
As the docs explain the rate limit is related to the domain. I don't think you are able to see whether you have been rate limited. If you use e.g.
duckdns.orgmany others might also request certificates for this domain, which is why the rate limit is reached very easily.I'm not really sure what you mean "put the cloudflare certificate to work". Are you talking about the DNS challenge with cloudflare? You have to add your cloudflare credentials into the textbox, see the docs