• Resolved w-sky

    (@w-sky)


    Jetpacks publicize recently stopped working and in other threads discussing Jetpack and publicize problems I found the advice to create a cron job to help Jetpack. However the recent problem on our site was solved by deconnecting and reconnecting Jetpack once.

    Despite of Jetpack and publicize working fine now (for example, page statistics and auto plugin updates), the debug page sometimes reports that Jetpack is not connected properly.

    If problems keep to occur, should I create a server cron job to solve Jetpack problems permanently? As for now, no server cron job or changes to WP Cron have been applied on our site.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support KokkieH

    (@kokkieh)

    Hi there,

    Despite of Jetpack and publicize working fine now (for example, page statistics and auto plugin updates), the debug page sometimes reports that Jetpack is not connected properly.

    Are you referring to the debug page at wp-admin/admin.php?page=jetpack-debugger? Does it give any more specific details than that Jetpack is not connected properly?

    If this happens again you can click the Advanced debug link on that page and send us that info via the contact form also on that page so we can take a look? But it’s difficult to say what’s going on without more information.

    f problems keep to occur, should I create a server cron job to solve Jetpack problems permanently? As for now, no server cron job or changes to WP Cron have been applied on our site.

    If WP Cron is working correctly on your site you shouldn’t need to specifically create a cron job. Cron failures is also only one possible cause for Publicize failures and other Jetpack problems – it could also be caused by several other things.

    Thread Starter w-sky

    (@w-sky)

    Okay thanks! Yes there is more information. I did not notice at first that I can expand the short red “It looks like your site can not communicate properly with Jetpack.” message.;)

    Here is the full error message:

    SELF:
    							Array
    (
        [headers] => Requests_Utility_CaseInsensitiveDictionary Object
            (
                [data:protected] => Array
                    (
                        [server] => nginx
                        [date] => Mon, 19 Mar 2018 13:31:19 GMT
                        [content-type] => text/plain;charset=utf-8
                        [expires] => Wed, 11 Jan 1984 05:00:00 GMT
                        [cache-control] => no-cache, must-revalidate, max-age=60
                        [x-hacker] => Jetpack Test
                        [x-ac] => 3.fra _dfw
                        [strict-transport-security] => max-age=15552000
                    )
    
            )
    
        [body] => {"error":"Unknown Error","error_description":"An unknown error has occurred."}
        [response] => Array
            (
                [code] => 400
                [message] => Bad Request
            )
    
        [cookies] => Array
            (
            )
    
        [filename] => 
        [http_response] => WP_HTTP_Requests_Response Object
            (
                [response:protected] => Requests_Response Object
                    (
                        [body] => {"error":"Unknown Error","error_description":"An unknown error has occurred."}
                        [raw] => HTTP/1.1 400 Bad Request
    Server: nginx
    Date: Mon, 19 Mar 2018 13:31:19 GMT
    Content-Type: text/plain;charset=utf-8
    Transfer-Encoding: chunked
    Connection: close
    Expires: Wed, 11 Jan 1984 05:00:00 GMT
    Cache-Control: no-cache, must-revalidate, max-age=60
    X-hacker: Jetpack Test
    X-ac: 3.fra _dfw
    Strict-Transport-Security: max-age=15552000
    
    {"error":"Unknown Error","error_description":"An unknown error has occurred."}
                        [headers] => Requests_Response_Headers Object
                            (
                                [data:protected] => Array
                                    (
                                        [server] => Array
                                            (
                                                [0] => nginx
                                            )
    
                                        [date] => Array
                                            (
                                                [0] => Mon, 19 Mar 2018 13:31:19 GMT
                                            )
    
                                        [content-type] => Array
                                            (
                                                [0] => text/plain;charset=utf-8
                                            )
    
                                        [expires] => Array
                                            (
                                                [0] => Wed, 11 Jan 1984 05:00:00 GMT
                                            )
    
                                        [cache-control] => Array
                                            (
                                                [0] => no-cache, must-revalidate, max-age=60
                                            )
    
                                        [x-hacker] => Array
                                            (
                                                [0] => Jetpack Test
                                            )
    
                                        [x-ac] => Array
                                            (
                                                [0] => 3.fra _dfw
                                            )
    
                                        [strict-transport-security] => Array
                                            (
                                                [0] => max-age=15552000
                                            )
    
                                    )
    
                            )
    
                        [status_code] => 400
                        [protocol_version] => 1.1
                        [success] => 
                        [redirects] => 0
                        [url] => https://jetpack.wordpress.com/jetpack.testsite/1/?url=https://hanfjournal.de/xmlrpc.php
                        [history] => Array
                            (
                            )
    
                        [cookies] => Requests_Cookie_Jar Object
                            (
                                [cookies:protected] => Array
                                    (
                                    )
    
                            )
    
                    )
    
                [filename:protected] => 
                [data] => 
                [headers] => 
                [status] => 
            )
    
    )
    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Thanks for the extra details. Your site appears to be properly connected to WordPress.com right now, and your last post was sucessfully pushed to Publicize:

    You can consequently ignore the messages on the Debug page for now.

    If you start having trouble with Jetpack features again, Can you please use the contact form on that debug page to contact us and send us information about your site?

    Thank you.

    Thread Starter w-sky

    (@w-sky)

    Okay, thanks! Will do so. Yes it is just a little confusing when Jetpacks says “It looks like your site can not communicate properly with Jetpack” despite of everything seems to work fine right now.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Jetpack connection problems – sometimes. Cron job needed?’ is closed to new replies.