transport error – HTTP status code was not 200 (502)

  • Resolved Nick

    (@pilotnick)


    8 years, 4 months ago

    Every time that I try to approve my jetpack connection with wordpress.com I am given an error message. I have tried to contact my hosting company with regard to the issue, and they cannot figure it out either.

    The error that I am getting is as follows:

    transport error – HTTP status code was not 200 (502)

    Can you please help me fix this error so that I can connect to WordPress.com? Thank You

    • This topic was modified 8 years, 4 months ago by Nick.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Do you happen to use a caching plugin or service like CloudFlare that could filter the requests and communication between your site and third-party services like WordPress.com?

    If so, what happens when you deactivate those services?

    Let me know how it goes.

    Thread Starter Nick

    (@pilotnick)

    We’re not. We are using Varnish. I disabled Varnish, and we still get the same error.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    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 connect again, and then 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.

    Let me know what you find!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘transport error – HTTP status code was not 200 (502)’ is closed to new replies.