-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
letsencrypt - too many registrations for this IP #237
Comments
This is the letsencrypt api rate limit issue. Just wait, it will return normal after 24 hours. By the way, if you have more than 5 certificates, I recommend you to issue a wilcard certificate. |
Currently, the checking interval is about 5 minutes, and it will only perform the renewal action if it has been a month since the last issuance. As the validity period of the certificate is 3 months, I think time is enough for nginx-ui to renew the certificate. |
I can't do that, I currently have 10 different TDLs in use, so a wildcard certificate won't help me.
Apparently this does not work, because I still get the error message, my certificates are all still valid until March (distributed from 2 - 15). |
I can add a setting for the renewal interval, but I don’t think it can solve the problem. I have 6 certificates on my server, and also have the same issue as you. I checked the logs for each certificate, and I finally found that one of the sites had not configured the proxy to the HTTP challenge port, resulting in too many failures on this site which caused rate limiting issues on others. So, I think you can check if the problem is caused by the failure of renewal of one of the certificates. I also need to apologize because, in the previous version, due to my oversight, the auto-cert goroutine would block during certificate renewal. Therefore, in the current updated version, there might be an accumulation of previously unrenewed certificates in the first few days. However, as long as the root problem is resolved, these certificates will automatically renew within two or three days. |
I added a "location /.well-known/acme-challenge" to each server block when I set it up.
I have only updated to version: 2.0.0-beta.8 (101) Here is a small example: Logs from the certificate:
EDIT: |
Yes, this is the current method. 😂 |
😂 |
wtf, whatever happened, it worked again about an hour ago. Surely this can't be due to the update to the latest version? |
Yes, it has been 3 weeks since I last change that part of codes. |
It seems to work without problems now, thanks |
Describe the bug
I have the strange problem that my IP was apparently blocked at letsencrypt because I sent too many requests. I am currently using 9 certificates.
Expected behavior
that the certificates are updated automatically.
Log
Info (please complete the following information):
It would be practical if the update interval could be set in the GUI.
The text was updated successfully, but these errors were encountered: