I tried to regenerate my ssl cert by using letsencrypt-auto because today is Dezember the 13. and my guess was that some issues will be removed at that point. But my new ssl-cert was not generated for my serves ip. Here are some test results.: https://www.ssllabs.com/ssltest/analyze.html?d=golden-griffons.de
Can anyone help me out with this issue or is it just because neither the domain nor the server is in the use or canada?
You generated a certificate that’s only valid for www.golden-griffons.de, it’s not valid for golden-griffons.de. You should generate a certificate that’s valid for both golden-griffons.de and www.golden-griffons.de by supplying both to the client.
But you’re right would have to use -d option. it seems I tried it to aoften and I don’t know when I can try regeneration again. Here is the command line output:
┌──────────────────────────────────────────────────────────────────────┐
│ You have an existing certificate that contains a portion of the │
│ domains you requested (ref: │
│ /etc/letsencrypt/renewal/www.golden-griffons.de.conf) │
│ │
│ It contains these names: www.golden-griffons.de │
│ │
│ You requested these names for the new certificate: │
│ golden-griffons.de, www.golden-griffons.de. │
│ │
│ Do you want to replace this existing certificate with the new │
│ certificate? │
│ │
│ │
│ │
│ │
│ │
├──────────────────────────────────────────────────────────────────────┤
│ │
└──────────────────────────────────────────────────────────────────────┘
An unexpected error occurred:
There were too many requests of a given type :: Error creating new cert :: Too many certificates already issued for: golden-griffons.de
Please see the logfiles in /var/log/letsencrypt for more details.
https://www.golden-griffons.de/ is fine so now it seems i actually need to know how to get rid from the blacklist to be able to re-run the command.
I have made a temporary redirect now and will just regenerate the cert in a week That will fix it. Because I redirected the site I have no chance to make a screenshot but the numbers may be the dummy ip adresses from the cert template fro non-authorised sites.
And your certificates are only issued against what you type after the option -d in your command line. So it wouldn’t be ip and domain name for example. It would be considered valid for your issued against domain(s) no matter the ip.
And just as a tip:
IP v4 is 32 bits, 4 octets / groups of numbers between 0-255: xxx.xxx.xxx.xxx
And IPv6 is 128 bits, addresses are represented as eight groups of four hexadecimal digits with the groups being separated by colons.
So those #'s you noted shouldn’t be confused with ip addresses.