Hi there, I've deployed a Linux Nginx-based server on which I request my certificates from Let's Encrypt (certonly). I also wrote a script for monthly renewals. So far, everything works well. My requests are based on a config file (using --config option) in which I specified all my domains: doma…

This is a known bug, refer to this post for more details: [image] Common Name change after using --expand flag Issuance Tech A…

Thanks for your quick answer! So if I understand well, I have to either downgrade to 0.4.* or wait for 0.6.0 but in all cases, 0.5.0 is responsible for this error? I precise that I never used the --expand flag and that all of my requests are done after flushing existing certificates or are simple r…

That’s correct. --expand isn’t necessary to trigger this bug - any certificate generated by the client has this issue.

Wrong CN using multiple SAN

Server

pfg May 9, 2016, 3:01pm 2

This is a known bug, refer to this post for more details:

Topic		Replies	Views
Common Name change after using --expand flag Issuance Tech	6	6837	April 26, 2016
Latest renewal changes certificate CN with certbot 1.22.0 Help	2	607	May 4, 2023
Common name SAN not first domain in list Server	2	1910	May 3, 2016
Choose domain for expanded certificate Issuance Policy	5	2635	February 17, 2016
Certbot picks up wrong CN from the SAN list while renewing/creating cert Help	9	1576	July 18, 2023

Wrong CN using multiple SAN

Related topics