I see this message on the wordpress updates page
"Your server has returned a status code of403 while attempting to communicate with the Simple:Press server to establish up to date version information.
WordPress will retry this operation automatically but if the condition persists we firstly recommend seeking assistance from your hosting support team and then contacting Simple:Press support if they are unable to help."
Do you know what can be causing this?
Hi:
As far as I can tell our site is up and running so not sure why you're seeing a 403 error. What is the IP of your WordPress server? I can check our firewall logs to see if its been blacklisted for some reason - that's the only thing I can think of that might be an issue.
Thanks.
It's 104.18.57.131 for http://www.subnoise.es
I recently started using the Wordfence plugin since I had some hack attempts, could this plugin be causing this?
I don't see that IP in our blocked lists.
Not sure why WordFence would be an issue but anything is possible. Does the message go away if you disable it?
It didn't work.
Let's check the opposite, I'll ask my hosting if they can reach you.
Is it 104.27.154.59 ?
Hi:
Use the simple-press.com url to resolve the ip address. The server is behind a cloudflare proxy so the IP address could change depending on where you are and how Cloudflare is routing traffic through its proxy servers.
Thanks.
I forgot I'm behind cloudfare too. My real IP is 198.38.77.79 according to my hosting
They pinged simple-press.com and it responded well. Also they told me that whitelisting my IP on your cloudfare control panel should fix the issue
Unfortunately white listing an IP that isn't under our control isn't something we can do since it bypasses a lot of the security checks that CloudFlare provides. But I do see that 198.38.77.79 is being subjected to a security challenge when trying to access one of our xml files related to updates. CloudFlare doesn't tell us WHY its flagging your IP though - maybe that IP got on a blacklist somewhere or there's something else going on with the server that makes it look suspicious to CF? Over the last 24 hours its the only IP trying to access that particular file/path that is being subjected to a security challenge. Maybe the hosting provider can figure out if its blacklisted somewhere and/or switch the IP out for you? Since you're behind a cloudflare proxy, an ip change wouldn't take that much time to propagate - just maybe a minute or two of dns downtime at most (in our experience with Cloudflare).
I just tried adding a targeted firewall rule to that file to allow your IP. Lets see if that works. My concern is that it might block requests for other update files too even if this one is allowed.
Now I don't see the error and everything is up to date, thanks!
