Difference between revisions of "Xmlrpc"
Docs admin (Talk | contribs) |
Docs admin (Talk | contribs) |
||
| Line 14: | Line 14: | ||
</Files> | </Files> | ||
</pre> | </pre> | ||
| − | |||
3) Save the file. | 3) Save the file. | ||
<br><br> | <br><br> | ||
You should now be able to connect via XMLRPC from that specified IP. If you run into any problems, or need additional assistance, please open a new technical support ticket at our online [https://billing.ace-host.net helpdesk]. | You should now be able to connect via XMLRPC from that specified IP. If you run into any problems, or need additional assistance, please open a new technical support ticket at our online [https://billing.ace-host.net helpdesk]. | ||
Revision as of 14:47, 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 our shared and reseller servers. If you have an application that needs to use xmlrpc, you can manually enable access for specific IPs to the file with the following.
NOTE: We do not recommend enabling xmlrpc access for all IP addresses, due to attacks. Specific static IPs are strongly recommended.
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. If you run into any problems, or need additional assistance, please open a new technical support ticket at our online helpdesk.
