token_http_request_failed

  • Unknown's avatar

    I have installed Jetpack using the WP installer but I get this error:

    (I know there are others getting this error and I’ve been through the forums but can’t find the solution)

    Jetpack could not contact WordPress.com: token_http_request_failed. This usually means something is incorrectly configured on your web host. name lookup timed out

    I have WP installed on my own server and I have root access to the server via Putty, FTP or admin on Plesk. I am running PHP 5.2+ and WP is installed in the httpdocs folder of my vhost.

    Any help would be greatly appreciated.
    Blog url: http://www.ethicleanse.co.uk/blog

  • Unknown's avatar

    When I try to visit your site, and your XML-RPC file, I’m unable to load it. Can you make your XML-RPC file publicly accessible before trying to activate Jetpack?

  • Unknown's avatar

    For some reason the site is now down but is still on the server. I am running CentOS on a standalone server that I own and manage directly in the datacentre.

    The home site is on a shared IP address

    I don’t know how to make the XML-RPC file publicly accessible. I shall look online now to see if I can figure it out.

    Regards, Ray Jones

  • Unknown's avatar

    Update: I can find the xmlrpc.php file in the WordPress folder but I can’t access any of the WordPress pages from the browser.

    Not sure what’s occured here as I haven’t changed anything and the pages are all physically on the server?

    Regards, Ray Jones

  • You’ll need to get your site back online. Jetpack won’t be able to connect a site that’s offline.

  • Unknown's avatar

    OK I’ve re-installed WP here: ethicleanse.co.uk/ecoblog/

    I’ve checked XML-RPC (ethicleanse.co.uk/ecoblog/xmlrpc.php) and get the following:

    XML-RPC server accepts POST requests only.

    There are no plugins installed at present.

  • Ok, that means that the xmlrpc file is functioning properly. Are you still seeing the same exact error message?

  • The topic ‘token_http_request_failed’ is closed to new replies.