- Newest
- Most votes
- Most comments
Hi Marcelo,
I would try by listing all records known under this domain name to see which CNAMES are already known and better understand the message re. duplicate CNAMES.
To do that, see answers to https://stackoverflow.com/questions/19322962/how-can-i-list-all-dns-records
Best,
Didier
I thought I'd solved it!
My domain is being programmed and it worked, but when it reached the last propagation, it stopped and displayed the error:
'SSL setup failed One or more of the CNAMEs you provided are already associated with a different resource. Make SSL changes and try again Consult the troubleshooting guide, make any necessary changes, and retry activation.
Basically what I had thought of as a solution was:
Take away Amplify's responsibility to manage my SSL key
I used AWS ACM for this, certifying my domains 'www.xpto.com' and 'xpto.com'.
The reason for the error was that Amplify's SSL manager was automatically certifying the domains 'www.xpto.com' and '*.xpto.com'.
This was causing a conflict in my registration of a certificate for my api domain: 'api.xpto.com'.
The solution was to use ACM to manage the keys for the 'www.xpto.com' and '*.xpto.com' domains and link them to my customized Amplify domain.
But to no avail! Still waiting.
Relevant content
- asked 2 years ago
- asked 24 days ago
- asked 2 months ago