• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Can´t access PSA / admin login / IP range

T

testguys

Guest
Hi everybody,

I have originally restricted access towards the login page /PSA to an IP range of 84.xxx.0.0/16. But surprisingly and without any notification the telco provider has changed the routing and now i have with my internet connection an IP from the range 217.224.0.0/11.

Of course, i can´t log in at https://my-servers-ip:8443/login.php3 as admin any longer, even though the password is correct :((.

I assume that the IP range is stored in the DB, how to "reset" it or delete it?
I am using Plesk 8.0.1 - anyone knows what to do?

Thank you
 
SOLUTION

For other users with that IP range change problem for login into the control / admin panel - that worked for me:

SWsoft Knowledgebase

LOGIN INTO MYSQL:

sh:/ # mysql -uadmin -p psa
Enter password:

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3100 to server version: 4.1.10a

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

SEE WHAT IP´s ARE ACTIVE:

mysql> select * from cp_access;
+----+-------+------------+-------------+
| id | type | netaddr | netmask |
+----+-------+------------+-------------+
| 1 | allow | 84.128.0.0 | 255.192.0.0 |
| 2 | deny | 84.128.0.0 | 255.192.0.0 |
+----+-------+------------+-------------+
2 rows in set (0.00 sec)

WHICH POLICY:

mysql> select * from misc where param='access_policy';
+---------------+------+
| param | val |
+---------------+------+
| access_policy | deny |
+---------------+------+
1 row in set (0.00 sec)

DID NOT WORK FOR ME:

mysql> delete * from cp_access;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '* fro m cp_access' at line 1

WORKED:

mysql> update misc set val="allow" where param='access_policy';
Query OK, 1 row affected (0.03 sec)
Rows matched: 1 Changed: 1 Warnings: 0

Problem solved :D *Very Happy* - Weekend is sunny again - ;)
 
Back
Top