2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
con risposta 6 mesi fa
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.
con risposta 4 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa