Issue Unable to upload SSL cert: To read key from file or string use methods...

[ahoi]

Server operating system version

11.6

Plesk version and microupdate number

18.0.50

On a Plesk setup on Debian 11.6, I am getting this error while uploading a new cert (pem).

On multiple servers, this error occurs:

> To read key from file or string use methods PleskExt\SsIlt\OpenSs|\PrivateKey.:fromFile()and
PleskExt\Ss|it\OpenSs|\PrivateKey::fromString)

 

[ahoi]

Could be related to Issue - ERR [extension/sslit] Could not get config vars: To read x509 certificate from file or string use methods PleskExt\SslIt\OpenSsl\X509Certificate::from - but EXTLETSENC-1182 is already solved?

 

[scsa20]

You might want to reach out to Plesk support directly as they'll more likely want to jump into the server with you to see what is happening since there's not much to go off of on that error alone:

How to get support directly from Plesk?

Question How to get support directly from Plesk? Answer Lease-type Plesk licenses purchased directly from Plesk running on supported Plesk version include full free support. Perpetual-type license...

support.plesk.com

 

[selwonk11]

@ahoi

Did you find a solution to this problem? I have just started experiencing exactly the same error following an update:

Could not issue an SSL/TLS certificate for *******.***
Details
To read key from file or string use methods PleskExt\SslIt\OpenSsl\PrivateKey::fromFile() and PleskExt\SslIt\OpenSsl\PrivateKey::fromString()

This is what is running:



This is a dev box and it is locked down behind a firewall. To manage SSL for the handful of domains on this server, I create certificates with the Certify the Web desktop client for Windows, export the file to a .pem and upload it.

Until very recently this has been absolutely fine. Since it started to happen, I've tried to uninstall and reinstall SSL It! but this does not seem to do anything. I've rebooted, patched, updated extensions etc. but the problem persists.

The problem happens for new certificates or renewals, and also happens on brand new domains.

The lack of search results suggests, worryingly, that this is a fairly uncommon problem. Any assistance would be gratefully received.

Thanks in advance!