Errors in apache error log

Hi @bulfa,

That error is indicating that the current configuration of your server/site is preventing our plugin from accessing one of it’s files. This could be caused by a setting in a security plugin you have installed or could be a setting applied by your host. The first thing I would do is if you have a security plugin enabled then try temporarily disabling it, clearing any site cache, and then check whether the issue still occurs. If it does, then the next step would probably be contacting the host to see whether they have any security settings applied on their end which would prevent access to the file.

Let me know whether that helps at all, or if you need any further assistance.

John

Hello John,
thanks for your prompt reply. I tried disabling all the plugins and the error is still there. It happens every time a user visit the page. It seems that when the page is loaded (client side) the plugin checks for updates and the error is written in the log. But the feed gets updated anyway.
I’m running the server (centos with parallel plesk, about 200 sites on it hosted on a structure we have in OVH), standard configuration I would say, no issues in more than one year.

If you need more info just let me know.
Thank you
Bulfa

Hey Bulfa,

So what’s happening is that when the feed loads then the plugin makes a request to one of the plugin’s files using Ajax which returns the data for the likes, shares, and comments for each post. This is done after the rest of the feed has already loaded, and so doesn’t affect the loading of the actual posts at all. The file that is queried is called “query.php” and this file is being blocked on your site so that the plugin can’t access it (screenshot). You can see in the screenshot (and at this link) that it’s returning a 403 forbidden error when trying to access it. This is usually due to a security setting on the server which is preventing access to that file. Perhaps a file permissions issue on the plugins directory, or something similar. Are there any security restrictions in place on the server that might cause this?

Many thanks,

John