Self installed blog on Amazon EC2 and Jetpack

• 

  dannybaggs · Member · Dec 10, 2011 at 1:48 pm

  • Copy link
  • Add topic to favorites

  I’ve installed WordPress on a LAMP server I run within Amazon’s EC2. To complete the setup of Jetpack, I’m instructed to Connect to WordPress.com. Upon doing so, I get the following error info:

  “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 404]. If you are hosted with Go Daddy, they are aware of this issue, and we at WordPress.com are working with them to fix it. If your site is hosted elsewhere, please contact Jetpack Support: http://jetpack.me/support/”

  Therefore, I have full control over the hosting environment but need to understand what this connection is trying to do, to be able to diagnose where the problem is and fix.

  Given this, I’d appreciate any pointers or more technical details you can provide on this one so I can get to the next step.

  Regards,

  Dan
  Blog url: http://dannybaggs.wordpress.com/

• 

  dannybaggs · Member · Dec 10, 2011 at 1:49 pm

  • Copy link

  P.S. My blog URL posted above is not the blog instance that I’m questioning about.

• 

  staff-blorbo · Staff · Dec 10, 2011 at 8:23 pm

  • Copy link

  Can you tell us the URL of the blog you’re having trouble with?

• 

  dannybaggs · Member · Dec 10, 2011 at 11:50 pm

  • Copy link

  Hi Macmanx,

  It’s http://www.camerjam.com/blog

  Thanks,

  Dan

• 

  staff-blorbo · Staff · Dec 11, 2011 at 7:58 am

  • Copy link

  Well, it’s definitely accessible at least.

  I’d like to rule-out a plugin conflict. Would you please try connecting again with all other plugins disabled?

• 

  dannybaggs · Member · Dec 12, 2011 at 9:55 am

  • Copy link

  Hi Macmanx, I tried as you suggested and disabled the other plugins and tried to connect. Same result as before.

  Regards,

  Dan

• 

  staff-blorbo · Staff · Dec 12, 2011 at 7:36 pm

  • Copy link

  Alright, theme functions can sometimes conflict like plugins.

  Would you please try connecting one more time with the Twenty Eleven theme enabled?

• 

  dannybaggs · Member · Dec 13, 2011 at 6:15 am

  • Copy link

  Hi Macmanx,

  Did as requested but the same result.

  Are you able to shed light on what this connection process is trying to achieve? I can then perhaps better diagnose.

  Regards,

  Dan

• 

  staff-blorbo · Staff · Dec 13, 2011 at 9:08 am

  • Copy link

  It’s a simple OAUTH a connection, which bounces from you to us, then back to you to confirm. Are you running any sort of firewalls or security scripts that you could temporarily disable while connecting?

• 

  dannybaggs · Member · Dec 13, 2011 at 9:59 am

  • Copy link

  Hi Macmanx,

  I believe there is a default firewall that I’ve set up with my AWS instance that allows comms only over port 80.

  OAuth wouldn’t be over anything else would it?

  I’ll see if I can test that out but I’m of course not too comfortable in diabling this.

• 

  evarlese · Member · Dec 13, 2011 at 5:32 pm

  • Copy link

  If you could disable your firewall while connecting to Jetpack (and then reenable it when you’re done with testing), that would help us get a better idea of what’s causing this error message for you.

  Are you connecting via HTTPS?