Xmlrpc: Difference between revisions

From Acenet Knowledgebase
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:
----
----


 
<br><br>
1) in your home directory, open or create a ".htaccess" text file.
1) in your home directory, open or create a ".htaccess" text file.
 
<br><br>
2) In the .htaccess file, add the following text:
2) In the .htaccess file, add the following text.  Replace the XXX.XXX.XXX.XXX with the static IP of the connecting server.
 
<br>
<pre>
<pre>
<Files xmlrpc.php>
<Files xmlrpc.php>
Line 15: Line 15:
</Files>
</Files>
</pre>
</pre>
<br>
3) Save the file.
<br><br>


Replace the XXX.XXX.XXX.XXX with the static IP of the connecting server.
3) Save the file.


You should now be able to connect via XMLRPC from that specified IP.
You should now be able to connect via XMLRPC from that specified IP.

Revision as of 14:40, 30 October 2018

Due to the large amounts of XMLRPC attacks we see against our shared and reseller servers, Acenet has decided to block access to all xmlrpc.php files globally on the server. If you have an application that needs to use xmlrpc, you will need to manually enable access for specific IPs to the file with the following.




1) in your home directory, open or create a ".htaccess" text file.

2) In the .htaccess file, add the following text. Replace the XXX.XXX.XXX.XXX with the static IP of the connecting server.

<Files xmlrpc.php>
order deny,allow
deny from all
allow from XXX.XXX.XXX.XXX
</Files>


3) Save the file.


You should now be able to connect via XMLRPC from that specified IP.