How to create a redirect, that works with HTTPS?

[yahya]

I want to redirect all traffic from one domain to another.

For example: foo.mydomain.com/abc/xyz should redirect to https://newdomain.com/abc/xyz.

I successfully managed to do this using “page rules”.
Unfortunately you need to create a DNS record for page rules to work.

So I create a CNAME record that goes to a subdomain that I don’t use:

CNAME foo.mydomain.com dummy.mydomain.com (Cloudflare proxy active)

Redirecting works fine for http://foo.mydomain.com.

But when I go to https://foo.mydomain.com I get a ERR_SSL_VERSION_OR_CIPHER_MISMATCH error on Chrome (similar error for other browsers).

Please help.

[sdayman]

Here’s a simpler method:

Redirecting One Domain to Another

This tutorial covers redirecting one domain to another. For this, we will be redirecting domainA.com to domainB.com. The following settings need to be configured under the domain you are redirecting from, in this example, this is domainA.com Step 1, The DNS Record: The first thing you will need is a DNS record for @, www and any other subdomains you want to redirect, set to . This can point to any IP address as the redirection page rule will execute first. I would recommend pointing…

[yahya]

Thanks for the link.
This is exactly what I did, but the HTTPS version seems to give me the error I mentioned.
Any solution to this?

[yahya]

Actually I found out something odd.

I have 2 records similar to:

A foo 192.0.2.1
A www.foo 192.0.2.1

I also have 2 page rules:

Rule 1:
www.foo.mydomain.com/*
forwards to htps://newdomain.com/$1

Rule 2:
foo.mydomain.com/*
forwards to htps://newdomain.com/$1

It looks like htps://foo.mydomain.com works fine.
But htps://www.foo.mydomain.com does not.

Note that HTTP varients of all of them works as intended.

[yahya]

I had to call it htps instead of HTTPS, becuase the forum bizarrely doesn’t allow me to place more than 2 links for new users.

but my real rules use https:// . Not htps://

[sdayman]

www.foo won’t work because:

Subdomain too deep

This tutorial covers a possible reason for the SSL_ERROR_NO_CYPHER_OVERLAP and ERR_SSL_VERSION_OR_CIPHER_MISMATCH errors (Firefox and Chrome respectively) when seen on a subdomain. The Cloudflare universal certificates cover example.com and *.example.com. This means that it covers any subdomain one level below the domain you signed up with. It will cover www.example.com and subdomain.example.com, as these are one level below the root domain, example.com. The certificate will not cover www.sub…

[yahya]

That’s annoying. Thanks for the help!