Enabling TLS 1.2 and disabling other versions on Plesk.
In order to use the steps outlined below, you will need to upgrade Plesk to it’s most recent version. You can do so within the System Overview section of the Home screen in Plesk Panel or by running
Once you have completed the upgrade you can run the command in the link below to enable TLS1.2 and disable older versions of TLS.
Plesk uses system users to handle logins. As such removing the user effectively removes their access to the entire server.
If you want to delete the user without deleting any of their files, type this command as root:
If you want to delete the user’s home directory along with the user account itself, type this command as root:
# userdel -r username
Check for user
# grep username /etc/passwd
Just to be sure check the logins for Plesk on the server and the list of users is below.
# plesk db “select login from domains inner join sys_users on domains.id = sys_users.id”
| login |
| artist |
| test |
Courier cannot start:
Courier service can not be started: courierlogger dead but pid file exists
#service courier-pop3s status
In the Plesk Control Panel/Tools and Settings/ Services all of the ‘Courier’ entries show they are not running.
The usual fix of grep the courierlogger process and killing it does not work. Here is what does:
This is caused by hung processes, but not courierlogger was hung, but couriertcpd processes, one of them was running since April 3:
# ps aux | grep couriertcpd
root 3784 0.0 0.0 11976 1796 ? S 11:05 0:04 /usr/lib64/couriertcpd -address=0 -maxprocs=40 -maxperip=4 -nodnslookup -noidentlookup 110 /usr/sbin/pop3login /usr/lib64/plesk-9.0/pop3login Maildir
root 3907 0.0 0.0 11972 1884 ? S 11:05 0:00 /usr/lib64/couriertcpd -address=0 -maxprocs=40 -maxperip=4 -nodnslookup -noidentlookup 143 /usr/sbin/imaplogin /usr/bin/imapd Maildir
root 3973 0.0 0.0 11972 1776 ? S 11:05 0:00 /usr/lib64/couriertcpd -address=0 -maxprocs=40 -maxperip=4 -nodnslookup -noidentlookup 993 /usr/bin/couriertls -server -tcpd /usr/sbin/imaplogin /usr/bin/imapd Maildir
root 26808 0.0 0.0 103396 2080 pts/2 S+ 19:53 0:00 grep couriertcpd
root 26951 0.0 0.0 11976 1704 ? S Apr03 0:49 /usr/lib64/couriertcpd -address=0 -maxprocs=80 -maxperip=10 -nodnslookup -noidentlookup 995 /usr/bin/couriertls -server -tcpd /usr/sbin/pop3login /usr/lib64/plesk-9.0/pop3login Maildir
[root@216-55-187-88 ~]# ps aux | grep courierlogger
root 13394 0.0 0.0 4124 1432 ? S 18:08 0:00 /usr/sbin/courierlogger -name=courier-authdaemon -pid=/var/run/courier-authdaemon.pid -lockfile=/var/lock/subsys/courier-authdaemon -start /usr/lib64/courier-authlib/authdaemond
Kill all those processes and after that you are able to start the service successfully:
# service courier-imapd status
courierlogger (pid 29099) is running...
Here are some Plesk commands that are useful:
How to re-patch
# plesk installer update --repatch
This is related to an issue for Courier
In checking Plesk Stats, the traffic is much lower that the actual traffic.
Plesk Web Stats button only links to now SSL traffic. See: https://support.plesk.com/hc/en-us/articles/213951505-Different-statistics-values-for-SSL-and-non-SSL-traffic
As a workaround, SSL traffic statistics can be accessed using the following link:
FTP statistics can be accessed using the following link:
Login to your Plesk server.
Select the domain you wish to enable gzip for from the left hand side.
Click in Apache and nginx settings:
Down the bottom, add the following to the “Additional nginx directives” field:
gzip_disable "MSIE [1-6]\.(?!.*SV1)";
Click OK to save.
Verify with GTMetrix.com
Another way is to set up deflate.
First you need to check the module mod_deflate is enabled on the server.
Or, in ssh:
# httpd -M |grep deflate
Then you need to create the file /etc/httpd/conf.d/deflate.conf
# vim /etc/httpd/conf.d/deflate.conf
and add the following into it.
Chech here – https://checkgzipcompression.com
The Plesk self-repair functionality enables you to automatically diagnose and resolve issues with Plesk and Plesk services. If you encounter an issue with one of the Plesk services (for example, if mail is not being sent or delivered, or a website fails to open, and so on), or with Plesk itself (for example, if error messages are being displayed in the Plesk interface, or if Plesk pages fail to load), you can use the Plesk repair utility to attempt to resolve it. The utility can be used to check and repair individual aspects of Plesk (such as the mail service, or the Plesk database), or all the aspects at once.
More at https://docs.plesk.com/en-US/12.5/administrator-guide/plesk-administration/plesk-repair-utility.74649/