Unable to login to Plesk: ERR_TOO_MANY_REDIRECTS

Follow

Comments

7 comments

  • Avatar
    Abraham Joseph

    plesk db "remove from IP_addresses where ip_address="192.0.2.2" <== This is not working in my Plesk Onyx!!

  • Avatar
    Bulat Tsydenov

    @Abraham Are you sure you have absolutely the same symptoms of the issue as described in this article?

    > plesk db "remove from IP_addresses where ip_address="192.0.2.2" <== This is not working in my Plesk Onyx!!

    Did you replace the ip address in the command with your ip address?

  • Avatar
    Abraham Joseph

    Yes, Bulat. I have replaced the IP address. Below are the details from my panel.log

    [2017-10-12 01:19:36] ERR [panel] The IP address 172.17.0.1 is already used for hosting.:
    0: /usr/local/psa/admin/plib/Commands/RereadIpAddresses.php:181
    Commands_RereadIpAddresses->_deleteBlackListedIps()
    1: /usr/local/psa/admin/plib/Commands/RereadIpAddresses.php:40
    Commands_RereadIpAddresses->run(boolean false)
    2: /usr/local/psa/admin/plib/Db/Table/Broker/IpAddresses.php:134
    Db_Table_Broker_IpAddresses->reread()
    3: /usr/local/psa/admin/htdocs/server/configure.php:32

  • Avatar
    Abraham Joseph

    Yes. It worked. I have removed the entry using the below Command.

    delete from IP_addresses where ip_address="172.17.0.1"

  • Avatar
    Abraham Joseph

    May I know why this happened since I didn't do nothing with my Plesk?

  • Avatar
    Abraham Joseph

    After deleting the row using "delete from IP_addresses where ip_address="172.17.0.1",  I was able to log into the Plesk. But got error again at the next stage of configuration.

    I have now changed the table "IP_addresses" as like posted below, and everything is working fine now.

    1st stage
    ===============
    MariaDB [psa]> select * from IP_Addresses;
    +----+----------------+---------------+---------+--------------------+-------------------+-------+--------+---------------+-------------------+-------+
    | id | ip_address | mask | iface | ssl_certificate_id | default_domain_id | ftps | status | serviceNodeId | public_ip_address | main |
    +----+----------------+---------------+---------+--------------------+-------------------+-------+--------+---------------+-------------------+-------+
    | 1 | 172.17.0.1 | 255.255.0.0 | docker0 | 3 | 1 | false | 2 | 1 | NULL | false |
    | 2 | 192.168.124.80 | 255.255.0.0 | enp0s5 | 3 | 0 | false | 0 | 1 | NULL | true |
    | 3 | <my-public-IP> | 255.255.255.0 | enp0s6 | 3 | 0 | false | 0 | 1 | NULL | true |
    +----+----------------+---------------+---------+--------------------+-------------------+-------+--------+---------------+-------------------+-------+

    Changed To,
    ===============
    MariaDB [psa]> select * from IP_Addresses;
    +----+----------------+---------------+---------+--------------------+-------------------+-------+--------+---------------+-------------------+-------+
    | id | ip_address | mask | iface | ssl_certificate_id | default_domain_id | ftps | status | serviceNodeId | public_ip_address | main |
    +----+----------------+---------------+---------+--------------------+-------------------+-------+--------+---------------+-------------------+-------+
    | 1 | <my-public-IP> | 255.255.255.0 | enp0s6 | 3 | 0 | false | 0 | 1 | NULL | true |
    | 2 | 192.168.124.80 | 255.255.0.0 | enp0s5 | 3 | 0 | false | 0 | 1 | NULL | true |
    | 3 | 172.17.0.1 | 255.255.0.0 | docker0 | 3 | 1 | false | 0 | 1 | NULL | false |
    +----+----------------+---------------+---------+--------------------+-------------------+-------+--------+---------------+-------------------+-------+

  • Avatar
    Yulia Plokhotnikova (Edited )

    @Abraham Joseph

    Seems you did not execute this command from the article:

    # plesk bin ipmanage --reread

    This would add required records in IP_Addresses so that you do not modify the table manually.

    Even though you did not make any changes, the fact remains that the domain was assigned to incorrect IP address. This is a result of IP addresses misconfiguration that may appear due to some changes being made in the interface, while database server is in reloading state, or any similar reason.

     

     

Please sign in to leave a comment.