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: zitecraft-dev.cloud.tilaa.com
I ran this command: ./certbot-auto --apache
It produced this output: too many certificates already issued for this exact domain.
My web server is (include version): apache 2.2
The operating system my web server runs on is (include version): contOS 6.5
My hosting provider, if applicable, is: tilaa.nl
I can login to a root shell on my machine (yes or no, or I don’t know): yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no
Hi. I first ran the certbot-auto setup which cause an error due to a missing "etc/httpd/conf.d/ directory, I created the dir manually ran the setup again and chose the two domains www.zite… and without www, (like before). this time i got a little further in the setup but the www domaine caused an error. I tried again this time without the www domain and got even a little further, but this time it seems that i have exceeded the amount of certificates ?
When i test my domain on sslabs it says that it found a certificate but doesn’t match the name, the certificate is issued to: localhost and issued by: localhost it looks to be very old, so i suspect it is a old certificate from a previous attempt
Yesterday i was trying to setup letsencrypt via directAdmin, but with kind of same result, at some point in my trying to make it work i ran into this “too many certificates already issued blabla…”
Will I have to wait until? tomorrow? next week? Are there anything else i can do to continue? I would really apreciate getting https up and running before the weekend. Cheers!