Anonymous
My feedback
1 result found
-
1 vote
To let the Plesk login react only on a single IP address or a defined address range is a valid request. We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
An error occurred while saving the comment
This suggestion stems from a requirement we reported that support were unable to fulfill.
We don't want to blacklist by source. We want to restrict control panel service to a single public IP address.
We have a multi-IP server and we want the management interface on only one of those IPs. Without manually reconfiguring the Nginx proxy config file to comment out all but the home IP the default vhost on port 443 of ALL public-facing IPs proxies through Nginx to the panel service, irrespective of any other settings.
Imagine we have the range 1.2.3.160 - 1.2.3.169
We only want Plesk control panel to appear on 1.2.3.160:443, and for the default server on the remaining IPs to be unserved. Without the manual intervention described above, they also present the control panel login.