Hi,
I get the error:
too many certificates (50) already issued for "strangled.net" in the last 168h0m0s,
But strangled.net is a domain of some dyndns-service. Can you please set the limit for it to some higher value ore remove it at all? Otherwise the superbe efforts setting up letsencrypt and strangled.net are spoiled by some minor insignificant flaw.
Best regards
The owner of that service could request a rate limit increase, if they think it needs more than 50 new certificates per week. The error message that is returned includes this link describing the details of the rate limit and how the domain owner can request an increase:
I send them an email but I guess I'm probably fucked. Can you reccommend an alternative to let's encrypt?
The limit is a "leaky bucket", so an additional new name on that domain becomes available every 202 minutes. So if you just try again later, you might manage to get one.
But certainly there are plenty of other CAs out there, many of which also provide free certificates using the same ACME protocol. You may want to look at the comparisons offered by the developer of Certify the Web as well as offered by the developer of Posh-ACME.
Google Trust Services have rate limits which aren't scoped to domain names:
If the subdomains of that dyn dns domain are used by unrelated people it should probably be added to the Public Suffix List. That would place it outside that registered domain limit you ran into. The PSL provides various security benefits between those subdomains among other benefits. See: Learn more about the Public Suffix List
That is also done by the domain owner / operator.