Hi @borrelnoten
please share the complete output of that error.
There is another thread - Error creating new account 429
Looks like Sslforfree has a bug and is blocked.
There - https://check-your-website.server-daten.de/?q=burnmyass.nl#ct-logs - is no rate limit visible.
| Issuer | not before | not after | Domain names | LE-Duplicate | next LE |
|---|---|---|---|---|---|
| Let's Encrypt Authority X3 | 2019-04-27 | 2019-07-26 | burnmyass.nl, www.burnmyass.nl | ||
| 2 entries | |||||
| Let's Encrypt Authority X3 | 2019-02-02 | 2019-05-03 | burnmyass.nl | ||
| 1 entries | |||||
| Let's Encrypt Authority X3 | 2018-11-15 | 2019-02-13 | burnmyass.nl, www.burnmyass.nl | ||
| 2 entries | |||||
| Let's Encrypt Authority X3 | 2018-11-10 | 2019-02-08 | burnmyass.nl | ||
| 1 entries |
Read
to understand the Letsencrypt rate limits.
PS: There is a limit:
You can create a maximum of 10 Accounts per IP Address per 3 hours. You can create a maximum of 500 Accounts per IP Range within an IPv6 /48 per 3 hours. Hitting either account rate limit is very rare, and we recommend that large integrators prefer a design using one account for many customers.
So if Sslforfree creates a new account per new certificate order and if 10 users use that, the next hits the limit.