Continued from How to get a custom domain with SSL and CloudFlare - #8 by Senor_e474
Hi, thanks very much for the reply.
Background:
So far I have registered a .ml domain with freenom, updated the freenom dns to set the nameservers to Infinity’s nameservers. This worked fine with Wordpress running on http.
When you add a website to Cloudflare, step 2 prompts you to set up the DNS records, which was where I was struggling.
I got Cloudflare working by adding:
A record:
name: abcdef.ml
value: IP4 address (4 byte dotted quad) from account information, e.g. 123.234.x.x
CNAME record:
name: www
value: A record name part, e.g. abcdef.ml
This got me to the point where Cloudflare would list its nameservers. I went back to freenom and changed the nameserver settings from the Infinity’s to the ones given by Cloudflare. This seems to work OK for http, but I am struggling to set up https (with Wordpress, of course).
I tried setting up a self signed certificate on Infinity, and installing it, but that didn’t get recognised by the Really Simple SSL plugin. I then tried setting up the Free Lets Encrypt SSL certificate, and adding the “_acme challenge” CNAME record in Cloudflare’s DNS, but that didn’t work either. I’ve got as far as cloudflare returning a 526 “Invalid SSL certificate” when I try and visit via https.
At this point I’m not sure how to get Wordpress working with SSL, or if I’ve actually set up my Cloudflare DNS record correctly, or just happened to luck out with an accidentally working configuration.
Edit: I just went in to Cloudflare and changed the “SSL/TLS Encryption Mode” from “Full (strict)” to just “Full”, and I get a grey padlocked default site “Let’s Make Something Awesome”. So I guess https is now working, but I still have to figure out how to get Wordpress up and running with SSL.
I’m going to give setting up Wordpress and SSL another go, I assume I need to get the Really Simple SSL plugin to work, hopefully it was a caching issue. It’s definitely using the Lets Encrypt SSL certificate (looking at the certificate details in Chrome), but I hope it’s just a matter of getting Wordpress and the SSL plugin happy.