Saving debug log to /var/log/letsencrypt/letsencrypt.log
Found credentials in shared credentials file: ~/.aws/credentials
Plugins selected: Authenticator dns-route53, Installer None
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Requesting a certificate for *.mydomain.com
Performing the following challenges:
dns-01 challenge for ydomain.com
Encountered exception during recovery: SSLError: hostname 'route53.none.amazonaws.com' doesn't match either of '.bizland.com', 'bizland.com'
An unexpected error occurred:
SSLError: hostname 'route53.none.amazonaws.com' doesn't match either of '.bizland.com', 'bizland.com'
Please see the logfiles in /var/log/letsencrypt for more details.
Could you please share the log file /var/log/letsencrypt/letsencrypt.log?
To me this looks like an incorrect assumption about the region perhaps? I'm not sure but I'm guessing there should be something else where none is in the URL right now.
Also, could you share the output of dig route53.none.amazonaws.com? As I can't resolve that URL at all, but you seem to be able.
Thanks for your reply,
I think Route 53 is not a region specific, it is global service.
dig route53.none.amazonaws.com it will not resolve (verified). none is coming inroute53.none.amazonaws.com here due to the error which facing now. Using dns-route53 plugin the route53 TXT record not updating. I assume that some issue with plugin that's why coming none
I can update DNS records with json for the hosted-zone
That's weird, because in your Certbot output it clearly did connect to something, otherwise it would not have given a SSL error with hostname mismatch. That can only happen when a certificate would have been served by a server in the TLS handshake and that requires a connection to an IP address. Do you have that hostname mentioned in /etc/hosts by any chance?
Also, please provide the requested log file. It might not help at all, but it's a good idea to have a look anyway.