• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

SSL error in reread ip

Webroy

Regular Pleskian
HI All,

I have a problem with one of my servers:

When i do a reread ip adress i get this error:

Unable to load object of type SSLCertificate with id=4: SSLCertificate: unable to select: no such row in the table

Ant ideas where i how i can fix this?

There is a ipadress deleted on this server..
 
It is database inconsistency. Try to fix it with following scenario:

0. Backed up psa database:

# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` psa > psa.prl.dump.sql

1. Indicate domain with incorrect setting (component_id=4 -> incorrect):

mysql> select d.id, d.name, R.rep_id, R.component_id, c.id from domains d, Repository R left join certificates c on c.id=R.component_id where d.cert_rep_id=R.rep_id and c.id is NULL;
+----+-----------------+--------+--------------+------+
| id | name | rep_id | component_id | id |
+----+-----------------+--------+--------------+------+
| 7 | domain.org | 4 | 4 | NULL |
+----+-----------------+--------+--------------+------+
1 row in set (0.00 sec)

2. domain.org have 10.51.36.10 IP address configured (ssl_certificate_id=30 -> correct).

mysql> select * from IP_Addresses;
+----+---------------+-----------------+-------+--------------------+-------------------+-------+
| id | ip_address | mask | iface | ssl_certificate_id | default_domain_id | ftps |
+----+---------------+-----------------+-------+--------------------+-------------------+-------+
| 1 | 10.51.37.138 | 255.255.255.192 | eth0 | 30 | 0 | false |
| 2 | 10.51.40.184 | 255.255.255.0 | eth0 | 42 | 1 | false |
| 3 | 10.51.36.10 | 255.255.255.0 | eth0 | 30 | 7 | false |
| 4 | 10.74.237.191 | 255.255.255.0 | eth0 | 34 | 14 | false |
| 5 | 10.74.237.220 | 255.255.255.0 | eth0 | 14 | 10 | false |
| 7 | 10.51.40.148 | 255.255.255.0 | eth0 | 36 | 19 | false |
+----+---------------+-----------------+-------+--------------------+-------------------+-------+
6 rows in set (0.01 sec)

3. To fix the issue it was necessary to update Repository table:

mysql> select * from Repository where rep_id = 4 and component_id =4;
+--------+--------------+
| rep_id | component_id |
+--------+--------------+
| 4 | 4 |
+--------+--------------+
1 row in set (0.00 sec)

mysql> update Repository set component_id = 30 where rep_id = 4 and component_id =4;

Contact Support Team if you can't fix it by yourself.
 
that didnt work, i fixed it by doing a copy of the sslkey id=1 in the table and gave it id=4 , i cannot find which domain is still using ssl id=4... can it be that it is removed but still somewere in the database? bootstrapper.sh repair also did not work. So for now with a workaround solved...
 
Back
Top