- Plesk Onyx
Note: This article has the reference to the issues with the fixes available:
- #PPPM-10429 "The "IP Access Restriction Management" feature stops working (as PPP-41886)"
- Plesk Obsidian Release Candidate 1.0 04 June 2019
- #PPP-41886 "Restricting access to Plesk to specific IP address in Tools & Settings > IP Access Restriction Management now works correctly even if the specified IP address had the white space character appended in front of it (for example, “ 192.0.2.1”)."
In Plesk > Tools & Settings > Restrict Administrative Access > Settings the option
Denied from the networks that are not listedis selected
Plesk can be accessed from IP which is not listed in Plesk > Tools & Settings > Restrict Administrative
A Line in
cp_accesstable in PSA database has "space" at the begining of the IP field:
MYSQL_LIN: MariaDB [psa]> select * from cp_access;
| 29 | deny | 203.0.113.22 | 255.255.255.255 |
| 30 | deny | 203.0.113.32 | 255.255.255.255 |
| 31 | deny | 203.0.113.42 | 255.255.255.255 |
| 32 | deny | 203.0.113.52 | 255.255.255.255 |
| 33 | deny | 203.0.113.254 | 255.255.255.255 |
A line in
cp_access table in PSA database has space at the beginning of the IP field which causes the Restrict Administrative Access to malfunction.
This is caused by a BUG with ID #PPPM-10429 which will be resolved in future Plesk updates.
As a workaround, the IP from the list can be corrected by:
Connect to the server via SSH
Execute the following command line:
# plesk db "update psa.cp_access set netaddr='203.0.113.254' where id=33"
Note: Consider subscribing to this article to be notified when the BUG is fixed.