2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
répondu il y a 6 mois
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.
répondu il y a 4 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- demandé il y a 20 jours
- AWS OFFICIELA mis à jour il y a 4 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans