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
(@qriouslad)
Yes, direct access of production site’s URL works in the browser, without authentication.
Staging:
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’ );
define( ‘CONTENT_STAGING_TRANSFER_TIMEOUT’, 60 );
Production:
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
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.
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
(@qriouslad)
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!
Great to hear, thank you for reporting back!
