• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Plesk upgrade to Obsidian extensions fails because invalid SSL certificate on ext.plesk.com

M

micheloe

New Pleskian
When upgrading Plesk Onyx 17.8 to Obsidian 18.0.23 in CentOS 7, the upgrade fails partially when updating extensions. The issue seems global though, not related to plesk/OS version. Afterwards, I'm unable to access the extensions catalog. The installation log shows:

ERROR: Upgrade step 2019-08-26-12-07-56_InstallExtensionRepairKit.php failed with code 1 and output:
[2020-02-04 07:05:07.113] ERR [panel] Error in cURL request: Peer's Certificate issuer is not recognized.
[2020-02-04 07:05:07.127] ERR [panel] Error in cURL request: Peer's Certificate issuer is not recognized.
[2020-02-04 07:05:07.141] ERR [panel] Error in cURL request: Peer's Certificate issuer is not recognized.:
0: /usr/local/psa/admin/plib/Upgrade/upgrade.php:44
ERROR: Plesk\Upgrade\Exception: Error in cURL request: Peer's Certificate issuer is not recognized. (upgrade.php:44)
Click to expand...
...

ERROR: Upgrade step 2019-08-26-13-15-41_InstallExtensionAdvancedMonitoring.php failed with code 1 and output:
[2020-02-04 07:05:08.100] ERR [panel] Error in cURL request: Peer's Certificate issuer is not recognized.
[2020-02-04 07:05:08.115] ERR [panel] Error in cURL request: Peer's Certificate issuer is not recognized.
[2020-02-04 07:05:08.129] ERR [panel] Error in cURL request: Peer's Certificate issuer is not recognized.:
0: /usr/local/psa/admin/plib/Upgrade/upgrade.php:44
ERROR: Plesk\Upgrade\Exception: Error in cURL request: Peer's Certificate issuer is not recognized. (upgrade.php:44)

SUCCESS: Upgrade step 2019-10-09-11-05-57_SendProductAgreement.php was successfully done.
SUCCESS: Upgrade step 2019-11-11-13-20-40_AddWebPMimeType.php was successfully done.
SUCCESS: Upgrade step 2019-11-14-07-15-09_SetDefaultPasswordStrength.php was successfully done.
SUCCESS: Upgrade step 2019-11-19-09-48-55_ResetThemeToOnyx.php was successfully done.
SUCCESS: Upgrade step 2019-12-01-22-23-14_MoveUserSettings.php was successfully done.
SUCCESS: Upgrade step 2019-12-17-06-50-14_SetGlobalDefaultDoc.php was successfully done.
SUCCESS: Upgrade step 2019-12-20-10-01-36_CreateTempUploadDir.php was successfully done.
Some steps of upgrade failed. Run upgrade with option --repair to rerun failed steps.
Click to expand...

Rerunning the failed steps with "plesk repair installation" also fails with the same error.

When trying to access ext.plesk.com, an invalid SSL certificate warning is also shown in the browser.

Debugging this issue on several machines with curl shows the same issue:

curl -v https://ext.plesk.com
* About to connect() to ext.plesk.com port 443 (#0)
* Trying 195.181.172.7...
* Connected to ext.plesk.com (195.181.172.7) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* Server certificate:
* subject: CN=rsc.cdn77.org,O=DataCamp Limited,L=London,C=GB
* start date: Oct 24 00:00:00 2019 GMT
* expire date: Jun 09 12:00:00 2020 GMT
* common name: rsc.cdn77.org
* issuer: CN=DigiCert SHA2 Secure Server CA,O=DigiCert Inc,C=US
* NSS error -12276 (SSL_ERROR_BAD_CERT_DOMAIN)
* Unable to communicate securely with peer: requested domain name does not match the server's certificate.
* Closing connection 0
curl: (51) Unable to communicate securely with peer: requested domain name does not match the server's certificate.
Click to expand...

Please fix the SSL certificate on your CDN. Thanks.
 
You must log in or register to reply here.

Similar threads

D
Issue Errors during downloading metadata for repository 'rpm-deathwatch-rhel-8'
Replies
1
Views
1K
AYamshanov
AYamshanov
flederwiesel
Question `SSLVerifyClient require` -> AH10158: cannot perform post-handshake authentication
Replies
0
Views
666
flederwiesel
flederwiesel
M
Issue curl: (60) SSL: no alternative certificate subject name matches target host name
Replies
2
Views
3K
AYamshanov
AYamshanov
M
Issue Backup to FTPS server fails after upgrade to Plesk 18.0.64
Replies
1
Views
818
mjehlenz
M
carini
Issue Using Scaleway S3 for Plesk backups
Replies
1
Views
623
Maarten
M
Back
Top