now im banned and i had to wait until 10 august pterodactyl installer made much certificates when its bugged and now im banned when it work
My domain is: panel.kelpmc.life
I ran this command: bash <(pterodactyl-installer.se)
Hi @st1glio,
Are you banned or rate limited?
Testing and debugging are best done using the Staging Environment as the Rate Limits are much higher.
And to assist with debugging there is a great place to start is Let's Debug.
6 Likes
im rate limited im testing
it says IssueFromLetsEncrypt
Error
A test authorization for panel.kelpmc.life to the Let's Encrypt staging service has revealed issues that may prevent any certificate for this domain being issued.
213.199.63.237: Connection refused
With being rate limited the only thing to do is wait out the 168 hours (i.e. one week). For future one may apply for a rate limit increase, it may be granted if there’s a good reason.
Edit
Well one more thing to do while waiting is getting the configuration in good working order and test test test.
3 Likes
| Rate Limit | Current Status | Domain |
|---|---|---|
| 50 Certificates per Registered Domain per week | OK (4 / 50 this week.) | kelpmc.life |
| Summary generated at Let's Debug Toolkit . |
The Let's Debug toolkit relies on the https://crt.sh system to show certificates. Often crt.sh is late in posting to its databases.
And that is the case here. You have gotten 5 production certs for that name in the last couple days. Following the Rate Limit link Bruce provided describes a possible work-around. Or, try a different ACME Certificate Authority until you can again get a Let's Encrypt cert.
This is another tool to search cert history which clearly shows the certs you got: Entrust Certificate Search - Entrust, Inc.
Note ignore certs with the same serial number that is just showing both the Precert and the Leaf but that's just one production cert
I don't see any problems at the Let's Debug test site. And, since you got so many certs it is not a problem with you getting them but in setting up your system to use them.
3 Likes
Testing should be done on the staging environment to prevent exactly this, hitting rate limits (and adding load to the production environment without any good reason).
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.