• 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

Resolved Plesk - installed version / update missmtach

Pakon

New Pleskian
Hey,

I've got a problem with my plesk. After upgrading my distro and (fix some very old issues), I ran into big trouble.
1) The plesk repair tool shows the following message:

ERROR: Selector '18.0.20' does not match any product ID, release ID, release tier, or release version. Use either 'list' or 'list-all' command to list known entities.

The web-panel is working and shows version:
Version 18.0.33

I've more trouble but my guess is the mismatch of the version ins the installer and the web-panel.

Any suggestions?

Thanks in advance,
Pakon
 
I suppose that you have OVH mirror as a SOURCE. Please check it with

# grep SOURCE /root/.autoinstallerrc

If you see something like:

SOURCE="http://parallels.mirrors.ovh.net/parallels/"

rename the /root/.autoinstallerrc file by executing the command below:

# mv /root/.autoinstallerrc /root/.autoinstallerrc.bak

Then try to perform the Plesk repair tool one more time.
 
Hey,

I already found this way an tried it. The content is as following


cat /root/.autoinstallerrc
SSL_CIPHERS=ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256
SSL_PROTOCOLS=TLSv1.2
SSL_CIPHER_SERVER_PREFERENCE=yes


lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal

I might clean up my souces.list.d, but i don't know whether this one is needed:

ls /etc/apt/sources.list.d/ | grep plesk | grep list$
plesk-migrator.list with content:

cat /etc/apt/sources.list.d/plesk-migrator.list
#deb [arch=amd64] Index of /ubuntu/PMM_0.1.10 focal all
Should id enable it?

-----

Maybe to my main problem:

Every Site throws a 502 error, the problem is between the nginx and apache2. The SSL handshake between both are failing.

2021/02/16 13:08:22 [error] 1274860#0: *162 SSL_do_handshake() failed (SSL: error:1408F10B:SSL routines:ssl3_get_record:wrong version number) while SSL handshaking to upstream, client: <CLIENT IP>, server: <mydomain>, request: "GET /cloud/status.php HTTP/1.1", upstream: "https://<SERVER IP EXTERNAL>:7081/cloud/status.php", host: "hatkeininter.net"


-----

Plesk Repair Status:


Reconfiguring the Plesk installation
Reconfiguring the Plesk installation ............................ [FAILED]
- Started bootstrapper repair procedure (fast mode). This may
take a while.
- Certain actions may be skipped if not applicable.
-
- Finishing up upgrade procedures and rerunning previously
failed upgrade actions...
-
- **** Product repair started.
- Started bootstrapper repair procedure (fast mode). This may
take a while.
- Certain actions may be skipped if not applicable.
-
- Trying to start service mysql... active
- done
- Trying to establish test connection... connected
- done
- Trying to find psa database... version is 018000000
- Trying to backup MySQL database... done
- MySQL databases are dumped to
/var/lib/psa/dumps/mysql.preupgrade.18.0.33-18.0.33.20210216-130031.dump.gz
- Finishing up upgrade procedures and rerunning previously
failed upgrade actions...
- Trying to add supplementary group 'lock-manager' for user
'psaadm'... already there
- ===> Cumulative APS controller database (apsc) upgrade and
repair has been started.
- Upgrade or repair for 'apsc' (stage 'prep') is not required
- Trying to backup MySQL database... done
- MySQL databases are dumped to
/var/lib/psa/dumps/mysql.preupgrade.apsc.18.0.33-18.0.33.20210216-130036.dump.gz
- ===> Cumulative upgrade and repair of APS controller database
has been completed.
- Connection to APSC DB is possible
- ===> Cumulative APS controller upgrade and repair (final stage)
has been started.
- Upgrade or repair for 'apsc' (stage 'post') is not required
- ===> Cumulative upgrade and repair of APS controller (final
stage) has been completed.
- Dropping phpMyAdmin '' DB and '' DB user
-
- Warning: phpMyAdmin was configured without configuration
storage in database
-

- ===> Cumulative Plesk database upgrade and repair (revertable
stage) has been started.
- ===> Preparing Plesk database upgrade (revertable stage).
- ===> Cumulative upgrade and repair of Plesk database
(revertable stage) has been completed.
- ===> Plesk database scheme upgrade has been started.
- Applying migrations from:
/opt/psa/bootstrapper/pp18.0.33-bootstrapper/migrations/
- ===> Plesk database scheme upgrade has been completed.
- ===> Cumulative Plesk upgrade and repair (final stage) has been
started.
- ===> Preparing Plesk upgrade (final stage).


- Downloading file pmm.inf3: 100% was finished.
- Checking for installed packages...
- ERROR: Selector '18.0.20' does not match any product ID,
release ID, release tier, or release version. Use either 'list'
or 'list-all' command to list known entities.
-
- ERROR:Unable to retrieve repository configuration from
autoinstaller: unknown error
-
- Bootstrapper repair finished.
- Errors occurred while performing the following actions: fix
Plesk packages permissions.
- Check '/var/log/plesk/install/plesk_18.0.33_repair.log' and
'/var/log/plesk/install/plesk_18.0.33_repair_problems.log' for
details.
- If you can't resolve the issue on your own, please address
Plesk support.

- ***** problem report *****
- Warning: phpMyAdmin was configured without configuration
storage in database
Try to fix the phpMyAdmin error also failed.
 
I just realized, when I remove and install apache2, I get the following error. It's may also related to my problem:
ERR [panel] No info about current plesk installation at upgrade history
 
Hey, I resolved my main issue.

The link from sites-enabled to the plesk directory was missing.

- fixed and closed -
 
Back
Top