Home > Programming, Servers & Scripts >

Follow Caurmen's S3 + Cloudfront setup and receive unsafe warning from Chrome (5)

05-15-2017 04:13 AM #1 anhtitbeo (Member)
Follow Caurmen's S3 + Cloudfront setup and receive unsafe warning from Chrome

So I've followed through Caurmen's guide to set up a landing page using S3 + Cloudfront and all works well with www.domainname.com. However, when I decided that I wanted to use domainname.com (without the www.), I scrapped the whole setup and did the whole thing again. Everything is fast and easy this time since I was getting used to the process, but at my final testing step, this warning pops out on Google Chrome:

This server could not prove that it is domain.com; its security certificate is from *.cloudfront.net. This may be caused by a misconfiguration or an attacker intercepting your connection"

Anyone know how to fix and remove that warning? I'm afraid it may cause traffic to stay away from my LP if receiving this warning.

P/S: when I test it on safari and IE, no such warning appears. Really wonder what cause the problem.

05-15-2017 05:27 AM #2 Issac (AMC Alumnus)

When you create the bucket for your domain, you have to create and redirect "www" subdomain to the domain.

The subdomain and the domain must be included, with their own instance in ROUTE 53, if you use it, and on CLOUDFRONT.

Here you have a detailed step by step. It´s easy to follow.

http://docs.aws.amazon.com/AmazonS3/...lkthrough.html


Thank you

Issac

05-15-2017 01:45 PM #3 caurmen (Administrator)

That problem pops up from time to time associated with Cloudfront - I assume you're using HTTPS not HTTP?

Hopefully Issac's solution will solve it - if not check back in here and we'll get into fixing the issue.

(Note: if at all possible, it's usually easiest to just use www.domain.com)

05-15-2017 01:45 PM #4 caurmen (Administrator)

That problem pops up from time to time associated with Cloudfront - I assume you're using HTTPS not HTTP?

Hopefully Issac's solution will solve it - if not check back in here and we'll get into fixing the issue.

(Note: if at all possible, it's usually easiest to just use www.domain.com)

05-15-2017 03:07 PM #5 anhtitbeo (Member)

Quote Originally Posted by caurmen View Post
That problem pops up from time to time associated with Cloudfront - I assume you're using HTTPS not HTTP?

Hopefully Issac's solution will solve it - if not check back in here and we'll get into fixing the issue.

(Note: if at all possible, it's usually easiest to just use www.domain.com)
You're right. The problem is because I tried to access the domain using https, otherwise it run smoothly after I follow Isaac's solution. Thank you both for helping me out!

Home > Programming, Servers & Scripts >