• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Weak Security settings

Binesh S

Regular Pleskian
I have found apache logs, an illegal default access


Sat Nov 10 22:59:09 2012] [error] [client 1.1.1.1] File does not exist: /var/www/vhosts/default/htdocs/autodiscover
[Sat Nov 10 22:59:09 2012] [error] [client 2.2.2.2] File does not exist: /var/www/vhosts/default/htdocs/autodiscover
[Sat Nov 10 23:02:06 2012] [error] [client 2.2.2.2] File does not exist: /var/www/vhosts/default/htdocs/autodiscover
[Sat Nov 10 23:04:13 2012] [error] [client 1.1.1.1] File does not exist: /var/www/vhosts/default/htdocs/autodiscover
[Sat Nov 10 23:04:13 2012] [error] [client 1.1.1.1] File does not exist: /var/www/vhosts/default/htdocs/autodiscover
[Sat Nov 10 23:07:10 2012] [error] [client 2.2.2.2] File does not exist: /var/www/vhosts/default/htdocs/autodiscover


Any patch update on this issue ?


FYI 1.1.1.1 & 2.2.2.2 sample IP address


Thanks
 
Last edited:
Yes I have already blocking IP from access. However the access should be block from coding level

Thanks
 
Yes I have already blocking IP from access. However the access should be block from coding level

Thanks

Do you mean that we should block all known IPs of possible hacker's attacks in Plesk code? Or what do you mean?
 
There is utility like fail2ban IP for some time like one hour may prvent excessive access right ? I am not asking to ban all IPs is not good to application like temporarry solution or provide alerts failed attempts
 
Back
Top