You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I add the www.example.com, it fails. If I just run this with example.com, it works. It logs the following:
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for example.com
http-01 challenge for www.example.com
Found credentials in environment variables.
Calling s3:put_object with {'Body': u'<id>', u'Bucket': 'example.com', 'Key': u'.well-known/acme-challenge/<id>', 'ACL': 'public-read'}
Starting new HTTPS connection (1): s3-us-west-1.amazonaws.com
Starting new HTTP connection (1): example.com
Starting new HTTPS connection (1): example.com
Calling s3:put_object with {'Body': u'<id>', u'Bucket': 'example.com', 'Key': u'.well-known/acme-challenge/<id>', 'ACL': 'public-read'}
Starting new HTTPS connection (1): s3-us-west-1.amazonaws.com
Starting new HTTP connection (1): www.example.com
Starting new HTTPS connection (1): www.example.com
Unable to reach http://www.example.com/.well-known/acme-challenge/<id>: hostname 'www.example.com' doesn't match 'example.com'
Self-verify of challenge failed, authorization abandoned!
Waiting for verification...
Cleaning up challenges
Starting new HTTPS connection (1): s3-us-west-1.amazonaws.com
Incomplete authorizations
Note that I added www.example.com AFTER initially setting up the cert with example.com.
The text was updated successfully, but these errors were encountered:
Probably a bit late but I came here looking for the answer and figured it out eventually:
Firstly, you specify additional domains by adding extra -d options to the original commandline. So in your example you'd have -d example.com -d www.example.com. As you've already run it certbot will ask you if you want to expand the existing certificate. Just say yes.
Once that is done you can specify the additional domains in the Cloudfront Alternate names (CNAMEs) field when editing the distribution.
Here is the command I tried:
When I add the
www.example.com
, it fails. If I just run this withexample.com
, it works. It logs the following:Note that I added
www.example.com
AFTER initially setting up the cert withexample.com
.The text was updated successfully, but these errors were encountered: