1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
The issue you're facing is due to the HSTS policy being applied to your custom redirect domain. The HSTS policy requires a valid SSL certificate to be served for your domain, and the certificate's common name should match the domain.
To solve the problem:
- Obtain a valid SSL certificate for your custom redirect domain.
- Install the SSL certificate on the server hosting your custom redirect domain.
- Ensure the server is configured to serve the SSL certificate for HTTPS requests.
By having a valid SSL certificate in place, the browser will no longer block your tracked links due to the HSTS policy, and the NET::ERR_CERT_COMMON_NAME_INVALID error will be resolved.
関連するコンテンツ
AWS公式更新しました 9ヶ月前- AWS公式更新しました 9ヶ月前
- AWS公式更新しました 1年前
in NS1 DNS record, the current custom redirect domain for tracking "link.domain" IN CNAME r.us-east-1.awstrack.me If i have to add SSL in hosting server the record would be "link.domain" IN A domain-IP, then how to setup my redirect domain for point to awstrack.me?
I am stuck in this part. As info, i already have SSL for redirect domain for tracking
this link not as expected, should be to truspilot site. https://link.blessingtransportbromoijen.com/CL0/https:%2F%2Fwww.trustpilot.com%2Freview%2Fblessingtransportbromoijen.com/1/010001870cf9c454-6f008a43-9963-48bf-9551-7bd25a060442-000000/oEZHz66HrbvefESjY2kkiqCTaLVhesL0AB5TCCbNhqA=293