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: poc.moxehealth.com (note: this was done in --staging
but the behavior also exists in production)
I ran this command: certbot certonly -n --agree-tos --email admin@moxehealth.com --dns-route53 -d poc.moxehealth.com -d poc-san-1.moxehealth.com,poc-san-2.moxehealth.com,poc-san-3.moxehealth.com,poc-san-4.moxehealth.com,poc-san-5.moxehealth.com,poc-hello.moxehealth.com --expand --config-dir /tmp/config-dir/ --work-dir /tmp/work-dir/ --logs-dir . --staging
It produced this output: The certificate creation succeeded; however, the Subject (primary domain name) of the certificate is poc-hello.moxehealth.com
when I am expecting it to be the first domain name added, poc.moxehealth.com
My web server is (include version): AWS ACM
The operating system my web server runs on is (include version): n/a
My hosting provider, if applicable, is: AWS
I can login to a root shell on my machine (yes or no, or I don't know): yes (the certificate is created using an AWS Lambda function)
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): 2.4.0, also experienced on 1.20.0