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:
Apenfamilie.nl, main-system.nl
I ran this command:
No command ( trying to get vestaCP to work.
It produced this output:
Error: Let’s Encrypt new auth status 429
My web server is (include version):
Virtual centos7
The operating system my web server runs on is (include version):
Centos7 with vestacp
My hosting provider, if applicable, is:
myself…
I can login to a root shell on my machine (yes or no, or I don’t know):
Yes can do snapshots also so can go back in time.
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
VESTACP
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
no bot i think…
Hi all,
I think i know the problem (to manny ssl’s made) but can someone delete all of them?
apenfamilie.nl and domain main-system.nl ??
Because of the cname i think it makes a cert but somewhere in the procces its going bad.
So after troubleshooting i read i must delete cname in cloudflare and make a A record.
Now i dont have a error 400 but a Error: Let’s Encrypt new auth status 429 / 423
Can someone have a look or tell me what i done wrong?