Gonna comment on the main things.
Now, you can opt into using their “Full SSL” option instead, but now you lose the ease of use from the “Flexible SSL” option because you need to configure your own web server for SSL instead of just making a DNS change.
Including the previous section. This is correct, but you need to secure your website as well, plus it can be a one time thing every 15 years if you use their free Origin Certificates.
The above is easily enough reason to avoid them like the plague, but they also used shared SSL certificates. That means the SSL certificate being served with your domain is also being served to dozens or hundreds of other unrelated sites.
Come on, avoid them like the plague, it’s absurd. The recommend method before is always Full (Strict), which validated and encrypt the connection on both sides of their POPs. Obviously they still decrypt the data at the nodes, but every proxy CDN does the same (Akamai uses even their domain, Fastly, etc.), there are no solutions to this.
Also no one will care about the list of domains (not Google’s SEO rules, not 99.999% of users) and new ones are not shared anymore. I don’t know if you need to re-add the domain or ask support for the switch if it was shared previously. (@cloonan, would you mind confirming this?)
You Can Get a Dedicated SSL Certificate With Cloudflare, But…
It’s going to end up costing $5 / month per domain name.
That means if I wanted to protect all of my course sites as well as this site (which is 4 sites at the time of writing this article) I would need to spend $20/month for SSL certificates. No thanks!
That’s way more expensive than most SSL vendors. They typically charge $10 per year.
Solved before, new ones aren’t shared any more.
Cloudflare hijacks your DNS, which means their servers are hit first when someone tries to resolve your domain name, then it in turn sends the traffic to your server. So ignoring the SSL issues we went over above, you may experience much slower load times on your site when using Cloudflare (especially if you use their free plan).
They are a reverse proxy type of CDN, that’s their whole point, completely unrelated to SSL. Most likely there are much better load times, since paths are better in customer ↔ Cloudflare ↔ origin than direct customer ↔ origin. Also they can cache your content, reducing load on your server if configured correctly obviously.
Unlike Cloudflare, there’s no monthly fees or additional fees for SSL certificates. Once you have it all configured, you can sit back and relax while cron and Let’s Encrypt does everything for you. It’ll work for life and it’s free.
Cloudflare has also a great and unlimited free plan, with global CDN, not shared SSL certificate with multiple other benefits.
This guy is basically trying to sell his course, which is fine by me, but it’s not really fair. Let’s Encrypt is great, but it’s not really a comparison with Cloudflare, you can use them both.