Too many certificates already issued for ovh.net


#1

Solution:

If you have a domain like vpsxxxxx.ovh.net and you get the error: “There were too many requests of a given type :: Error finalizing order :: too many certificates already issued for: ovh.net: see https://letsencrypt.org/docs/rate-limits/” you can get the SSL certificate using the reverse record.

For example, you get the IP aaa.bbb.ccc.ddd for the vpsxxxxx.ovh.net domain, also you get a reverse record, like: ddd.ip-aaa-bbb-ccc.eu (you can find it in the OVH control panel “Manage IPs”).

You can use the reverse record (domain) “ddd.ip-aaa-bbb-ccc.eu” for the SSL.


#2

ovh.netisn’t on the Public Suffix List, so you’re unlikely to be able to dependably issue certificates under that domain.

Consider using your own (non-shared) Registered Domain, as it’s the only real solution to this issue. I don’t think OVH would agree to having their domain listed on the PSL, nor the maintainers of the PSL would agree to list them.

Rate Limit Current Status Domain
50 Certificates per Registered Domain per week Limit exceeded (60/50 this week). Next certificate issuable at 2018-12-06T23:58:38.000Z. ovh.net

Summary generated at https://tools.letsdebug.net/cert-search?m=domain&q=ovh.net&d=168 .


#3

Or maybe you can also use a free Dynamic DNS service name from the PSL.