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.
Thank you for reply. Yes I have Cloud DNS, and it is common to have googledomains text in the nameserver. Here issue is with authentication, but as I am using Compute Engine it doesn’t require any credentials file, I even assigned the service account to Instance. I am not sure where the issue is !
Failed authorization procedure. mettavisions.com (dns-01): urn:ietf:params:acme:error:dns :: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.mettavisions.com
IMPORTANT NOTES:
The following errors were reported by the server:
Domain: mettavisions.com
Type: None
Detail: DNS problem: NXDOMAIN looking up TXT for
_acme-challenge.mettavisions.com
That's the main problem, if the dns-google-plugin isn't compatible with your setup.
You can add
--debug-challenges
then Certbot should wait before doing the next step after the plugin has created the TXT entry. So you can recheck your domain and test, if the TXT entry is visible.
Before adding ssl it used to redirect to www.mettavisioins.com when I entered mettavisions.com, this is not happening now with https. What could be the issue?