Closed verdurin closed 4 years ago
The ACME module uses a DNS challenge to confirm the domain name ownership and then generates the SSL certificates (https://letsencrypt.org/docs/challenge-types/). The process fails from time to time, but there is not much we can do on the Magic Castle side of things, apart from documenting what to do when this happens and why it could happen.
If the domain name was recently transferred to Google DNS, there might be some delay with the nameservers update?
You should be able to call terraform apply
again and eventually the certificates generation will work.
Yes, I do realise this might not be a Magic Castle problem.
Having tried a couple of times, it looks like it might be a Google DNS problem, because when I lookup the domain it returns ns-cloud-e1.googledomains.com.
while inside the domain management interface it reports that we're using ns-cloud-c1.googledomains.com.
. I suspect this is because I only this evening created both the domain and later the zone in Cloud DNS,
This has worked for me before, but I probably had left a bit more time after creating the domain and the zone.
Will try again tomorrow and close this ticket if it's working by then.
This does appear to work if the Google DNS nameserver entries are manually edited to match those in the Google Cloud DNS zone. One might have expected them to be the same automatically, but alas not.
I see this error with a newly-created domain registered with Google Cloud DNS: