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.
Isn't psa-mail-pc-driver part of Plesk?
To be more precise, the database that stores the mail handler configuration was changed in such a way that my mail handler is no longer executed.
The Update #14 of Panel 11.0.9 modified my /etc/postfix/main.cf. Specifically, the configuration option smtpd_tls_cert_file was set back to the default.
This is extremely annoying, because it means
1. I can no longer run updates automatically, because of the possibility to screw up my...
Update #14 of Panel 11.0.9 removed my custom mail handler
The Update #14 of Panel 11.0.9 removed my custom mail handler.
This is extremely annoying, because it means
1. I can no longer run updates automatically, because of the possibility to screw up my system.
2. I have to set up a...
Workaround:
1. Delete the CNAME entry for www.example.net from DNS.
2. Create a new subdomain www of example.net. This will automatically create an A entry in the DNS.
3. Assign a certificate to the www.example.net subdomain the same way you did for example.net.
I wonder why Plesk is...
I have rewritten my custom mail handler to work with my current version of Plesk Panel, so I am no longer in need for a solution provided by Plesk Panel.
I would like to apply Greylisting only to those E-Mails, that SpamAssassin considers spam. Is there some way to configure this in Plesk? I have implemented a custom mail handler to do this, but it stopped working after an upgrade to Plesk 11 (see Environment Variable TCPREMOTEIP not set).
Apache sends wrong certificate
I have two domains in two webspaces: example.org and example.net.
When I visit https://example.org, Apache uses the certificate that I have configured for the example.org webspace.
When I visit https://example.net, Apache uses the certificate that I have...