• Site Health reports “HTTPS is already supported for your website.”

    I didn’t know why. Don’t have SSL certificate on hosting provider.

    Turns out WordPress is detecting a certificate via Cloudflare, which I use together with W3 Total Cache?
    [Learned this through switching to development mode in Cloudflare]

    I tried the “”Update your site to use HTTPS” button; but then had “too many redirects” issue trying to access admin pages.
    Reported issue here; fixed redirects by changing home and siteurl in database, from https back to http.
    – maybe these were the only changes WordPress made in attempting migration, before stalling???

    I have tried searching, but haven’t found info on the migration and Cloudflare.

    Is there a problem, or just me? [and if not Cloudflare, what … ]

    I wonder if, before attempting one-click migration, best to choose “development mode” for Cloudflare; would that work?

    A bit more info from Site Health might be useful; such as about the SSL certificate detected.

    Also, there’s no “undo” button or information.
    – I had delayed before trying this migration, as didn’t know what would happen if things went awry.
    Hopefully just changing siteurl and home is sufficient.

    • This topic was modified 2 years, 10 months ago by docmartinhk.
Viewing 2 replies - 1 through 2 (of 2 total)
  • You’re using Cloudflare as a web proxy. That means all requests to your domain go to Cloudflare, and Cloudflare, behind the scenes, passes the request to your hosting provider.

    So as far as your site’s visitors are concerned, your site is hosted with Cloudflare. So if there are SSL certificates installed on your domain at Cloudflare, then, of course, WordPress will detect it just like any useragent would.

    Most HTTPS redirect loops with Cloudlare boil down to incorrect SSL/TLS encryption mode selected in the Cloudflace dashboard. Please see: https://support.cloudflare.com/hc/en-us/articles/200170566

    If you have no need for your site to use HTTPS, then there’s nothing more to do.

    But if you still need your site to use HTTPS, you’ll need to try the various Cloudflare SSL/TLS encryption modes to see which one will allow you to access your website over HTTPS without any redirect loops. Then you can change your WordPress site’s URL to use HTTPS.

    Good luck!

    Thread Starter docmartinhk

    (@docmartinhk)

    Update: in case any use to anyone.

    Just done a migration to https – as wanting to try and sell photos thro site.

    I tried disabling Cloudflare thro W3 Total Cache settings; the one click upgrade via Site Health again didn’t work.

    Instead, to Cloudflare: could stop caching here; I also disabled Cloudflare.

    Then, the change to https via Site Health worked.
    Had another issue, with login not enabling me to administer site.
    Tried a few things; searched online, and found I had to add these lines of code to around top of wp-config:

    /** SSL */  
    define('FORCE_SSL_ADMIN', true);  
    // in some setups HTTP_X_FORWARDED_PROTO might contain  
    // a comma-separated list e.g. http,https  
    // so check for https existence  
    if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false)  
        $_SERVER['HTTPS']='on';
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘One-click HTTPS migration and Cloudflare clash?’ is closed to new replies.