大网数据广告活动
服务器运维问答

CloudFront redirection with ssl gives "invalid certificate" error when accessing https://company.com, but why?

· 52CE 我爱测

I've configured an AWS CloudFront redirection (with SSL) using [this guide]. 1 I've configured an A record with Alias which points company.com. to the CloudFront domain name. When I access the CloudFront domain name, the site is …

问题原文

原帖链接 · Itai Ganot · CC BY-SA 3.0

I've configured an AWS CloudFront redirection (with SSL) using [this guide].1

I've configured an A record with Alias which points company.com. to the CloudFront domain name.

When I access the CloudFront domain name, the site is loaded successfully and appears secured.

But when I access the site by https://company.com I get a certificate error which says that the certificate is not valid.

The certificate I purchased is for *.company.com.

In chrome, I get the following error:

Your connection is not private

Attackers might be trying to steal your information from angelsense.com (for example, passwords, messages, or credit cards). 
Learn more
NET::ERR_CERT_COMMON_NAME_INVALID

Automatically send some system information and page content to Google to help detect dangerous apps and sites. Privacy policy

How can it be fixed?

已采纳解答

原帖链接 · Gerald Schneider · CC BY-SA 3.0

Your certificate is only valid for *.angelsense.com. It is not valid for angelsense.com. To use it without any subdomain you have to add angelsense.com additionally to *.angelsense.com as a SAN (Subject Alternative Name) when you create the certificate.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2017-10-16)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。