Support

 Hi! I im browsing through our DirectAdmin user weblogs to see if there are issues we have not noticed yet. All seem to be fine, but on a number of sites (Joomla with AdminTools) we get these kind of errors:

[Sat Apr 30 12:43:19.086401 2016] [authz_core:error] [pid 768984:tid 140195298924288] [client 208.115.113.83:35804] AH01630: client denied by server configuration: /home/blauwv01/domains/blauwvingerenergie.nl/public_html/robots.txt
[Sat Apr 30 12:43:19.086552 2016] [authz_core:error] [pid 768984:tid 140195298924288] [client 208.115.113.83:35804] AH01630: client denied by server configuration: /home/blauwv01/domains/blauwvingerenergie.nl/public_html/403.shtml

The all involve the robots.txt and 403.shtml files.

The robots.txt file on this particular site is accessible through the browser.

I was just wondering if you could help me figure out if this is something to worry about. Can serach engines readthe robots.txt ok?

On the web I read some remarks about changing

Order allow, deny
Allow from all

to:

Require all granted

But I don't think this code is used in the htaccess. (We are on apache 2.4) The webroot htaccess is created by AdminTools.

Any thoughts on where these error log entries come from and if I should worry about it?

Kind regards,
Jip Jonker

Hi! I have disable the 'Block access from specific user agents' option on on of our sites. We will wait and see if the error log is still producing these error.

But when this 'solves' the error messages, should we keep it disabled? I guess this feature is added for a specific reason. To make the sites safer. right? We could also just ignore the errors in the logs if we know for sure they are only caused by specific user agents. At least we now know why the errors are there. Would you advise to keep the feature turned on?

Kind regards,
Jip Jonker

It seems there are no more errors with 'authz_core'. So I guess these were indeed related to the user-agents being blocked. We now will have to decide whether we want to make life easier for the 'kiddies' and prevent the errors, or the other way around ;-)

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.