Jetpack Error

wordpress

#1

Is anyone getting the following error when trying to set-up Jetpack?

Your website needs to be publicly accessible to use Jetpack: site_inaccessible Error Details: The Jetpack server was unable to communicate with your site [HTTP 503]. Ask your web host if they allow connections from WordPress.com. If you need further assistance, contact Jetpack Support: http://jetpack.me/support/

I was chatting with LeoB and he told me the following:

LeoB: at 21:46:06
unfortunately i am finding out that it is a current issue we are having with that install, and our team is currently working on fixing it

LeoB: at 21:46:08
so sorry

LeoB: at 21:47:08
our push out

LeoB: at 21:47:23
which means an update to our systme caused it

LeoB: at 21:47:37
*system

LeoB: at 21:48:23
the pushout/ update was lastnight


#2

I’m getting the same error. Is there an eta on a fix?

I want to use this for the follow widget. Is there another one that works? I can’t get the one just called “follow” to work because it wants you to create a page called “subscribe” but DreamHost changes the name to “subscribe-2” even though there is no “subscribe” page. So I can’t get that plugin to work either.


#3

They haven’t told me anything about a fix. They did give me approximately $10 compensation, however.


#4

turns out this issue is related to the one i was facing: https://discussion.dreamhost.com/thread-140412.html

jetpack’s inability to connect was making commenting fail. i deactivated jetpack but now cannot re-activate. same issue as you.


#5

Here’s hoping they fix it soon.


#6

FYI, we’re working on it. Seems to be a mod_security issue.


#7

I’m now getting a NEW error:

Your Jetpack has a glitch. Something went wrong that’s never supposed to happen. Guess you’re just lucky: xml_rpc-32700
Try connecting again. Error Details: The Jetpack server could not communicate with your site’s XML-RPC URL. Please check to make sure http://www.briannechantal.com/xmlrpc.php is working properly. It should show ‘XML‑RPC server accepts POST requests only.’ on a line by itself when viewed in a browser and should not have any blank links or extra output anywhere.


#8

Put in a ticket and ask support to restart apache.

We FINALLY managed to get this one licked around 5pm yesterday. Sooo tired :frowning: In my dreams, my dreamself went to sleep because I was tired.


#9

Forgot to post this before,

this now works thanks!