We need some real urgent help.
We are putting together a multisite solution that relies on the Cron Jobs.
The solution we implement, relies on
We have put
https://ourdomain.com/subsite/wp-cron.php in the browser, and it triggers autoresponders etc just fine.
We then put the cron jobs in the server Cron Tab, they seem trigger fine, but not really hitting our multisite subsites to get the real tasks (like sending autoresponders) executed. Yes, they are the same URLs that when put in the browser address bar, can manually trigger execution.
We then moved the cron jobs to cron-job.org which saves much more detailed responses for us. And we got this:
The developer whose solution relies on this cron job, looked into this and said: it means the call to wp-cron.php is intercepted by your Cloudflare cache and does not reach the blog. Ask the tech to add an exception to that file.
We then researched on line, and read that for Cloudflare, if there is such a conflict, we should just create another subdomain, put the cron jobs under it, and then totally bypass Cloudflare.
But this does not seem viable for us because we are on a multisite. Each subsite’s cron job has to be set up separately. We have to use
I added some page rules, telling the cache to bypass https://.ourdomain.com//wp-cron.php. The cron job save response still shows X-Cache: HIT, And there is no improvement.
What shall we do? Does it mean we have to leave Cloudflare to make this work?