Cloudflare certificates on AWS

What is the name of the domain?

example.com

What is the issue you’re encountering

HTTPS not working on AWS infrastructure

What feature, service or problem is this related to?

I don’t know

What are the steps to reproduce the issue?

Hello everyone,

I’ve registered domain with Cloudflare and set up SSL certificates with cert-bot (let’sencrypt) for mydomain.com and *.mydomain.com.
I’ve set up certificates on AWS (certificate, private key, chain).
I’ve created CloudFront and ELB that use these certificates.
When I put records for something.mydomain.com and point them to my CloudFront’s and Network Load Balancer’s public DNS I get insecure connections.
something.mydomain.com is proxied (not DNS only).

Is there any way to solve this issue while still using Cloudflare DDoS protection with infrastructure on AWS?
thanks in advance!

What is the name of the domain?

ridenow-ug.com

What is the issue you’re encountering

Can’t use Cloudflare certificates on AWS

What are the steps to reproduce the issue?

Hello everyone,

I’ve registered domain with Cloudflare and set up SSL certificates with cert-bot (let’s encrypt) for ridenow-ug.com and *.ridenow-ug.com.
I’ve set up certificates on AWS (certificate, private key, chain).
I’ve created CloudFront and ELB that use these certificates.
When I put records for something.mydomain.com and point them to my CloudFront’s and Network Load Balancer’s public DNS I get insecure connections.
something.ridenow-ug.com is proxied (not DNS only).

Is there any way to solve this issue while still using Cloudflare DDoS protection with infrastructure on AWS?
thanks in advance!

something.ridenow-ug.com does not resolve at all. You need to configure the DNS entry.

And what’s your encryption mode on Cloudflare?

Hello Sandro,

I am sorry about not giving proper urls, here is the list:

Record behind CloudFront is http://admin-staging.ridenow-ug.com.
Record(s) behind Network Load Balancer (ELB) are:
http://dispatch-stg.ridenow-ug.com
http://api-stg.ridenow.com
and few more (can’t post more urls)

At the moment encryption mode is “Flexible”.

Change this to Full Strict for starters, as you otherwise have no encryption at all.

1 Like

I have turned off “proxied” parameter and set DNS only parameter and it works with https now, but I really want “proxied” to be turned on so I could use Cloudflare services.

Done this now, thanks!

Seems to work fine with the proxies however

sitemeer.com/#aa9ee702956b5da714a4639392012a730f786599

I have turned on “proxied” for that URL now, seems to be working fine. Will test it a bit more and report back soon!

The problem was probably the disabled encryption.
The encryption mode always needs to be Full Strict.

2 Likes

Yup this seems to be it, thanks Sandro you are a real G.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.