• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

PLESK SSL Wrapper Failing to start at all

T

Traged1

Guest
After the PLESK 7.6.1 upgrade the PLESK SSL Wrapper service is failing to start. We ahve many customers using secure email and this failure to start is preventing them from sending out thier email. Which of cource they have complained to us.

I have tried to restart the service using PLESK's service montior and manually using the Administration services console. Same result:

"Error 1053: The service failed to respond ina timely manner."

Anyone got any suggestions.
 
PLESK support suggested that I try using the ADD/Remove programs to repair the PLESK installation, but that did not help at all.

Upon comparison of the stunnel files from the affected server to another server which stunnel is working on I have noticed that the file: C:\Program Files\SWsoft\Plesk\admin\bin\stunnel.conf has not been updated on the affected server.

In particular the section:

# Certificate
cert = @CertificateFileName@

Should now be:

# Certificate
cert = C:\Program Files\SWsoft\Plesk\admin\conf\httpsd.pem

Editing this file like above and restarting the PLESK SSL Wrapper service appears to have fixed the issue.
 
Back
Top