• Resolved visionviper

    (@visionviper)


    I get the connect timeout error:
    Jetpack could not contact WordPress.com: register_http_request_failed. This usually means something is incorrectly configured on your web host. Operation timed out after 15000 milliseconds with 0 bytes received

    When I run the Jetpack compatibility test I get:

    TEST: HTTP Connection
    
    Array
    (
        [headers] => Array
            (
                [server] => nginx
                [date] => Tue, 01 Oct 2013 18:07:35 GMT
                [content-type] => text/plain;charset=utf-8
                [connection] => close
                [vary] => Cookie
                [x-pingback] => http://jetpack.wordpress.com/xmlrpc.php
                [expires] => Wed, 11 Jan 1984 05:00:00 GMT
                [cache-control] => no-cache, must-revalidate, max-age=60
                [pragma] => no-cache
                [x-hacker] => Jetpack Test
            )
    
        [body] => OK
        [response] => Array
            (
                [code] => 200
                [message] => OK
            )
    
        [cookies] => Array
            (
            )
    
        [filename] =>
    )
    TEST: HTTPS Connection
    
    Array
    (
        [headers] => Array
            (
                [server] => nginx
                [date] => Tue, 01 Oct 2013 18:07:35 GMT
                [content-type] => text/plain;charset=utf-8
                [connection] => close
                [vary] => Cookie
                [x-pingback] => http://jetpack.wordpress.com/xmlrpc.php
                [expires] => Wed, 11 Jan 1984 05:00:00 GMT
                [cache-control] => no-cache, must-revalidate, max-age=60
                [pragma] => no-cache
                [x-hacker] => Jetpack Test
            )
    
        [body] => OK
        [response] => Array
            (
                [code] => 200
                [message] => OK
            )
    
        [cookies] => Array
            (
            )
    
        [filename] =>
    )
    TEST: Self Connection
    
    WP_Error Object
    (
        [errors] => Array
            (
                [http_request_failed] => Array
                    (
                        [0] => Operation timed out after 5000 milliseconds with 0 bytes received
                    )
    
            )
    
        [error_data] => Array
            (
            )
    
    )
    TEST: Self Connection (HTTPS)
    
    WP_Error Object
    (
        [errors] => Array
            (
                [http_request_failed] => Array
                    (
                        [0] => Operation timed out after 5000 milliseconds with 0 bytes received
                    )
    
            )
    
        [error_data] => Array
            (
            )
    
    )

    Which at first, would seem to indicate a problem with xmlrpc file. But when I visit it I get the expected:
    XML-RPC server accepts POST requests only.

    I'm not sure where to go from here in troubleshooting.

    http://wordpress.org/plugins/jetpack/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter visionviper

    (@visionviper)

    The Core Control tells me cURL, PHP Streams and PHP fsockopen() are all available and working.

    Using the logging feature I also verified that the Jetpack request is going out as a cURL request to POST to the Jetpack URL.

    I know my server can reach out to jetpack.com because if I just do a simple wget it works just fine.

    Thread Starter visionviper

    (@visionviper)

    I went ahead and used the Core Control trick of disabling cURL transport, activating and then enabling it again. It was certainly not my preferred solution as I wanted to figure out what the root cause was but I also didn’t want to wait forever.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Unable to connect to WordPress.com’ is closed to new replies.