Adding Cloudflare to a Cloudways-hosted site gives you a content delivery network, DDoS protection, and free SSL without changing your hosting plan. This guide walks through connecting the two services and configuring the settings that matter most after setup.
Why Use Cloudflare With Cloudways?
Cloudways already delivers fast hosting through SSD storage, server-side caching, and your choice of cloud provider. Cloudflare sits in front of that, adding a layer of performance and protection that Cloudways alone does not provide:
- CDN delivery – Static files (images, CSS, JavaScript) are cached on Cloudflare’s global edge network and served from the location closest to each visitor. This reduces load on your server and improves time-to-first-byte for international users.
- DDoS protection – Cloudflare filters malicious traffic before it reaches your Cloudways server.
- Free SSL – Cloudflare provides an SSL certificate at no extra cost. To avoid mixed-content warnings, set SSL mode to Full (Strict) if your Cloudways server already has a certificate installed.
- Traffic analytics – Cloudflare’s dashboard shows request volume, cache hit rate, and blocked threats in one view.
If you are still deciding whether this setup is right for you, see our overview on whether to use Cloudflare with Cloudways.
How to Connect Cloudflare to Cloudways
Step 1 – Create a Cloudflare Account
Go to cloudflare.com and sign up with your email and a password. No credit card is required for the free plan.
Step 2 – Add Your Website
Once logged in, click Add a Site and enter your root domain (for example, yourdomain.com without the www). Select the Free plan on the next screen.
Cloudflare will scan your existing DNS records. This takes up to 60 seconds. When it finishes, review the records listed and confirm they look correct before continuing.
Step 3 – Review DNS Records
Cloudflare imports your current DNS records from your registrar. Check that your A record (the one pointing to your Cloudways server IP) is present. If it is missing, add it manually: set the type to A, the name to @ (for the root domain), and the value to your Cloudways server’s IP address.
Make sure the Proxy Status for your A record is set to Proxied (the orange cloud icon) rather than DNS-only. This is what enables the CDN and protection features.
Step 4 – Update Your Nameservers
Cloudflare gives you two nameservers to copy. Log into your domain registrar (wherever you bought the domain) and replace the existing nameservers with the Cloudflare ones. Save the changes.
Nameserver changes take anywhere from a few minutes to 48 hours to propagate globally, though most complete within a few hours. Once Cloudflare detects the change, your site will be active through the Cloudflare network.
Step 5 – Set SSL Mode to Full (Strict)
This is the step most guides skip, and it causes the most problems. In the Cloudflare dashboard, select your domain, then go to SSL/TLS > Overview. Set the encryption mode to Full (Strict).
If your Cloudways server has a valid Let’s Encrypt certificate installed (which it should by default), Full (Strict) is the correct setting. Using Flexible SSL with Cloudways often causes redirect loops because Cloudways tries to force HTTPS on its end while Cloudflare handles the other direction.
Step 6 – Configure Caching and Performance
With the connection live, set the cache level to Standard in Cloudflare’s Caching > Configuration section. For WordPress sites using a caching plugin like Breeze (Cloudways’ built-in plugin), the plugin handles page caching while Cloudflare handles static asset delivery.
You can also enable Auto Minify for JavaScript, CSS, and HTML under Speed > Optimization. Avoid enabling Cloudflare Rocket Loader on WordPress sites if you notice JavaScript conflicts after enabling it.
After Setup: What to Verify
Once Cloudflare is active, check the following:
- Your site loads over HTTPS without a certificate warning
- There is no redirect loop (if there is one, check your SSL mode setting)
- The Cloudflare dashboard shows your site as Active
- Cache hit rate in the Cloudflare analytics is rising over time, indicating assets are being served from the CDN
If your Cloudways server IP changes (for example, after a server resize or migration), update the A record in Cloudflare’s DNS settings rather than at your registrar. Since Cloudflare is now your DNS authority, changes go there.
Troubleshooting Common Issues
Redirect loop after enabling Cloudflare: This almost always means your SSL mode is set to Flexible. Switch it to Full or Full (Strict) in the Cloudflare SSL/TLS settings.
Site not active after nameserver update: Allow up to 48 hours, then check in the Cloudflare dashboard. You can also use a tool like whatsmydns.net to check propagation status globally.
Images or fonts not loading: Clear both your Cloudways server cache and the Cloudflare cache. In Cloudflare, go to Caching > Configuration and click Purge Everything.
Once the setup is complete, Cloudflare runs in the background without requiring ongoing management. Our Cloudways performance and speed guide covers how Cloudflare fits alongside Varnish, Redis, and Breeze for a full Cloudways optimization stack.
