• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question How to disable/restrict by IP <server-ip>/login_up.php ?

fabkim

New Pleskian
Hi,

I just noticed that when I access the IP address of my server with Chrome, I am redirected to the page <ip-address>/login_up.php or <server_name>/login_up
Is there a way to restrict this page by IP as is the case when using port 8443?
The "Restricting Administrative Access" feature only protects when the correct credentials are used. There is therefore a possibility of using this page to find the identifiers by brute force
Or is there a way to disable the non-8443-port access or redirecting to the 8443 port ?

Thanks
 
You cannot brute-force into Plesk when the Fail2Ban jail that protects the login is used. Simply activate that jail and you have peace.
 
yes, you are right, I forgot about fail2ban.
But leaving this page accessible lets a hacker know that Plesk is used on the server. The goal of security is to give as little information as possible, which is why I would like this page to no longer be publicly accessible at all.
So is there a way to block it ?
 
Or is there a way to disable the non-8443-port access or redirecting to the 8443 port ?
Hi!

Try to use the Plesk Firewall and/or to allow only a subnet for Your I-provider
If you are looking at
Code:
cat /var/log/plesk/panel.log | grep "Failed login attempt with login"
may you will see, that there is no entry (like here).

I have never had a Fail2ban notification about a failed attempt on the Plesk panel.
IMHO, SSH, installed websites (wordpress etc) and SMTP is much more the risk than Plesk per se.
 
Back
Top