- Newest
- Most votes
- Most comments
Hey,
This is happening as SailPoint created DNS zone is different then your global DNS zone (managed by Route 53). Go to LightSail >> Domain and DNS >> Under Details Locate Edit Name Servers >> Use Light sail Name Servers >> Save
And that's it! Go back and try to add SSL/TLS certificate. This should work now. Would suggest to take backup of existing name servers. Thanks!
answered a year ago
By
SailPointabove, do you mean Lightsail?@AWS-SUM yes, he means Lightsail. I followed his instructions and it worked. It took 2 attempts after updating the Name Servers, so it probably requires a few minutes to take effect even after it's done loading. Thanks!
Hi,
The DNS records get confirmed as part of verification during the SSL/TLS certificate generation by LetsEncrypt. If the TTL on the records and their time to propagate can be as long as 24 hours - then that likely is why the SetUp is unable to verify them at present. Waiting a while should help.
You could also try running commands to confirm the DNS propagation of those records yourself (though what you see and what LetsEncrypt sees can still be out of sync until the records are globally propagated)
Example commands -
dig A <insert_domain_name>
// check if response returns the Static IP address correctly
dig AAAA <insert_domain_name>
// check if response returns the IPv6 address correctly
Thanks.
I am getting the same issue. This is yet another blocker in what is suggested to be a simple process. Can I suggest that more detail is put into the AWS instructions. Seems it take a step, wait a day, take another step, wait a day... So far creating my word press site with lightsail is now into the weeks.
answered 2 years ago
Having the same issue currently. The domain is made, and I followed all steps based on aws documentation. Did your error end up resolving after 24 hours like is suggested above?
I have created two different instances using Lightstail to replicate the process and have the same issues.
answered a year ago
I had this error when using cloudflare for DNS and had the A and AAAA record's proxy status ON. Turned it off and the Lightsail error went away.
answered a year ago
Relevant content
asked 12 days ago
asked 2 years ago
I encountered this today as well for my site. Was there a resolution to your error? Please let me know what worked. Thanks,
I encountered this today as well. Was there a resolution?
Have you tried the commands mentioned here below and also waited until DNS propagates?
I am also getting this. I am using the get started link, instructions. It seems this needs looking into. I suspect the answer below about 'waiting' will resolve the issue. Following simple instructions results in errors, so lets make simple = simple pls.