- Newest
- Most votes
- Most comments
- Check Your DNS Configuration: Verify that the DNS records for api.centroproinf.com.br are correctly pointing to your intended AWS service (e.g., an EC2 instance, API Gateway, etc.).
Ensure that there are no conflicting CNAME or A records pointing to other AWS services like Kinesis or another API endpoint that could cause the certificate to change.
- Verify ACM Certificate Associations:
If you are using AWS Certificate Manager (ACM) for your SSL certificates, ensure that the correct certificate is associated with your domain. Check that the certificate is correctly attached to the service you are using (e.g., API Gateway, CloudFront, etc.).
Ensure there are no old or incorrect certificates associated with your domain.
- Check for Wildcard Certificate Conflicts:
If your domain is using a wildcard certificate (e.g., *.centroproinf.com.br), ensure that no other services (like Kinesis Video Streams) are inadvertently being matched by this wildcard and serving their own certificate.
- Review SSL/TLS Settings in Your Browser or Client:
Ensure that your browser or client is not caching old certificate information. Clear the SSL state in your browser, or use a different browser or incognito mode to see if the issue persists.
Relevant content
- asked 8 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thank you very much for your answer, thanks to it I went to check my IPs and I saw that I had a private IPv4 that I could define in the website's https settings. Since then, my website has not gone down anymore. But api.centroproinf.com.br no longer works within the AWS server. I finally solved my problem.