The server will not issue certificates for the identifier :: NewOrder request did not include a SAN short enough to fit in CN

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. crt.sh | 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: alotofyoumaybeaskingwhyareyouavirginisaytothemidkwhyami.tk right now but i want to change it to alotofyoumaybeaskingwhyareyouavirginisaytothemiampoggersgfisnot.international

I ran this command: sudo certbot --nginx -d alotofyoumaybeaskingwhyareyouavirginisaytothemiampoggersgfisnot.international

It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx
Obtaining a new certificate
An unexpected error occurred:
The server will not issue certificates for the identifier :: NewOrder request did not include a SAN short enough to fit in CN
Please see the logfiles in /var/log/letsencrypt for more details.

My web server is (include version): Nginx 1.18.0

The operating system my web server runs on is (include version): Ubuntu Server 20.04.2

My hosting provider, if applicable, is: IONOS

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 0.40.0

1 Like

For some technical/historical reasons, certificates issued by Let's Encrypt need to include at least one domain name which is less than 64 characters.

This will change one day in the future, but at the moment, there is no workaround other than to add a second name which fits that constraint.

5 Likes

With or without the TLD?

1 Like

The full domain: with the TLD.

And to be clear, you can get a certificate for your long domain, it's just that you will need to complement it with a second, shorter domain.

3 Likes

How would I do that?

1 Like

You'd register a second domain like lessthan64chars.tk and point it at your server, then when you want the certificate for alotofyoumaybeaskingwhyareyouavirginisaytothemiampoggersgfisnot.international, you'd do:

certbot --nginx -d lessthan64chars.tk -d alotofyoumaybeaskingwhyareyouavirginisaytothemiampoggersgfisnot.international
3 Likes

Would I point the less characters name to my server directly with an A record or point it to the domain with a CNAME record?

2 Likes

Either would be fine, but the CNAME would probably be easier from an administrative perspective.

3 Likes

If I am using a subdomain, it now does this:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Error while running nginx -c /etc/nginx/nginx.conf -t.

nginx: [emerg] a duplicate default server for 0.0.0.0:80 in /etc/nginx/conf.d/hopefullythisgetstoguinessworldrecordssomehowihopethisdoesplsdo.alotofyoumaybeaskingwhyareyouavirginisaytothemiampoggersgfisnot.international.conf:24
nginx: configuration file /etc/nginx/nginx.conf test failed

This part of the error says it all: you shouldn't designate multiple server blocks as default server.

2 Likes

But I haven't, just one.

Could you please post the output of sudo nginx -T ?

1 Like

If you show this file, we can all see the problem:

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.