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.
My domain is: panos.network
I ran this command: certbot renew
It produced this output: too many requests of a given type
I can not renew my cert anymore. I do not know if a have a problem with my router, but for the first time the http challenge did not work. So after 5 times I got the “too many requests” error.
Do I really have to wait for a whole week and then try again? I might need more tries to find out what the problem is.
I am sorry I did not get the exact output of the renewal. I will try next time.
What do I mean by “using the other cert instead”?
I have two servers in my domain “panos.network”.
One server has a cert for “panos.network” and “www.panos.network” and the other server has a cert for “panos.network”
I do not know if this is the right way to do it, but I always worked.
If you want to test without worrying about the rate limits you can try certbot renew --dry-run which will use the staging server. Once you’ve figured out the problem then run certbot renew again.
You can run certbot certificates to see what certificates you have; if you have one that’s valid you may be able to change your web server configuration to use it.