I’m not sure I understand. Could you tell me more about what you’re trying to implement on your WordPress site, or if you experience any issues with Jetpack?
Thanks!
One feature requires that the site be publically accessible, but nothing about making the site publically accessible. Does this require the sacrifice of one black chicken and three white chickens, or three white chickens and one black chicken—order is important to some minor deities after all.
Oh, I understand now.
The order doesn’t really matter, neither does the color of the chicken. 🙂
More seriously, a site is considered publicly accessible when no one requires a username and a password to access the site, and when access to the site isn’t restricted for specific visitors (like robots, or visitors from specific countries.)
I hope that makes sense. If you think your site is publicly accessible, but Jetpack tells you otherwise, don’t hesitate to post your site URL here; I’ll take a closer look.
If you want it to remain private, you can also contact us via this contact form:
http://jetpack.com/contact-support/
Thanks!
I need a username and password to access the admin side of my sites, does that count?
It could be it, depending on how you’ve implemented it. You’d want to make sure that this additional authentication layer doesn’t restrict access to the XML-RPC file, which Jetpack and other plugins and apps use to communicate with your site. You can get to that file by adding xmlrpc.php to your WordPress URL.
If you need to enter a username/password to access the file, then your site won’t be able to communicate with 3rd party services.
