• Resolved ACEkin

    (@acekin)


    Hello Emre,

    About a week ago, I received an e-mail from Cloudflare that my zone was dropped from Cloudflare and for several days I could not resolve the issue nor did I gain access to their registrar page. Clearly, I did not delete my own CF zone, nor do I know how to do that. They told me that the zone was dropped from my server IP using their API. After some help and doing some work, I regained access to my registrar page and immediately moved the domain out to another registrar. With a few hiccups, the site seems to be settling down.

    As a result of the above, I had to disable the CF integration in WPFC and remove the Cloudflare plugin as well. Since the site settled, I put it behind Cloudflare again and added the CF integration to WPFC following the instructions, and installed the CF plugin again. For some reason, the instructions seemed different from the first time I had to do it.

    Now, every time I visit the Cloudflare plugin settings page, it loads and then presents an orange bar at the bottom with “Bad request”. I have been going back and forth with Cloudflare to give them an idea of what was happening. I have a staging site with almost an exact replica of my live site and the same problem was happening there as well. Thinking that WPFC is integrated with CF, I decided to disable WPFC regular and the premium versions and the warning message disappeared from the CF plugin settings page.

    I wonder if you could provide some help in resolving that error message. I don’t know what the request is and the consequences of a request failing but it is not comforting to me.

    Thank you,

    Cemal

    • This topic was modified 3 years ago by ACEkin.

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter ACEkin

    (@acekin)

    Here is a way to view the error and how it stops after deactivating WPFC:

    View the video screen capture

    Cemal

    • This reply was modified 3 years ago by ACEkin.
    • This reply was modified 3 years ago by ACEkin.
    Plugin Author Emre Vona

    (@emrevona)

    so strange. we changed the cloudflare integration. Can you the cloudflare integration and add as below again plesae?

    https://www.wpfastestcache.com/tutorial/wp-fastest-cache-cloudflare/

    Thread Starter ACEkin

    (@acekin)

    That’s the method I used after my domain zone was dropped from Cloudflare.

    Cemal

    Plugin Author Emre Vona

    (@emrevona)

    was The Zone dropped from Cloudflare after you removing Cloudflare Integration?

    Thread Starter ACEkin

    (@acekin)

    No, with no action on my part I received an e-mail from Cloudflare telling me that the zone for keptlight.com was dropped from Cloudflare but it could be restored. I had great difficulty even getting in touch with Cloudflare support because I could not select the domain to start a ticket, but that’s a different story. During my communications with CF I told them I did not drop my zone and they told me that it was dropped by their API from my server IP.

    I repeated the integration process once more, the result is the same. I get the Bad request orange bar at the bottom if WPFC is active. I provided a HAR file to CF support and informed them that disabling WPFC eliminates the error message.

    Thanks for your help,

    Cemal

    Plugin Author Emre Vona

    (@emrevona)

    There is no action which can crop the zone.
    you can search the api.cloudflare.com on the following link and find out the request type.

    https://plugins.trac.wordpress.org/browser/wp-fastest-cache/trunk/inc/cdn.php

    By the way, there are logs on the Cloudflare.com. You can find the request for this transaction which drops the zone.

    If you contact me via email, I can help you to find the issue.
    https://www.wpfastestcache.com/contact-us/

    Thread Starter ACEkin

    (@acekin)

    I sent an e-mail.

    Cemal

    Thread Starter ACEkin

    (@acekin)

    After a series of trouble ticket communications with Cloudflare support and repeated trials of deactivating the WPFC plugin, the problem eventually did not stop when WPFC was disabled. At this point, I have no idea what is causing the bad request and I reported the situation to CF. I even tried the steps using a totally new browser in incognito mode to eliminate the browser cache interfering upon the recommendation from Cloudflare, no matter what I do, whether the WPFC is active or not, the bad request warning appears upon loading the Cloudflare plugin settings page.

    At this point, my original observation seems inaccurate about WPFC might be the culprit. I appreciated the efforts Emre put forth, looked at it on a staging site, and could not tie it to his plugin.

    Mystery continues elsewhere,

    Cemal

    Thread Starter ACEkin

    (@acekin)

    I am writing to report that this issue has been resolved with a few simple steps. `Here are the steps I followed:

    1. Used a different browser, and uninstalled the Cloudflare plugin
    2. Cleared the entire cache of the browser from the beginning and all history, cookies, everything
    3. Reinstalled the Cloudflare plugin and reconnected with my e-mail and the API token
    4. Cleared the browser history again
    5. When I logged in once more, I loaded the Cloudflare plugin settings, and the “Bad Request” message did not show up
    6. I switched to the browser I had been using, without clearing the cache, I loaded the Cloudflare plugin settings page …

    AND there was no error banner at the bottom. I visited the Cloudflare account, went to the Speed page where I saw the message that could not connect to the plugin, and the message was not there.

    The initial apparent relation to WP Fastest Cache was not there after all. I thought others may want to know that it was not caused by WP Fastest Cache, and the solution was reasonably simple.

    Cemal

    Plugin Author Emre Vona

    (@emrevona)

    Thank you very much for the detailed explanation.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Cloudflare related issue’ is closed to new replies.