Jetpack REST API returns (503) error

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

    (@jeherve)

    Jetpack Mechanic 🚀

    10 years, 4 months ago

    Could you add the following to your site’s wp-config.php file, and then call the API page again?

    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, check the wp-content/debug.log file for errors, and paste the results here. You can then replace define('WP_DEBUG', true); by define('WP_DEBUG', false); in the code above.

    Thanks!

    Thread Starter dylancompanjen

    (@dylancompanjen)

    10 years, 4 months ago

    I have just added that lines to my wp-config.php and called the API again. There is no debug.log file appearing in my wp-content folder though…

    Thanks for the reply!

    Thread Starter dylancompanjen

    (@dylancompanjen)

    10 years, 4 months ago

    As of this morning it starts to work 50/50 again. Sometimes the API shows me a successful response and sometimes I still get the (503) response.
    What could it be, is my web hosting too slow?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    10 years, 3 months ago

    If you don’t see any errors in debug.log, could you check your server error logs around the time when you experienced the issues? The 503 should be listed there, and could tell us more about the problem.

    If you don’t know how to access your server error logs, your hosting provider should be able to help.

    Let me know how it goes.

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

The topic ‘Jetpack REST API returns (503) error’ is closed to new replies.

Tags