Title: Full sync error Last modified: January 10, 2017 --- # Full sync error * Resolved [Rick](https://wordpress.org/support/users/figurehead/) * (@figurehead) * [9 years, 4 months ago](https://wordpress.org/support/topic/full-sync-error/) * Hi, I’m trying to run a full sync on a couple of blogs but I get this error: * > The Jetpack site is inaccessible or returned an error: transport error – HTTP > status code was not 200 (403) [-32300] * When I open my wordpress settings page there is also another red message on top- right of the screen: * There was an error retrieving your site settings. Make sure your Jetpack is up to date * I’ve done some research and I think the reason is that the two blogs are on https. * These are the URLs: blog.expedia.fr blog.expedia.nl * Is there a workaround to enable the sync? * thanks Rick Viewing 10 replies - 1 through 10 (of 10 total) * Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/) * (@jeherve) * Jetpack Mechanic 🚀 * [9 years, 4 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8642314) * Jetpack uses your site’s XML-RPC file to communicate with WordPress.com. Unfortunately I cannot access that file on your site at the moment: [https://blog.expedia.fr/xmlrpc.php](https://blog.expedia.fr/xmlrpc.php) * If you use a security plugin to block access to the file, you’ll need to configure it to allow incoming and outgoing connections to /xmlrpc.php. * If you do not use such plugin, you’ll want to contact your hosting provider and ask them if they currently block access to your site’s XML-RPC file. * I hope this helps. * Thread Starter [Rick](https://wordpress.org/support/users/figurehead/) * (@figurehead) * [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8714887) * Hi Jeremy, * thanks for your reply. I’m sorry for my delayed reply but I didn’t receive a notification. * I’ve now unblocked the access to /xmlrpc.php. Could you please verify and let me know if you’re still blocked? * thanks * Thread Starter [Rick](https://wordpress.org/support/users/figurehead/) * (@figurehead) * [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8714888) * Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/) * (@jeherve) * Jetpack Mechanic 🚀 * [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8720317) * I’m afraid the problem is still the same: Access to XML-RPC is still blocked. * Thread Starter [Rick](https://wordpress.org/support/users/figurehead/) * (@figurehead) * [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8728564) * Do you think this is a file permission issue then? It’s currently set to 674. Alternatively I can send you the file here? * Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/) * (@jeherve) * Jetpack Mechanic 🚀 * [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8729343) * The file is shipped with WordPress, so its contents should be fairly standard: [https://core.trac.wordpress.org/browser/tags/4.7.2/src/xmlrpc.php](https://core.trac.wordpress.org/browser/tags/4.7.2/src/xmlrpc.php) * You also shouldn’t have to change the file’s permissions. * Access to the file is most likely blocked elsewhere, either via a Security plugin, via a rule in your site’s `.htaccess` file, or directly by your hosting provider. If you’ve already eliminated all other plugins and the problem remains, check the `.htaccess` file. If nothing blocks XML-RPC in that file, you’ll need to ask your hosting provider for help. * Thread Starter [Rick](https://wordpress.org/support/users/figurehead/) * (@figurehead) * [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8730644) * Hi, I’ve contacted my hosting provider. I’ll get back to you as soon as I have an answer. * thanks * Thread Starter [Rick](https://wordpress.org/support/users/figurehead/) * (@figurehead) * [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8733721) * The file is now accessible. Let me know if you can look into it. * thanks! * Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/) * (@jeherve) * Jetpack Mechanic 🚀 * [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8735677) * Your site appears to be properly connected to WordPress.com now. You should be all set! * If you still experience issues, could you give me more details about the problems you’re having? * Thanks! * Thread Starter [Rick](https://wordpress.org/support/users/figurehead/) * (@figurehead) * [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8743908) * It all worked fine. Now jetpack is synced, thanks! Viewing 10 replies - 1 through 10 (of 10 total) The topic ‘Full sync error’ is closed to new replies. * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237) * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/) * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq) * [Support Threads](https://wordpress.org/support/plugin/jetpack/) * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/) * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/) * 10 replies * 2 participants * Last reply from: [Rick](https://wordpress.org/support/users/figurehead/) * Last activity: [9 years, 3 months ago](https://wordpress.org/support/topic/full-sync-error/#post-8743908) * Status: resolved