Title: Error 32700
Last modified: August 21, 2016

---

# Error 32700

 *  Resolved [DavidSoegiarto](https://wordpress.org/support/users/davidsoegiarto/)
 * (@davidsoegiarto)
 * [12 years, 10 months ago](https://wordpress.org/support/topic/error-32700/)
 * Had no problem with it couple months back on WP3.4.2 and Jetpack2.2.
 * Used Publicize option (and a couple other minor stuff) and added LinkedIn connection,
   works great.
 * This morning I tried adding a Facebook/Twitter connections and greeted with that
   error.
 * Tried everything I can think of (yes, XMLRPC page looks fine, no space, right
   line), and couldn’t figure it out.
 * Tried running the compatibility plugin and everything looks normal to me. I can
   email this to yo separately.
 * Tried reinstalling Jetpack to the latest version, requires WP3.6.
    So I updated
   WP to 3.6 and tried to connect Jetpack to WordPress.com when I’m greeted with
   the same 32700 message.
 * Help?
 * Pecelayam.com
    Hosted at godaddy.com – IIS7 – PHP5.2 (<- i dont think any of 
   these changed the last few months)
 * [http://wordpress.org/plugins/jetpack/](http://wordpress.org/plugins/jetpack/)

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

 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [12 years, 10 months ago](https://wordpress.org/support/topic/error-32700/#post-4005015)
 * I can’t seem to be able to access your site at the moment but in the past few
   weeks, we’ve received reports of similar issues from other folks hosted with 
   GoDaddy on a Windows server. We’re not able to connect to such sites from WordPress.
   com servers anymore.
 * GoDaddy recommends that you switch to a Linux server instead:
    [http://wordpress.org/support/topic/error-site_inaccessible-cant-connect-with-wordpresscom?replies=3#post-4499873](http://wordpress.org/support/topic/error-site_inaccessible-cant-connect-with-wordpresscom?replies=3#post-4499873)
 * Do not hesitate to contact them about this issue, they’re aware of the problem
   and have helped other users switch in the past few weeks.
 *  Thread Starter [DavidSoegiarto](https://wordpress.org/support/users/davidsoegiarto/)
 * (@davidsoegiarto)
 * [12 years, 10 months ago](https://wordpress.org/support/topic/error-32700/#post-4005045)
 * That’s too bad.
 * My hosting plan is the free one that comes with the domain. I can’t switch it
   to Linux unless I pony up some fee.
 * Well, I’ll revisit the plugin later then.
 * PS: My site seems to have no problem. Anything wrong accessing it? You can enter
   from either pecelayam.com or davidsoegiarto.com
 *  Plugin Author [Jeremy Herve](https://wordpress.org/support/users/jeherve/)
 * (@jeherve)
 * Jetpack Mechanic 🚀
 * [12 years, 10 months ago](https://wordpress.org/support/topic/error-32700/#post-4005114)
 * > My site seems to have no problem. Anything wrong accessing it? You can enter
   > from either pecelayam.com or davidsoegiarto.com
 * I can access it now. it seems it was temporary down when I tried to access it
   yesterday.
 *  Thread Starter [DavidSoegiarto](https://wordpress.org/support/users/davidsoegiarto/)
 * (@davidsoegiarto)
 * [12 years, 10 months ago](https://wordpress.org/support/topic/error-32700/#post-4005117)
 * I figured it out.
 * Reinstall WordPress. Cleaned (more like rebuild lol) out the DNS table. Reforward
   the domain. Reset file permissions on wordpress file.
 * Somewhere along the line, the site pops up and Jetpack reconnects.
 * Yes, all this while still on Windows server.
 * And yes, the site was down but not to my knowledge, which adds to the confusion.
   Apparently after I updated 3.6 manually (GoDaddy doesn’t support auto-update)
   it broke the DNS record, so while my office (where I did all the work) cached
   the @ record, if I access it from outside (home, cellphone), it came back not
   available.
 * I think part of it was due to the fact I have 2 domain going to the same hosting
   plan. One is forwarding with mask, and one is native, and I added the masked 
   domain as Hosted Domain in the host, etc……
 * Anyway, it’s a network config issue. Finally sorted out.
 * Thanks, Jeremy! (and Richard who emailed me)

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

The topic ‘Error 32700’ 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/)

 * 4 replies
 * 2 participants
 * Last reply from: [DavidSoegiarto](https://wordpress.org/support/users/davidsoegiarto/)
 * Last activity: [12 years, 10 months ago](https://wordpress.org/support/topic/error-32700/#post-4005117)
 * Status: resolved