Sure. I have used this combination with my Rails sites, and from the setup perspective, that’s identical.
To begin, add your domain to CloudFlare. They will automatically import whatever your current DNS host has set up as far as machine names and services. On the DNS tab for the new domain, you should see the name servers that they have assigned to you.
In my setup for ActionsForge, I have that domain pointed to kim.ns.cloudflare.com
and paul.ns.cloudfalre.com
. Your mileage may vary.
Once you’ve set that up, log in wherever you registered your domain. There should be a simple setting to point the domain at Cloudflare instead of using your previous DNS (which may, for convenience sake, be the domain registrar). This doesn’t change anything about your registration, just where the domain name is mapped over to the numerical address system (IP) of the Internet. There is no requirement that your domain be registered by the same company that manages DNS.
At this point, your site should still be working. If it isn’t, go outside and wash the car or something, because refreshing your browser and swearing will not change anything. The Domain Name System is distributed, which means that each node needs to synch with all the others before there is a clear and consistent picture of which names map to which servers. Time heals all wounds, and routing errors.
Finally, to switch to SSL on your site, without changing anything else about your Web server, simply move to the SSL/TLS tab of Cloudflare, and switch the mode from Off (default) to Flexible. This should start working right away, Note that this only encrypts traffic between the browser and CloudFlare, not between CloudFlare and your server. This is correct and okay, unless you handle money or secrets, in which case you must set up SSL on your Web server, so that the entire signal chain is encrypted. If you do that, then you would change the settings from Flexible to Full (strict), but only after you have completed the setup of SSL on your Web server.
CloudFlare sits between your server and the browser clients on the wider Web. They provide a distributed CDN, which speeds up the delivery of your site around the world. They also can automatically compress your site resources, which further speeds things up. And if you get attacked by a DDOS, they will automatically respond by denying the attackers. It’s a good thing to have, whether or not you need SSL.
Walter
On May 9, 2020, at 6:38 AM, Victor email@hidden wrote:
Hi again.
I would like to make my site above secure as in https.
I have downloaded the freeway action HTTPS CDN helper and I know I can apply that action to all pages of the website (There are not many)
I use Cloudflare free SSL to generate a free SSL (I have not set this up yet with cloudflare as I know I must point the domain to cloudflare but I dont want to do that yet until I know how to set it up correctly)
After i apply the action I dont know what to do next with freeway or Cloudflare.
Has anyone used this action and cloudflare or another free ssl and converted their freeway site to https successfully and let me know what method and order I need to do to do this properly without breaking the website.
Thanks in advance
Victor
http://eltorosalou.com
freewaytalk mailing list
email@hidden
Update your subscriptions at:
Information for existing FreewayTalk / Groups.io users - Site Feedback - Softpress Talk
freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options