Comments time out

A time-out could indeed happen if you were to write the comment and wait a few hours before to submit it, but it shouldn’t happen with a comment you’ve just pasted into the comment form.

Could you post your site URL here, so I can have a look?

If you want it to remain private, you can also contact us via this contact form:
https://jetpack.me/contact-support/

Thanks!

Hi there. THANK YOU for your help!
This is really important to me.

My site is: https://LuciFit.com
My reader said he took maybe 25 minutes to compose his post. Then the copy and paste just led him directly to another time out.

Can you contact your hosting provider and explain to them that we are unable to access your blog via cURL, which is needed in order to use Jetpack on your site.

You can let them know we tested the following:

1. Check for access to xmlrpc.php via browser:
https://lucifit.com/xmlrpc.php

That test returned “XML-RPC server accepts POST requests only.” which is a valid result.

2. Check for access via cURL by running the following command from the command prompt:
curl -A "Jetpack by WordPress.com" -is -H 'Content-Type: text/xml' --data '<?xml version="1.0"?><methodCall><methodName>demo.sayHello</methodName><params></params></methodCall>' 'https://lucifit.com/xmlrpc.php' && echo

The cURL test returned the following invalid result:

HTTP/1.1 408 Request Timeout
Connection: close
Pragma: no-cache
cache-control: no-cache
Content-Type: text/html
Content-Length: 514

Please provide the information above to your hosting provider so that they can correct the server settings to allow cURL access.

Once you sort out that issue, please disconnect and reconnect Jetpack to refresh your connection settings – that should sort out the timeout issue with the comment form.

Let me know if you have any questions.

Hi there. It took me a little while to get to doing this. But when I did, my host (GoDaddy) said they have nothing to do with cURL and I need to Google it and figure it out myself.
Honestly, I use WP because I’m not a programmer. There’s got to be a better fix for this.

I’m afraid there isn’t much we can do on our end. As long as GoDaddy blocks access to your site’s XML-RPC file, you won’t be able to use plugins that use the file to connect to third-party services, like Jetpack.

I would suggest contacting GoDaddy again, and pointing them to this thread. They can also contact us directly if they need more details.

Hi there,

I finally got to someone who knows what he’s doing and he showed me how to look up the cURL info. It seems to already be accessible. You can see it here under the cURL info: https://lucifit.com/phpinfo.php

Although cURL is available, that doesn’t necessarily mean that your site’s XML-RPC file can be queried via cURL.

Unfortunately, we still get the same error reported by my colleague Carolyn above when we try to query your site’s XML-RPC file.

Could you forward that thread to GoDaddy, and ask them to post here or contact us directly if they need more details to fix that problem?

Thanks!