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.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
Support stated they are working on this actively. They recommended to follow the following article to be notified when they introduce this migration option. Does Plesk support dist-upgrade?
I just upgraded to Obsidian and must say it seemed flawless. I would like to upgrade my server from Ubuntu 16.0.4 LTS to Ubuntu 18.0.4 and would like to know if there are any known issues with Plesk when performing an OS upgrade on the same server?
I'd plan on issuing the following commands...
My issue is resolved! I now see wildcard option. A while ago, I appended cli.ini found in /usr/local/psa/var/modules/letsencrypt/cli.ini
I had a single entry of:
rsa-key-size = 4096
This was to increase the key size of LE certificates to improve my SSLLabs score.
I deleted the cli.ini file...
cat /usr/local/psa/admin/conf/panel.ini
; Plesk initialization file
;
; Notes:
; * Be careful and understand what do you do while modifying of panel behavior.
; * If option is missed default value will be used.
; * Use ";" for comments.
; * Enabled debug mode or high log level can be the reason...
This new wildcard feature is not working for me. :(
I have the latest version of Plesk and the latest Let's Encrypt Extension:
Plesk Onyx Version 17.8.11 Update #14, last updated on July 9, 2018 12:29 PM
Let's Encrypt Version: 2.6.1-398
Ubuntu 16.04.4 LTS
I did not have an existing panel.ini...
OS Ubuntu 16.04.4 LTS
Product Plesk Onyx
Version 17.5.3 Update #45, last updated on April 12, 2018 06:25 A
When I click on "Updates and Upgrades" from the Plesk tools page, it comes up with a browser error:
Using a common SSL validation test:
The server does not have SSL/TLS encryption on...
I was very pleased a while back with the ability to secure webmail and now understand that this new version allows for so much more including mail, cname, subdomains etc... However, I don't know how to use this new feature to add the additional cname/A/subdomains such as ftp, mail, ns...
I had a similar desire to update DH parms on my Plesk Onyx system. I'm always a little hesitant with performing direct mods to source files rather than using a Plesk commands where available.
The command below will alter your dhparm from whatever it is set 2048 or other to 4096. The -G...
I'm currently using Ubuntu 16.04.3 and nginx 1.11.10. Looking at my installation script, I added the nginx repo before installing Plesk. The latest nginx repo version for Ubuntu mainline nginx is 1.13.5-2. I see after an apt update that "http://autoinstall.plesk.com/ubuntu/NGINX17 xenial...
I have successfully implemented DNSSEC on my server. However, I don't see where I can set the "Digest Type" encryption? Here are my initial default settings from the plugin itself.
Allowed algorithms for key generation:
ECDSAP384sha384
Key Signing Key
ECDSAP384sha384
Default size 4096...
I realized my error before your response and altered my question... I posted that I found my issue with the nginx version but am still interested in understanding where one would customize the protocols and ciphers for nginx manually?
I missed my own version before posting the request. I am using nginx 1.11 and not 1.13
http://nginx.org/en/CHANGES
Changes with nginx 1.13.0 25 Apr 2017
*) Feature: the "TLSv1.3" parameter of the "ssl_protocols" directive.
Still interested in...
It doesn't appear as though Plesk formally supports TLSv1.3. Either that or the sslmng command needs to be updated. How would you enable TLSv1.3 for nginx?
user@pleskserver:~# plesk sbin sslmng --custom --protocols="TLSv1.2 TLSv1.3"
WARNING:Ignoring unsuppored protocol TLSv1.3...
You should be able to simplify your OCSP by only including the following...
ssl_stapling on;
ssl_stapling_verify on;
resolver 8.8.4.4 8.8.8.8 valid=300s;
resolver_timeout 10s;