Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It produced this output: There were too many requests of a given type :: too many certificates (50) already issued for "nicesrv.de" in the last 168h0m0s, retry after 2025-08-17 16:04:43 UTC
My web server is (include version): apache 2.4.62
The operating system my web server runs on is (include version): debian 12
You can't. If nicesrv.de issues individual subdomains to various users, they probably belong on the public suffix list:
This is something the owner of that domain would arrange. If they're added to the PSL, Let's Encrypt will in due course pick up on that and adjust their rate limits accordingly.
Edit: though really, given those subdomains, I'd think they aren't intended to be in public use, and thus you wouldn't be issuing certs for those. It seems more like an internal hostname--I know Contabo does something like this for their VPS systems. The expectation is that if you're exposing something to the public, you'd use your own domain name to do it.
Thanks danb35. You are right, these are names created by my VPS administrator, and are not intended for public use. My mistake was to use it as if it were a public name, although used only by me for administrative access to the server. I will create a new domain of my own and use it instead.
Kind regards!