Support » Plugin: Jetpack by WordPress.com » Can't connect Jetpack to WordPress anymore, details inside (Always blank page)

  • Resolved quorn23

    (@quorn23)


    Hi there,

    I disconnected Jetpack, as i was not able to connect Klout (klout.com) with my WordPress Blog. After the disconnect of Jetpack, i tried to reconnecting again. This results in a blank page.

    So what i tried so far:
    Disabled all plugins and set page to the default template – Same effect.
    Testing the xmlrpc.php link. (https://amoklauf.ch/blog/xmlrpc.php – The normal message (…POST…) appears, looks good.
    Added the Jetpack using Port 80 option from the support page – Same effect (blank page)
    Added the Server 443 Port option from the support page (while removing the Port 80 option) – Same effect.
    Added that Jetpack never uses https – Still same blank page.

    Logged into WordPress.com and removed (unlink from Jetpack) site, now wordpress.com tells me i do not have a site set up. – Same effect sadly.

    In a last resort i tried to add a rewrite rule from xmlrpc.php to /blog/xmlrpc.php as searching around i read that the Connector expects the php file in the root. – same effect.

    My blog is set up that the index.php is in the root (it loads /blog/wp-blog-header.php) This i’ve done following the wordpress manual.

    I recently changed from http to https (I did the SSL check from ssllab the certificate is Grade A) and everything works fine, besides connecting Jetpack.

    When i click on Debug on the bottom i get a page telling me Jetpack can’t communicate with my Webpage.

    On https://jetpack.com/support/debug/
    i get the following error:
    We were unable to validate a security token for Jetpack communication. Please try disconnecting Jetpack from your WordPress.com account, and connecting it again.

    I also removed Jetpack and reinstalled it to have a fresh installation. Effect remains the same.

    Basically i tried everything i could find on your support pages regarding the issue, but now i’m lost. Any help would be really appreciated.

    Kind Regards,
    Gabe

    https://wordpress.org/plugins/jetpack/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    It looks like you’ve applied most of the rules described here:
    https://jetpack.com/support/getting-started-with-jetpack/configure-jetpack-cloudflare/

    Could you give it another look, make sure it’s all done?

    Once you’ve done so, could you try the following:

    1) Go the Jetpack menu in your dashboard
    2) Click on “My Jetpack” at the top of the page.
    3) Click on “Disconnect Site from WordPress.com” if your site is currently connected to WordPress.com.
    4) Confirm the disconnection.
    5) Click on the Connect button to connect your site to WordPress.com again. You might receive a 520 error from CloudFlare when you do so, but you can ignore it and refresh the page to access your dashboard again. Jetpack should be connected.

    Let me know how that goes.

    Hi Jeremy,

    Issue remains the same, besides that i’m now getting the same error with http and https on https://jetpack.com/support/debug/

    We were unable to validate a security token for Jetpack communication. Please try disconnecting Jetpack from your WordPress.com account, and connecting it again.

    I did just find out i can click on the error at https://amoklauf.ch/blog/wp-admin/admin.php?page=jetpack-debugger

    Edit -> i do not have “My Jetpack” and on WordPress.com i do not have it connected anymore. I disconnected the page everywhere i was able to.

    This is the error:

    SELF:
    	Array
    (
        [headers] => Array
            (
                [server] => nginx
                [date] => Mon, 13 Jun 2016 16:42:29 GMT
                [content-type] => text/plain;charset=utf-8
                [connection] => close
                [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
                [x-ac] => 3.fra _dfw
                [strict-transport-security] => max-age=15552000
            )
    
        [body] => {"error":"Could not validate security token","error_description":"We were unable to validate a security token for Jetpack communication. Please try disconnecting Jetpack from your WordPress.com account, and connecting it again."}
        [response] => Array
            (
                [code] => 400
                [message] => Bad Request
            )
    
        [cookies] => Array
            (
            )
    
        [filename] =>
    )

    Oh and i have SSL in Cloudflare on "Full (strict)", so i'm not sure if i need the flexible ssl plugin. I do have a valid SSL Certificate for my domain. Reading the description on on Cloudflare that's what i need if i have a valid one.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    Can you please use Jetpack’s Debugger module to send us some more information about your site?

    1. Go to Plugins > Add New > Upload, and upload this little plugin to your site:
      https://kraft.im/wp-content/lib/helpers/bkjpdebug.zip
    2. Navigate to Tools->Jetpack Debug
    3. Copy the results.
    4. Send them to us via this contact form:
      http://jetpack.com/contact-support/

    Thanks!

    Hi Jeremy,

    Debug log send, i used the url to this thread as the “short description”

    Spoiler alert, my untrained eye for jetpack debug logs only spots Self : Fail and the error from above.

    Let me know if i can provide additional information.

    (The source code from the blank page is blank too, something i forgot to mention but also checked)

    Hi Jeremy,

    I got it to work (i think)

    But i’m rather puzzled.

    What i did.

    Disabled what i did in Step 8. here:
    https://jetpack.com/support/getting-started-with-jetpack/configure-jetpack-cloudflare/

    – Jetpack still gives me a blank page.
    So i went ahead and disabled all plugins again.
    – Jetpack activates(connects) like a charm.
    Next step, disconnected Jetpack and activated all plugins again. – again blank screen.
    So it seems the https was causing an issue and one of my plugins causing another issue. Yay for IT.

    Now i will reconfigure my Jetpack (linking accounts etc.) and then proceed to activate one plugin after another. As i’m running a rather tight ship with my plugins, what is the best way to debug which plugin causes Jetpack to “crash”? I will keep an eye on the jetpack-debugger, but is there a good way to get quicker to the answer what could cause the issue?

    I re enabled all my plugins and the Jetpack-debugger still says all good with my connection with Jetpack.

    I haven’t reactivated the Flexible SSL Plugin, as i have full strict ssl as mentioned.

    My remaining question: Set the port to 443 by adding the following to wp-config.php:
    1
    2
    3
    4
    /**
    * Set port to 443
    */
    $_SERVER[‘SERVER_PORT’] = 443;

    is this needed? As i have full ssl activated on cloudflare anyway? Or will removing it having a negative impact on the Jetpack connectivity?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    is this needed? As i have full ssl activated on cloudflare anyway? Or will removing it having a negative impact on the Jetpack connectivity?

    It’s best to keep this, to make sure Jetpack and other third-party services always know how to communicate with your site.

    As i’m running a rather tight ship with my plugins, what is the best way to debug which plugin causes Jetpack to “crash”?

    I’d recommend adding the following to your site’s wp-config.php file:

    define('WP_DEBUG', true);
    
    if ( WP_DEBUG ) {
    
            @error_reporting( E_ALL );
            @ini_set( 'log_errors', true );
            @ini_set( 'log_errors_max_len', '0' );
    
            define( 'WP_DEBUG_LOG', true );
            define('WP_DEBUG_DISPLAY', false);
            define( 'CONCATENATE_SCRIPTS', false );
            define( 'SAVEQUERIES', true );
    
    }

    Once you’ve done so, trigger the blank page again, and then check the wp-content/debug.log file for errors. It should tell you more.

    You can then replace define('WP_DEBUG', true); by define('WP_DEBUG', false);.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Can't connect Jetpack to WordPress anymore, details inside (Always blank page)’ is closed to new replies.