By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

AWS SES HTTPS custom domain click link-invalid cert

0

i wan to use HTTPS custom redirect domain for click link. i follow this aws document

  • step 1 and 2, created, verify and setup configuration set for subdomain [link.mydomain.com] in SES-Region Virginia.
  • step 3, create new distribution, other than main distribution that specific for web. origin: [mydomain.com], alternate: [link.mydomain.com]
  • step 4, in NS1 DNS add record [link.mydomain.com] IN ALIAS [r.us-east-1.awstrack.me]
  • step 5, add [link.domain.com] IN CNAME [distribution_name]
  • step 6, request and use certificate in ACM to used in distribution

when trying click the link in email, browser blocked the access NET::ERR_CERT_COMMON_NAME_INVALID https://link.blessingtransportbromoijen.com/CL0/https:%2F%2Fwww.trustpilot.com%2Freview%2Fblessingtransportbromoijen.com/1/010001874d4ac313-2b8d5d6f-2fc5-417c-8dc0-f12de35c3fd7-000000/5x8QxG3VmqQLXsAJui8PWmlvtDt8jk3S4_zoa2BmlO8=295

do i missed some steps or have wrong configurations? need some help to solve this problem.

Topics
Front-End Web & MobileBusiness Applications
Tags
Amazon Simple Email Service
Language
English
Alfan
asked a year ago507 views
2 Answers
0

NET::ERR_CERT_COMMON_NAME_INVALID, suggests there is an issue with the SSL certificate for your custom domain

Please check the following

  • Ensure that the SSL certificate you have requested in ACM includes the custom subdomain link.mydomain.com. The certificate should be either a wildcard certificate for *.mydomain.com or a certificate that specifically lists link.mydomain.com as one of the domain names
  • Double-check that you have selected the correct ACM certificate in the CloudFront distribution settings for the custom domain
  • Ensure that the DNS records are properly set up: Verify that the CNAME record for link.mydomain.com points to the CloudFront distribution domain name (e.g., d12345abcdwq.cloudfront.net). Verify that the ALIAS record for link.mydomain.com points to r.us-east-1.awstrack.me.
profile picture
EXPERT
Sedat Salman
answered a year ago
  • Alfan
    a year ago
    • ACM already issued SSL cert for *.mydomain.com
    • The cloudfront distributions already used the SSL cert above.
    • CNAME and ALIAS already properly set up to each names and vales.

    NET::ERR_CERT_COMMON_NAME_INVALID still exist

0

with my current configuration for HTTPS custom link (HSTS subdomain preload enable): Cloudfront, link.mydomain as alias for dxxx.cloudfront.net origin www.mydomain SES, custom domain link e.link.mydomain NS1 Dns,

  • link.mydomain in CNAME r.us-east-1.awstrack.me
  • e.link.mydomain in CNAME dxxx.cloudfront.net

now i got ERR_SSL_VERSION_OR_CIPHER_MISMATCH

whether SSL by ACM not valid to used for custom domain click link tracking? no idea to solved this problem.

Alfan
answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content