Jetpack uses your site’s XML-RPC file to communicate with WordPress.com. Unfortunately I cannot access that file on your site at the moment:
http://mefemn.org/xmlrpc.php
While it appears in the browser, it’s followed by this message:
<!-- permalink_structure ends with slash (/) but REQUEST_URI does not end with slash (/) -->
When trying to connect to the file from WordPress.com, I get a 406 error.
If you use a security plugin to block access to the file, or that may add anything to your site’s .htaccess file, you’ll need to configure it to allow incoming and outgoing connections to /xmlrpc.php, without outputting any text or error message in the file.
If you do not use such plugin, you’ll want to contact your hosting provider and ask them if they currently block access to your site’s XML-RPC file.
I hope this helps.
I am on this very same boat and also it can’t fetch users
http://www.solarpaque.com.ar
Thanks!
I wanted to access your site to check the status of your Jetpack connection, but my antivirus doesn’t seem to allow me to visit your site:
http://i.wpne.ws/kCXB
I would recommend that you run through the tests on this page to make sure your site hasn’t been hacked:
https://codex.wordpress.org/FAQ_My_site_was_hacked
Hi –
My website is now unresponsive and I do not know how to fix this. I was updating it yesterday, I installed some plug ins to help with images (which seemed fine) it was looking great then BAM! gone! I cannot access it from any device, I cannot access the admin dashboard, I cannot view plugins to delete any and it tells me that there are problems fetching my plugins. I get a 500 internal server message anytime I try to access my site or admin dashboard. I know my site wasn’t deleted but I’m blocked from even viewing the pages when I log in! This is terrible. Please help!
I get a 500 internal server message anytime I try to access my site or admin dashboard.
@offerstage Your problem is most likely not related to Jetpack. I would recommend following the instructions here to gain access to your site again:
https://codex.wordpress.org/Common_WordPress_Errors#The_White_Screen_of_Death
