Client denied by server configuration error

G3oangelo

Registered
Dec 12, 2018
1
0
1
Romania
cPanel Access Level
Root Administrator
Code:
[Wed Dec 12 10:38:36.920201 2018] [proxy_fcgi:error] [pid 4337] (104)Connection reset by peer: [client 204.187.14.72:46166] AH01075: Error dispatching request to :
[Wed Dec 12 10:38:38.052131 2018] [proxy_fcgi:error] [pid 4337] [client 204.187.14.72:46166] AH01067: Failed to read FastCGI header
[Wed Dec 12 10:38:38.052189 2018] [proxy_fcgi:error] [pid 4337] (104)Connection reset by peer: [client 204.187.14.72:46166] AH01075: Error dispatching request to :
[Wed Dec 12 10:47:11.629630 2018] [access_compat:error] [pid 6011] [client 123.57.254.142:41239] AH01797: client denied by server configuration: /home/domain/public_html/xmlrpc.php
[Wed Dec 12 10:47:11.904525 2018] [access_compat:error] [pid 6012] [client 123.57.254.142:41277] AH01797: client denied by server configuration: /home/domain/public_html/xmlrpc.php
And my site it gives me this error.
Code:
[Wed Dec 12 09:13:19.580364 2018] [access_compat:error] [pid 29449] [client 89.24x.xxx.xx:52904] AH01797: client denied by server configuration: /home/domain/public_html/xmlrpc.php
 
Last edited by a moderator:

GOT

Get Proactive!
PartnerNOC
Apr 8, 2003
1,772
326
363
Chesapeake, VA
cPanel Access Level
DataCenter Provider
Are you sure these are accesses you want to go through? Xmlrpc.php is a common attack vector in wordpress and I would initially say that you probably have some wordpress security in place that is blocking that access which is generally desirable.
 

cPanelLauren

Product Owner II
Staff member
Nov 14, 2017
13,266
1,300
363
Houston
I am inclined to agree with @GOT it looks like (most likely in .htaccess) you have something blocking access to xmlrpc.php which isn't necessarily a bad thing due to the tendency for it to be attacked in the forum of a Brute Force Amplification Attack. WordPress even has a blog post going over methods to stop attacks of this nature: Stop XML-RPC Attack
 

baronn

Active Member
Dec 27, 2017
33
7
8
manchester
cPanel Access Level
Root Administrator
@G3oangelo the advice is spot on. XML-RPC is most often the prefreed way to start attacks on your site. You need to ask yourself if this is a service that you actually will be using at all? Further to the wordpress resource link you can use this wordpress plugin: en-gb.wordpress.org/plugins/better-wp-security/ iThemes Security (formerly Better WP Security to configure the security on your wordpress install. It will allow you to configure not only your XML-RPC settings but also stop most other forms of security settings to stop common attacks. Works pretty well and has an easy to use GUI.
 
Last edited by a moderator:
  • Like
Reactions: cPanelLauren