Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion -
Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here
Resolved Plesk is so slow
- Thread starter TurabG
- Start date
no. I would prefer to see some informative and valuable parts of the log
SirAdams
New Pleskian
The topic is old but I spent a lot of time to solve the problem that appeared in me.
Check the /etc/resolv.conf file.
If localhost (127.0.0.1) is not in the first place then change that.
If you are already using dynamic addition to resolv.conf, the default option on server providers, then make sure that the first place is 127.0.0.1. You can achieve this by editing the files in /etc/resolvconf/resolv.conf.d/ in the head file add entries:
nameserver ::1
nameserver 127.0.0.1
I have spent a lot of time to come to the conclusion that if you have a foreign server entered and it is slow or with restrictions, the whole plesk panel works slowly and even can fail to work.
Check the /etc/resolv.conf file.
If localhost (127.0.0.1) is not in the first place then change that.
If you are already using dynamic addition to resolv.conf, the default option on server providers, then make sure that the first place is 127.0.0.1. You can achieve this by editing the files in /etc/resolvconf/resolv.conf.d/ in the head file add entries:
nameserver ::1
nameserver 127.0.0.1
I have spent a lot of time to come to the conclusion that if you have a foreign server entered and it is slow or with restrictions, the whole plesk panel works slowly and even can fail to work.
