2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Figured out it is because when adding the CNAME to enable the https, I missed the ending period in the name. Now. my custom domain is available. But it still doesn't work, it says 404.
beantwortet vor 6 Monaten
0
Checking if you include the '.' at the end, '.' mean that is FQDN and different with no '.' at the end. I have been faced with same situation before, please copy exactly given CNAME, and URL you got in Amplify console.
beantwortet vor 4 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor 4 Monaten