fabspiderkris

Hi, running into another strange error and I thought it might be worth it to ask here.

We’re able to upload posts using the WordPress app again after talking with our hosts, they identified some issues with an external security provider.

However, I was trying to publish a new post, with no luck. So I decided to publish a test post just using some placeholder lorem ipsum text to test and this worked, which lead me to believe the error lies with the specific text I am trying to post.

This might sound a bit peculiar but the post is 1300 words long and we’ve narrowed it down to a single word that is causing the post to fail and that is:

‘Destination’

If I remove this word the post uploads fine with no errors whatsoever but If we try and upload a post containing this word from the WordPress app the upload instantly fails. If I change the world to ‘Destinatio’ the post uploads successfully.

Is there a reason why the word Destination would cause this behaviour?

Here is my application log, may be of some use: https://pastebin.com/Z6ztMYTQ

I have also forwarded to the app support.

Thank you for your help.

Hi again,

Just a quick question, are you able to offer support on the WordPress app?

I am running into some strange issues on the app. Everything is running fine on the browser and desktop versions of WordPress.com after your 2 lines of code in the .htaccess, so thanks for that.

Now when trying to save written posts as drafts, or publish posts, via the WordPress app, I get “We couldn’t complete this action, but we’ll try again later” and “1 file not uploaded, there was an error uploading this post”. It’s strange because this only seems to affect larger posts than shorter ones.

On checking the app’s application log I see the following error:

Error message: The Jetpack site is inaccessible
or returned an error: transport error - HTTP status
code was not 200 (403) [-32300], Error Type: GENERIC_ERROR

Just wondering if you have anything to help with this error? Or am I best off making a ticket? Is their separate support for the app version?

Thanks

Hi KokkieH,

Thanks for helping with this so far!

I forwarded your message to my host, and they replied with the following:

I've again, tested the logs and I'm
unable to see anything in our Haproxys
or our CDN node logs.
Would jetpack be able to advise what test
they attempted to check?

We're certainly not blocking Jetpack, as it's
a popular plugin which a lot of our customers use.
The only requests we do block are HTTP requests, which
shouldn't be needed to connect as it's a security flaw
to allow so, and as mentioned above, this doesn't affect
our other customers who use Jetpack.

A POST to xmlrpc should work, and that's all that Jetpack
has needed in the past, and is still working for our other
customers.

I'd need further details on the test they completed so I can see
what exactly is occurring. 

Please do let me know if I can help in the meantime.

Is it possible for you to expand further on the test you completed so that my host can further investigate this error?

Thanks again!

Hi,

Here is the update from my host:

“We actually don’t block Jetpack, and the XMLRPC.php file. In reference to the xmlrpc file, connections can be freely made via a post request. This should be all that is needed for them to connect to the site, as this is set a platform level and we have many people who use Jetpack with our hosting infrastructure without any issues.

Can you try removing and reinstalling Jetpack, and then set it up again? This should hopefully refresh the issue and allow a connection to be made.

Jetpack as a user-agent, is actually whitelisted so any IP whitelists which need to be done, aren’t needed as we simply operate the whitelist from the “Jetpack” name.

I hope this helps.”

—

Any ideas? I am getting constant disconnects and XMLRPC errors.

Thanks again!

• This reply was modified 6 years, 2 months ago by fabspiderkris.

Hi lizkarkosi,

I have deactivated all the plugins, deleted and reinstalled Jetpack, and ran the debugger.

I now receive:

We were unable to make an XML-RPC request to your website. Please make sure that XML-RPC is turned on and that Jetpack is installed, activated and connected with your WordPress.com account.

If you continue to get this error, please check out our troubleshooting guide or contact support.

Now I have been in touch with my host as I understand the XMLRPC file needs to be accessible for Jetpack to communicate properly. This is what they say:

I've been looking into this for you, and there doesn't appear to be any specific connection issues with the XMLRPC file from our side.

Would you be able to speak to Jetpack and speak to them regarding the issue you're having, and see if they can advise what is occurring?

I can’t leave the plugins deactivated for long as the website will not function, I hope you can help.

Thanks!

• This reply was modified 6 years, 2 months ago by fabspiderkris.

Hi Neil,

Thanks for the reply, however, this doesn’t seem to have worked.

I have changed the theme to a default WordPress theme and deactivated all other plugins, and I still get the issue.

I have attached some GIF’s to illustrate the issue:

With Date Pickers: https://media.giphy.com/media/5864S2LozMe9o9ovCk/giphy.gif

Without Date Pickers: https://media.giphy.com/media/tsX41RHC4Aucs7wG5K/giphy.gif

Thanks.

• This reply was modified 7 years, 1 month ago by fabspiderkris.