Using cPanel to set up Cloudflare for users, advantages, disadvantages and setup.
Subject: Using cPanel to set up Cloudflare for users, advantages, disadvantages and setup.
Transcript:
Downsides in setting up Cloudflare for client's using cPanel:
Cloudflare within cPanel is only useful for clients whose primary domain for SEO is www.domain. If client uses a domain without www. then the cPanel setup should be discouraged.
Likewise, Cloudflare within cPanel will not allow a client to use Universal SSL.
The only way is to disable CloudFlare through cPanel, then return to the Cloudflare.com account and set up domain manually.
Upside for offering Cloudflare through client's using cPanel:
If www. is the primary domain then setup is just a click or two to complete.
Step by step for setting up Cloudflare for client within cPanel:
First screen step below.
Notice, I have enabled Cloudflare by clicking the cloud symbol to right of the domain:
Client will then be sent an email for account password setup:
Password screen:
After login, you'll be redirected to the Overview screen for review:
A few notes:
1. By default HTTP/2 will be enabled (if server allows this)
2. If non-www.domain works, then a 301 redirect should be put in place such that www.domain is the only option for page loading.
3. Website owners who wish to use the Cloudflare with SSL cannot use the Cloudflare + cPanel setup option.
4. Sites running solely as non-www, like HackGuard.com should not use the Cloudflare + cPanel setup option. To disable cPanel connection to Cloudflare just deactivate within cPanel, then set up manually:
+++
This concludes the "Using cPanel to set up Cloudflare for users, advantages, disadvantages and setup.", article by Jim Walker, https://tvcnet.com
Help us caption & translate this video!
http://amara.org/v/HiMG/