Support » Plugin: Jetpack by WordPress.com » Jetpack 4.4.1 500 Error

  • Resolved bambino

    (@babybitch1976)


    I just downloaded and activated Jetpack 4.4.1 and get a server error 500 when I click the Connect To WordPress button.

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

    (@jeherve)

    Jetpack Mechanic πŸš€

    Could you try to log in to your site via FTP or CPanel, delete the existing Jetpack plugin folder, and reinstall the plugin manually as explained here:
    http://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation

    You’ll find the Jetpack plugin folder here:

    
    wp-content
       plugins
         jetpack - DELETE THIS FOLDER
    

    If you’re not sure how to do this, you can ask your hosting company for help. They should also have documentation explaining how to edit or remove files from your site using FTP or a File Manager in your admin panel.

    Let me know how it goes.

    Same here. I have deleted the folder and manually re-installed, same error. I have a multisite install, tried it with Jetpack active on the network and active on just one site, same error. All other plugins are disabled, theme is Twenty Sixteen.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    @katjames17 Could you add 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, try to reproduce the error, and then check the wp-content/debug.log file for errors. You can paste the results here. You can then replace define('WP_DEBUG', true); by define('WP_DEBUG', false); in the code above.
    Let me know what you find!

    I also called my web host, not necessarily because of this, but I had 2 site outages earlier in the day for a few minutes at a time (score one for Jetpack Monitor!) and they recycled my application pool.

    On the second attempt, I first got a blank screen with “Are you sure you want to do this?” and a link saying “Try again.” So I clicked the link, went back to the page with the link to connect Jetpack to WordPress, clicked that and it connected.

    I did look at the debug log and here’s what was in there:

    [22-Nov-2016 22:35:07 UTC] PHP Warning: mysql_query(): MySQL server has gone away in D:\Hosting\7268586\html\wp-includes\wp-db.php on line 1870
    [22-Nov-2016 22:35:07 UTC] PHP Warning: mysql_query(): Error reading result set’s header in D:\Hosting\7268586\html\wp-includes\wp-db.php on line 1870

    Whoops, no, it didn’t connect. I have an error of

    cURL error 18: transfer closed with 2168 bytes remaining to read

    Another attempt and I have Error Details: 504 and the same 2 lines in the debug log, just different time stamps.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    @katjames17 Are you hosting this on a VPS or are you using a shared host?

    If the former:

    1) Check your system logs ( /var/log/messages and/or /var/log/syslog ) to see if MySQL is getting shut down due to OOM conditions or
    2) if it’s not getting shut down, try increasing the max packet size

    If shared host:

    Put in a ticket with your host requesting information similar to the above, they should be able to investigate a bit more to find out what happened.

    I do have shared hosting and they said it might be a network issue that’s making the query take longer than 30 seconds. I’m on a Windows-based host and the server logs are not available.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    Is this still happening if you connect Jetpack to WordPress.com right now?

    Yes, it’s still happening.

    bambino

    (@babybitch1976)

    I found it to be a conflict with the EM Beer Manager plugin. I deactivated it and was able to connect Jetpack, setup the features I needed, and then activate the plugin again.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic πŸš€

    @babybitch1976 I’m glad to hear you could work around the problem.

    I’ve tried to install the EM Beer Manager plugin on my own site, and then reconnected Jetpack to WordPress.com. Unfortunately I wasn’t able to reproduce the issue.

    If this happens again on your site in the future, could you follow the instructions I posted above to find out more about the error?

    Thanks!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Jetpack 4.4.1 500 Error’ is closed to new replies.