If your site loops forever with ERR_TOO_MANY_REDIRECTS right after you turn on Cloudflare's proxy, the fix is almost always the SSL/TLS mode. Open Cloudflare CDN in the portal, click Manage on the domain, and change SSL/TLS mode from Flexible to Full or Full (strict). Every Flashcloud hosting account gets a valid Let's Encrypt certificate on the origin server automatically, so there's no reason to use the mode built for origins that don't have one.
Why Flexible causes the loop
SSL/TLS mode controls how Cloudflare talks to your origin server, not how the visitor's browser talks to Cloudflare. In Flexible mode, Cloudflare connects to your origin over plain HTTP, on the assumption that your server has no certificate at all. Most Flashcloud-hosted sites don't work that way: once a certificate is issued, the site is usually set to send plain HTTP requests on to HTTPS (through a .htaccess rule, the WordPress site address, or a Force HTTPS setting).
So the sequence goes: Cloudflare receives an HTTPS request from the visitor, opens a plain HTTP connection to your origin, your server sees HTTP and redirects to HTTPS, Cloudflare follows that redirect back to itself, sees HTTP again from its own point of view, and redirects again. Neither side is misconfigured on its own, they disagree about which protocol the origin is running. The browser eventually gives up with the redirect error.
Full and Full (strict) both tell Cloudflare to connect to your origin over HTTPS too, which removes the mismatch. Full (strict) additionally verifies the origin certificate is valid and matches the hostname, which it will be on Flashcloud hosting since certificates are auto-issued and auto-renewed. Use Full (strict) unless you have a specific reason not to. For the full breakdown of what each of the four modes does, see Cloudflare SSL/TLS modes: Full vs Flexible on Flashcloud.
Confirming it's actually this cause
Open the URL in an incognito window with the browser's network tab open. If you see the same URL, or two URLs, repeating with 301 or 302 status codes, that's a loop. A single redirect that lands somewhere unexpected, like an old domain or the wrong protocol, is a different problem with a different fix. See Fixing ERR_TOO_MANY_REDIRECTS (redirect loops) for the other common causes, including WordPress URL settings pointing at the wrong protocol and stacked rules in .htaccess.
Everything here is managed from the Cloudflare CDN page in the portal. There's no separate cloudflare.com dashboard to check or log into. If you're not sure where that page lives relative to the rest of your account, Find your way around the portal maps out the sidebar.
After you switch the mode
The change takes effect on Cloudflare's side immediately, but browsers and any intermediate caches may hold onto the old redirect chain for a few minutes. Reload in a private window if the loop still shows up right after switching. If Full (strict) throws a certificate error instead of a loop, your origin certificate may not have issued yet, wait a few minutes and try again, or drop to plain Full temporarily while it issues.
While you're on that domain's settings, it's worth reviewing the rest of the Cloudflare CDN page, Always Use HTTPS in particular pairs well with a correct SSL/TLS mode and closes off the case where a visitor lands on plain HTTP by typing the address without https://. Every Cloudflare setting explained covers what each toggle on that page does if you want the full reference before changing anything else.
When to contact support
If you've set the mode to Full (strict), cleared your browser cache, and the loop persists, or if you're not sure whether your domain is even proxied through Cloudflare, open a ticket from Support → New ticket in the portal. A real person can check the proxy status and certificate on your account directly rather than you guessing from the outside.