• 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.

Resolved Roundcube - Could not connect to ssl

Bogdan1

Regular Pleskian
Hi,

I have a problem with roundcube.
I've set Lest Encrypt Certificate as "Certificate for securing mail" in "SSL/TLS Certificates".
And now I'm getting this error in roundcube.

OS: Centos7

[09-Mar-2018 14:39:58 UTC] PHP Warning: stream_socket_client(): Failed to enable crypto in /usr/share/psa-roundcube/program/lib/Roundcube/rcube_imap_generic.php on line 959

[09-Mar-2018 14:39:58 UTC] PHP Warning: stream_socket_client(): unable to connect to ssl://localhost:993 (Unknown error) in /usr/share/psa-roundcube/program/lib/Roundcube/rcube_imap_generic.php on line 959

[09-Mar-2018 14:39:58 +0000]: <nqu4gdmp> IMAP Error: Login failed for [email protected] from **.***.**.**(X-Real-IP: **.***.**.**). Could not connect to ssl://localhost:993: Unknown reason in /usr/share/psa-roundcube/program/lib/Roundcube/rcube_imap.php on line 196 (POST /?_task=login&_action=login)
 
Last edited:
Yes, thats it. Hope it will be fixed ASAP. Thanks
To be honest I was surprised to see 17.8.11 RTM while this bug was still standing... It doesn't seems to me to be an "esoteric" configuration that can impact just an handful of installations...
 
Back
Top