Plesk comes with its own SSL and there is the familiar SSL warning for the browser.

PleskSSL

 

You will see a certificate warning. This is normal. Plesk comes with its own certificate, rather than a purchased certificate, so the connection is secure but you will still see the browser warning. You should continue to the site.

If you want to avoid the issue, here is what you can do.

  1. Set the hostname for the server in plesk > Tools and Utilities > Settings, then click Server Settings. Set the hostname to a vaild hostname a FQDN. ex, host.domain.com.
  2. Go to Tools and Utilities > SSL certificates.Generate a new CSR for the hostname (host.domain.com).
  3. Take the CSR and purchase an new SSL for the hostname.
  4. Install the new SSL.
  5. Make sure the DNS points the hostname to the server primary IP.
  6. Now navigate to the hostname vs IP for the plesk panel https://host.domain.com:8443

Now you should not see any warnings for the SSL certificate.

 

Migrating in plesk shows an error. Checking the IP address pool in plesk show this

2607:5200:1800:1000:226:18ff:fe24:4e35  (dedicated)

Trying to remove it produces an error:

Error:   Cannot remove the IP address 2607:5200:1800:1000:226:18ff:fe24:4e35  because it is the last IP address present on a network interface.   

Disable IPV6 – http://wiki.centos.org/FAQ/CentOS6#head-d47139912868bcb9d754441ecb6a8a10d41781df

Restart plesk and re-read the IP address pool in plesk > Tools and Settings > IP Addresses > Re-read IP’s

Need to allow access to a Devloper or Programmer?

You can create another user in Plesk if you log in with Administrator first and go to Domains -> Manage Hosting (to the far right of the domain name) then click on the “Users” Tab. From there you can set user roles (aka what they have permissions to) and create a user account with that role.

Post fix restart produces the following

# tail -f /usr/local/psa/var/log/maillog
Mar  4 21:40:07 postfix/postfix-script[24660]: fatal: the Postfix mail system is not running
Mar  4 21:40:08 postfix/postfix-script[24731]: starting the Postfix mail system
Mar  4 21:40:08 postfix/master[24732]: fatal: bind 0.0.0.0 port 25: Address already in use

Look for multiple instances of smtp inet n – n – – smtpd and comment them out:


#smtp inet n - n - - smtpd
localhost:smtp inet n - n - - smtpd
smtp_bind_address6= -o smtp_address_preference=ipv4
#smtp inet n - n - - smtpd

Restart postfix

# service postfix restart

Error in plesk postfix email logs:

Notice: Error: EHLO not accepted from server! in /var/www/vhosts/domain.com/httpdocs/system/library/mail.php on line 237

Check postfix main and comment out non_smtpd_milters:


smtpd_milters = , inet:127.0.0.1:12768
#non_smtpd_milters = , inet:127.0.0.1:12768

Restart postfix:

# service postfix restart
Shutting down postfix:                                     [  OK  ]
Starting postfix:                                          [  OK  ]

BUSY: Update operation was locked by another update process.
Having trouble updating Plesk? Check for the installer:


ps aux | grep installer

root     31859  0.0  0.2 135560 20820 ?        S    21:10   0:00 /var/cache/parallels_installer/parallels_installer_CentOS_6_x86_64 --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch release,stable --web-interface --with-ssl --disable-browser

Kill the process

kill -9 31859

There’s a psa-installer.lock file in /tmp/ which indicates Plesk a running installer. Be sure no installer is running and then delete this little bugger.


# cd /tmp
# ls
autoinstaller3.log  autoinstaller_webui_socket  phpsqGbDE  phpxQn6nH  psa-installer.lock  spamd_full.sock

If you are getting such error while uploading a file in the website, then I suggest you to follow the below steps:

Take the backup of the configuration file of the NGINX


# cp /etc/nginx/nginx.conf /etc/nginx/nginx.conf.bkp

Add client_max_body_size 0; (or 100m) to /etc/nginx/nginx.conf and reload nginx proxy server using the below command:


# /etc/init.d/nginx reload

(Note: If ‘client_max_body_size’ entry is not there in the above file, then you can simply insert it under ‘http {‘ section )

If you are getting such error while uploading a file in Plesk Panel (not while uploading in website), I suggest you to follow the below steps:

Increase ‘client_max_body_size’ value accordingly in ‘/etc/sw-cp-server/config’ config file, for e.g. if the file’s size is 4.5GB, you can set the value to 5120m (5120MB).


# grep client_max_body_size /etc/sw-cp-server/config
client_max_body_size 5120m;