You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
adding cutom domain resulted to the following message:
Something went wrong. Please refer to our troubleshooting guide below to diagnose the issue. After fixing the issue, choose retry below.
Error message: One or more of the CNAMEs you provided are already associated with a different resource.
I've checked where my subdomains are pointing to (with dig command and online tools). They point correctly to url provided in amplify web console for domain management.
i suspect that subdomain can be connected to one of my previousd amplify account that has been discontinued a few years ago. if so, it looks like a bug.
i was also trying to use aws cloudfront list-conflicting-aliases --distribution-id ??? --alias name.mydomain.me but always got: The specified distribution does not exist. I tried use hosting url and stackId but they do not work for distribution-id param.
Pls help to solve the problem and advise on how can i get distribution-id for my amplify dev and prod environments deployed in amplify cloud.
Expected behavior
custom domain is validated and added
Reproduction steps
amplify push
go to console and add custom subdomain for prod env (dev has already working subdomain and same master domain)
go error above on last step
Code Snippet
// Put your code below this line.
Log output
// Put your logs below this line
Something went wrong. Please refer to our troubleshooting guide below to diagnose the issue. After fixing the issue, choose retry below.
Error message: One or more of the CNAMEs you provided are already associated with a different resource.
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered:
Hey, @nilyin 👋. Appreciate your patience on a response. Can you see if the steps detailed within this AWS re:Post article can help resolve the issue? In the mean time, I'll reach out to our Hosting team to see if there are further steps to take to unblock you.
Hi @cwomack : the recommendations from this post are not applicable as I am using Amplify app, for which I don't know how to get my app's distribution-id (target distribution-id). So that I am not able to use AWS CLI commands described there, as these rely on this parameter.
Before opening, please confirm:
JavaScript Framework
Vue
Amplify APIs
GraphQL API
Amplify Version
v5
Amplify Categories
auth, storage, function, api, hosting
Backend
Amplify CLI
Environment information
Describe the bug
adding cutom domain resulted to the following message:
I've checked where my subdomains are pointing to (with dig command and online tools). They point correctly to url provided in amplify web console for domain management.
i suspect that subdomain can be connected to one of my previousd amplify account that has been discontinued a few years ago. if so, it looks like a bug.
i was also trying to use
aws cloudfront list-conflicting-aliases --distribution-id ??? --alias name.mydomain.me
but always got:The specified distribution does not exist.
I tried use hosting url and stackId but they do not work fordistribution-id
param.Pls help to solve the problem and advise on how can i get
distribution-id
for my amplify dev and prod environments deployed in amplify cloud.Expected behavior
custom domain is validated and added
Reproduction steps
Code Snippet
// Put your code below this line.
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: