False "Requested domain is not a FQDN"

[LouWii]

Hi,

It's never the right time to have issues...
I got a certificate expiring tomorrow, and I can't renew it.

letsencrypt certonly --apache --renew-by-default --domains 
Requested domain  is not a FQDN

This is what I got for the domain https://canada.with.susie.and.louwii.fr/

What file should I modify in order to make that work ? I'd like to renew my cert quite quickly.

Thanks !

[bmw]

The FQDN is:

canada.with.susie.and.louwii.fr

If you prepend https:// like you would in your web browser, this is no longer a domain name and you'll see the error you encountered.

Alternatively, if you're running an up to date version of the client (if you run letsencrypt --version you should see version 0.5.0), you can simply run letsencrypt renew. This will renew your cert for you with the names you originally requested.

One caveat to this approach is letsencrypt renew will renew any certificates you have that are within 30 days of expiration. This may or may not be the behavior you want.

[LouWii]

Hum, interesting.

I have a script to renew certificates. That script was giving me the issue.
But I ran /opt/letsencrypt/letsencrypt-auto certonly --apache --renew-by-default --domains canada.with.susie.and.louwii.fr manually and it went through.

I'm gonna need to fix my renewal script.

Thanks bmw, you made me think and test the direct command line.

[jackrvaughan]

Posting this as it popped up on google.

If anyone has getting the Requested domain is not a FQDN because it contains an empty label. issue for multiple domain names (when using --expand for example), ensure there are no spaces between the domain names - only separate them with a comma.

I was writing:

./certbot-auto certonly --expand -d first.domain.com, second.domain.com

It should be:

./certbot-auto certonly --expand -d first.domain.com,second.domain.com

I don't believe that used to be a requirement but certainly is now.

[adrianbj]

Thanks @jackrvaughan - that solved the issue for me!