Title: Transport error
Last modified: August 24, 2016

---

# Transport error

 *  Resolved [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/transport-error/)
 * Hello,
 * This time, I created a new setup. A ‘production’ site, and a ‘staging’ site cloned
   from ‘production’. Exact same site, save for URL.
 * Installed Content Staging and configured wp-config on both sites. However, when
   trying to pre-flight, I got the following error message:
 * transport error – HTTP status code was not 200 (403) – on host: [http://[siteURLhere]](http://[siteURLhere])(
   error code -32301)
 * I double checked secret key (a SALT key) and it was a match. Changed to a simpler
   one, still not working.
 * There seems to be a similar error code with Jetpack plugin reported at:
    [https://wordpress.org/support/topic/what-is-error-code-32301](https://wordpress.org/support/topic/what-is-error-code-32301)
 * If it’s host specific, my new setup is hosted at Cloudways.com
 * Any clue?
 * Thanks!
    Bowo
 * [https://wordpress.org/plugins/content-staging/](https://wordpress.org/plugins/content-staging/)

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

 *  Plugin Author [stenberg.me](https://wordpress.org/support/users/stenbergme/)
 * (@stenbergme)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/transport-error/#post-5975917)
 * When Content Stage is trying to connect to Production it gets back a HTTP status
   header of 403 Forbidden.
 * Does it work to access the site URL you’ve specified in **CONTENT_STAGING_ENDPOINT**
   through your browser? Do you have to authenticate (e.g. with basic authentication)?
 * Thanks!
 *  Thread Starter [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/transport-error/#post-5975939)
 * Yes, direct access of production site’s URL works in the browser, without authentication.
 * Staging:
    [http://wordpress-1537-7254-31969.cloudwaysapps.com/](http://wordpress-1537-7254-31969.cloudwaysapps.com/)
 * wp-config has:
    $table_prefix = ‘s0m3prefix_’; define( ‘CONTENT_STAGING_SECRET_KEY’,‘
   s3cr3t_k3y’ ); define( ‘CONTENT_STAGING_ENDPOINT’, ‘[http://wordpress-1537-7254-31967.cloudwaysapps.com&#8217](http://wordpress-1537-7254-31967.cloudwaysapps.com&#8217););
   define( ‘CONTENT_STAGING_TRANSFER_TIMEOUT’, 60 );
 * Production:
    [http://wordpress-1537-7254-31967.cloudwaysapps.com/](http://wordpress-1537-7254-31967.cloudwaysapps.com/)
 * wp-config has:
    $table_prefix = ‘s0m3prefix_’; define( ‘CONTENT_STAGING_SECRET_KEY’,‘
   s3cr3t_k3y’ );
 * Not sure if its related or not, but adding a new batch listed a bunch of things
   that are not pages nor posts. Screenshot: [http://bit.ly/1GnSXby](http://bit.ly/1GnSXby)
 * Is that normal behaviour?
 * FYI, this is a skeleton base site with several plugins set up. Only has one page
   and zero post. My staging batch should be adding a new post.
 *  Plugin Author [stenberg.me](https://wordpress.org/support/users/stenbergme/)
 * (@stenbergme)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/transport-error/#post-5975975)
 * Might be that Cloudways block WordPress XML-RPC functionality, in that case your
   stage server won’t be able to communicate with your production server.
 * Check with Cloudways support if that is indeed the case. If it is, ask if they
   can enable XML-RPC support.
 * There are ways to disable part of the XML-RPC functionality provided by WordPress
   without removing support entirely.
 *  Thread Starter [Bowo](https://wordpress.org/support/users/qriouslad/)
 * (@qriouslad)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/transport-error/#post-5975991)
 * You are correct!!!
 * I’ve re-enabled XML-RPC and pre-flight + deploy is working!… note: I was using
   iThemes Security plugin, and “Completely disabled” it. I changed the settings
   to “Only disable trackbacks and pingbacks”.
 * Thanks!
 *  Plugin Author [stenberg.me](https://wordpress.org/support/users/stenbergme/)
 * (@stenbergme)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/transport-error/#post-5975993)
 * Great to hear, thank you for reporting back!

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

The topic ‘Transport error’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/content-staging.svg)
 * [Content Staging](https://wordpress.org/plugins/content-staging/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/content-staging/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/content-staging/)
 * [Active Topics](https://wordpress.org/support/plugin/content-staging/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/content-staging/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/content-staging/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [stenberg.me](https://wordpress.org/support/users/stenbergme/)
 * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/transport-error/#post-5975993)
 * Status: resolved