No. It’s not the case. I’m running another testing instance on the same server, and the plugin works fine there. So I thought it’s a matter of plugins.
I’ve disabled all of the plugins on a product instance. It didn’t help.
I did the same operation on a testing instance. The Cloudflare plugin works fine there.
The only difference that I have between testing and production instance is the protocol (HTTP vs. HTTPS) that was configured. But when I disabled the https on a production, still I wasn’t able to authorize with the Cloudflare form.
So I tried to play with directly accessing admin-ajax.php file with the action=cloudflare_proxy parameter. For testing instance, I get 0 value displayed in the browser. For the production instance, I have a null value.
So I did the same test with admin-ajax.php file and action parameter on the production instance only.
When HTTPS is configured in WordPress, I get:
null for accessing the file via HTTPS
0 for accessing the file via HTTP
When HTTP is NOT configured in WordPress, I get:
0 for accessing the file via HTTPS
null for accessing the file via HTTP
So it looks like the problem is either on the production instance or there is not covered edge case in the Cloudflare plugin that is the root of the problem. I don’t know when the admin-ajax.php file can return null. Maybe that’s a good trace to follow.
But that’s it. This is everything that I can do on my side.
-
This reply was modified 8 years, 5 months ago by
xysiu.