• On installing jetpack and trying to connect to WordPress.com to setup a site inaccessible 403 error results : Your website needs to be publicly accessible to use Jetpack: site_inaccessible

    Error Details: The Jetpack server was unable to communicate with your site.

    The site is public and accessible. The permissions have been checked and are all correct. We do have a WordPress.com account already which is working.

    The hosting provider is names.co.uk (namesco) . We understand they block xmlrpc.php as described here: https://www.thebambers.me.uk/wordpress/?p=308

    We have followed these instructions which have not resulted in jetpack working, but has allowed postit and the WordPress iPhone app to work.

    Namesco suggested posting here to ask if there are any other referenced to xmlrpc.php which would need renaming, and which files to look in.

    Any help would be very much appreciated!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi there,

    The WordPress.com server-side application that Jetpack talks to requires /xmlrpc.php be available, as of now. The fix described at the URL you mention will not fix Jetpack currently.

    Tim

    WordPress for iOS work with above fix. Why not Jetpack. did the developers thought about manual override?

    Same problem here – I can confirm that although the bug affecting xmlrpc is now six years old, Namesco absolutely will not allow even a single user to have this block lifted.

    WordPress for Android and iOS are able to reference xmlrpc without it having to specifically address the xmlrpc.php file, can the Jetpack server not do the same?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[plugin jetpack]’ is closed to new replies.