Hi foreverlearning,
It sounds like you are blocking access to login via xmlrpc.php. We don’t do that by default so you want to go over your Wordfence settings and see where you might be blocking them.
If you enable Worfence again and look at the Live Traffic list and your list of Blocked IPs you should be able to see the requests from JetPack that are being blocked. When you see them there will be a reason listed why they are being blocked and this will help you figure out how to make sure they are not.
Thanks for the reply. I saw the incoming traffic, unblocked it and then tried to connect again. This time I saw the traffic and and now it said: “blocked for UA/Referrer/IP Range not allowed at ….So I’m assuming that though the ip itself it extends in range beyond what WordFence allows. The only option that I can see is under options for whitelisting ip addresses. Is this my only option?
I think it’s the WordFence firewall. I’ll give details after more testing where I verify such.
Did you ever figure this out? Manage is not working for me, either. For me, though, even when I disable all other plugins it still doesn’t work. It’s a new site, so I’m not sure what the problem is. Are some Wordfence protections saved even when it is deactivated?
EDIT: Actually, Manage is working because it allows me to turn the plugins on and off, but all the auto-update switches are disabled.
I have not been able to overcome this as of yet. I just haven’t had the time to drill down on it. It would be great if the Jet Pack and the WordFence people could join brains and come up with a solution. I will post if I do get it figured out. The problem with the recommendation made by WordFence is that the IP coming back from Jet Pack is not always the same, nor is the is the query string. It seems to be dynamic when you initiate an update. What I have done is this as a work around.
1. Disable WordFence.
2. Connect to WordPress.Com
3. Set all plug-ins for auto update
The background process from what I can tell seems to work ok. If you want to review updates in advance of making the change (as I like to do) this is a sub-optimal approach, but the best I can come up with at this time.
Again, in case WordFence is listening, it would be great if they would reach out to JetPack/WordPress.Com to get this handled as there’s a lot of people who I would presume use both applications and would benefit greatly from having this handled for them.
Dan
To be fair, I am using Wordfence and Jetpack on other sites and auto-update works on them. I’m not sure what’s wrong on my end, yet. If you ever do figure it out please post here just in case your solution my work for me.
Do you have the WordFence firewall enabled on the other sites?
Hi foreverlearning,
the message “blocked for UA/Referrer/IP Range” indicates that you have blocked the range that this IP belongs to in the section “Advanced blocking” in Wordfence. So please remove any blocks you have under “Advanced blocking”.
