• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

rsa

  1. M

    Issue Failed to connect to the source server 'source'by SSH: not a valid OPENSSH private key file

    I am getting the given error while transferring the plesk data via plesk migrator extension. Failed to connect to the source server 'source' by SSH: not a valid OPENSSH private key file I use the same documentation here to generate and copy the RSA key, How to set up SSH keys for Plesk server...
  2. learning_curve

    Input Plesk / Let's Encrypt > Support for ECDSA Certificates

    The current Let's Encrypt Extension in Plesk, works well. Easy to use and for many, attractive because there's no CLI input required in order to generate certificates / automatic renewals etc. However, currently, if using this Plesk Extension, it's only possible to generate RSA certificates...
Back
Top