Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
A mail address can never be secured by SSL/TLS. Instead, the connection between client and server can be secured. If you have a valid certificate for your Plesk host name installed and if the client connects to POP, IMAP and SMTP using SSL/TLS and the host name (not the individual domain name of the subscription), then the connection is automatically properly secured. If the client is not connecting by using the host name of the host where the SSL certificate is installed, the connection is insecure. If the client is using the host name where the SSL certificate is installed, but is using SSL/TLS, the connection is insecure. For SSL to work you do not need to set an SSL checkbox in Plesk's mailbox configuration. If the host supports SSL, clients can use SSL when connecting to the mailbox. They must meet the conditions named in this post to properly establish a secure connection, though.
Plesk comes with a self-signed certificate, but you should use a commercial certificate to secure the host name, because you need a trust center signature to avoid browser warnings. I think there was a post on here, too, how to generate a host name certificate using Let's Encrypt, but not sure.