Getting SSL and Connection not secure errors for Amplify managed SSL certificate

Question

Hi,

I have a website hosted with AWS Amplify from May 2025, then I bought a custom domain from NameCheap with a .work extension in July and added it as a custom domain with an Amplify managed SSL certificate. It worked well for a while but now I am getting SSL errors like SSL_ERROR_RX_RECORD_TOO_LONG, Connection not secure error, etc. Tried deleting and adding the domain again still didn't help, also I cleared the browser cache and re-verified all DNS records between Amplify and NameCheap. Everything is correct, still I get errors from nowhere, after weeks of working fine, site is https as well. Can anyone please help me out and provide a solution to get it working on all browsers?

Thank you

re:Post Agent · Answer

When an Amplify-managed SSL certificate suddenly stops working after functioning correctly, there are several potential causes and solutions to consider:

1. Certificate Expiration: Amplify-managed certificates are valid for 13 months and should renew automatically. However, if the CNAME verification record in your DNS settings has been modified or deleted, Amplify cannot renew the certificate. In this case, you need to delete and re-add the domain in the Amplify console.

2. DNS Record Issues: Verify that all required DNS records (CNAME and A records) are correctly configured in your NameCheap account. Use tools like MxToolbox or dig to confirm that your DNS changes have propagated globally.

3. Conflicting DNS Records: Check for any conflicting records (duplicate CNAMEs or A records) that might interfere with the SSL configuration.

4. DNS Propagation: Some users might experience issues if DNS changes haven't fully propagated across all networks. This can take up to 48 hours in some cases.

5. CloudFront Distribution Problems: Since Amplify creates a CloudFront distribution for custom domains, there could be an issue with how your domain is associated with this distribution.

Troubleshooting steps:
- Navigate to "Hosting > Custom Domains > Actions > View DNS records" in your Amplify console to verify the required DNS records
- Check if the CNAME verification records are still present in your NameCheap DNS settings
- Try completely removing the custom domain from Amplify, clearing all related DNS records from NameCheap, and then re-adding the domain following the setup process again
- Ensure there are no proxy services (like Cloudflare) that might be interfering with the SSL configuration

If these steps don't resolve the issue, you may need to contact AWS Support for further investigation of your specific configuration.  
**Sources**  
[SSL certificate is expired (Certificate managed by Amplify) | AWS re:Post](https://repost.aws/questions/QUB_4n1pJCQxaKAqXGSXFWcQ/ssl-certificate-is-expired-certificate-managed-by-amplify)  
[AWS Amplify DNS issue | AWS re:Post](https://repost.aws/questions/QUcrdsRkg5S_yA23ylIvHIPQ/aws-amplify-dns-issue)  
[Amplify fails on SSL Configuration | AWS re:Post](https://repost.aws/questions/QU2ClTgEETT3uhLbnzdoDbnQ/amplify-fails-on-ssl-configuration)  
[Timeout when creating custom domain on AWS amplify | AWS re:Post](https://repost.aws/questions/QUFZTHapV0SpGUMcZKWCS9Yw/timeout-when-creating-custom-domain-on-aws-amplify)

Getting SSL and Connection not secure errors for Amplify managed SSL certificate

Add your answer

Relevant content