Cloudflare Blocking Jetpack Access to Wordpress.com

RollToReview

Hi Ezoic,

I just moved over to Ezoic but had users complain they could no longer post comments via the wordpress.com reader.

I did some digging and in the response to the POST request I got this error "The Jetpack site is inaccessible or returned an error: transport error - HTTP status code was not 200 (409)"

According to Jetpack's support:

Error code 409 – XML‑RPC is not responding correctly

Sites that proxy traffic through Cloudflare or other CDNs might see a 409 in the Debugger Tool.

If you are receiving this error on Jetpack Debugger, and you are using Cloudflare, you should bypass Cloudflare’s features for xmlrpc.php and WP Admin. Details here.

After reading that I looked to see if Ezoic would allow me to manage my Cloudflare settings but there is no options there.

Is this something that could be sorted out.

Thanks,
Dave

Lindsey_

Hi there - Lindsey here. We can certainly take a look at this, however, to adjust your Cloudflare settings, this will need to be done within your Cloudflare account versus through Ezoic. While we do link with your Cloudflare account for integration and security purposes, the Cloudflare settings for this can be found within your CF account.

If you're unsure of how to access these settings, however, please let us know and we can try to point you in the right direction. :-)

RollToReview

Hi LindseyW,

That would be great, I just signed up to Ezoic a week or so ago. I don't have an existing Cloudflare account, so is that created or somehow linked with my Ezoic account?

Thanks,
Dave

cjsmith

Hi Dave,

Your wp-admin is already excluded by default. I believe that is also the case for xmlrpc.php but can double-check on that. However, the URL Jetpack have linked you to is pretty vague - can they be more specific regarding which of Cloudflare's features need to be bypassed and how? On a separate note, I'm able to post comments on your site just fine (albeit I am getting Ezoic's CMP in the comments window, which we can look into separately) - is the issue intermittent or has it been resolved?

If it has not been resolved, I believe the best thing to do might be to mark the directory where the Jetpack Comments section lives completely static. Are you able to provide the directory that it's on?

RollToReview

Hi Chris,

I'm still getting the error, and it happens every time I go to comment. Noting that it only happens through Wordpress.com Reader, where my posts show, but still end up with the error as shown above. People can comment on my site if they visit it normally.

I haven't reached out to Jetpack yet, as this problem only started when I switched DNS over to Ezoic. So I'm hoping you can help me out. Everything else has been my own investigation. Another thing that points to the XML-RPC is the Jetpack Troubleshooting - I've attached a screenshot below.

Although if I execute that CURL command, I get the expected output. So I'm kind of at a loss as to what the problem is...

Sorry for the hassle, but not sure what you mean by 'mark the directory where the Jetpack Comments section lives' on. Otherwise, happy to provide anything required.

cjsmith

Thanks for the additional information. I'm going to open a bug with our Tech team and provide them with all the information you have kindly given us. I'll be in touch once I hear back from them, however please note that this won't be until after the weekend. Thanks for your patience and understanding in the meantime.

RollToReview

Brilliant, thanks Chris. Appreciate your efforts so far.

cjsmith

Hi Dave,

Just wanted to follow up here to let you know that we haven't forgotten about you - our engineers have been looking into this but haven't yet found a solution that sticks. As soon as they do, I'll let you know.

Thanks,

Chris

RollToReview

Thanks for the update Chris, looking forward to getting this one resolved.

cjsmith

Hi Dave,

Apologies for the lengthy delay on this. The long and short of it is that our team haven't been able to fix this on another site so have had to disable the Cloudflare app altogether. The issue on that site was slightly different albeit the cause was the same so there is one more thing we can try for your site before resorting to disable Cloudflare in order to get the desired functionality to work. We've added a couple of page rules to Cloudflare - could you let us know whether comments through the WordPress Reader are now working?

If not, please let us know if you're okay with us disabling the Cloudflare app. Apologies if that's all we can do in this case but seems there's an incompatibility that can't be resolved.

Best,

Chris