Facing Error : 1002

Hi @arj23,
Can you show us a screenshot of the page rule section of your CF dashboard? Also, it is really hard to track down exactly what’s happening without the logs as in the logs we can see exactly what’s going on and what response Cloudflare is giving when we talk to them via API.

Hi @isaumya

Thanks for the prompt reply.

PFA the screen shot of cloudflare link

Regarding logs, am using google app engine, no write access available in it. We use a plugin called “Google Cloud Storage plugin”. It helps to upload images and other temp files to a separate storage server. But your plugin logs are not created in that storage. If possible consider this as a feature request in your future release.

Thank you

Hi @arj23,
Can you Click on RESET ALL, and try to resetup the plugin and see if you see the same issue? As without the logs, it’s so hard to see what’s happening behind the scene.

It’s not working after reset. But i’m not getting the error 1002 when I try to disable the cache.

I have even tried to downgrade the plugin to version 4.3.6. But issue still persist.

Thank you for the support. Will try to get logs.

Btw found a minor bug : Click ResetAll-> in the confirmation box click cancel button. But it continues to reset.

PFA Logs here

Logs are created after reset all and configuring again with cloudflare.

Kindly help me to find the issue.

Hi @arj23 ,
the error is:

Your zone already has an existing page rule with that URL. If you are modifying only page rule settings use the Edit Page Rule option instead

Please delete the page rules on CF then reset all and enable the page cache again. This should solve your problem.

Btw found a minor bug : Click ResetAll-> in the confirmation box click cancel button. But it continues to reset.

Thank you, I fixed this on upcoming version.

Let me know

Still facing the issue.

Deleted the page rule in CF and reset all in plugin.

Then gave the API key details and domain name. It showed successfully created the page rule. Verified the page rule in CF as well (screenshot)

Then clicking Test Cache, shows a error pop up
“Page caching seems not working for both dynamic and static pages.”

Verified in website, cache is not working. Response headers are shown here

Attached the new logs for the reference here. (Log format will look slightly different, since am retrieving the logs from a database. Ignore it)

Hi @arj23,
First of all the x-wp-cf-super-cache-cookies-bypass: swfpc-feature-not-enabled is supposed to be like that unless you are using the worker mode and added custom cookie name for which you want to bypass the caching. Screenshot: https://i.imgur.com/FsVsfaT.png

Now coming to your website, when I am checking the response header I see:

cache-control: s-maxage=604800, max-age=60
content-encoding: gzip
content-length: 63166
content-type: text/html; charset=UTF-8
date: Sat, 19 Dec 2020 05:25:35 GMT
link: <https://potnxt.com/wp-json/>; rel="https://api.w.org/"
link: <https://potnxt.com/wp-json/wp/v2/pages/3347>; rel="alternate"; type="application/json"
link: <https://potnxt.com/>; rel=shortlink
server: Google Frontend
vary: Accept-Encoding
x-cloud-trace-context: ef806e7b035db00e25e894216621ae10;o=1
x-wp-cf-super-cache: cache
x-wp-cf-super-cache-active: 1
x-wp-cf-super-cache-cache-control: s-maxage=604800, max-age=60
x-wp-cf-super-cache-cookies-bypass: swfpc-feature-not-enabled

So, I see you cache-control has been set properly. but there is no cf-cache-status header present for any files, which is really wired.

Can you please go back to your Cloudflare dashboard and confirm the following things:
1. Development mode is disabled3
2. Site is not paused in Cloudflare
3. Go to the DNS section of Cloudflare dashboard and the orange cloud is turned on for your domains main A record and WWW cname record, I think this is the issue, as my hunch says they are currently grey.

Please check these and keep us posted.

Hi @isaumya , @salvatorefresta

It’s Working!

As you have mentioned, “WWW cname” record was not proxied in Cloudflare. After changing it to orange cloud. It worked.

Thank you very much, for spending your valuable time on this ticket.

Great! I’m closing this thread and don’t forget to write a review ??