You get this error:

Service Unavailable

HTTP Error 503. The service is unavailable.

The application pools were failing to start as they were not able to login using the proper account. Here is the error:

Application pool plesk(default)(2.0)(pool) has been disabled. Windows Process Activation Service (WAS) did not create a worker process to serve the application pool because the application pool identity is invalid.

Reset the password on the two accounts:

IWAM_plesk(default)
IWPD_11(unique)

Then reset the login creditendials for the two application pools. The application pools started and the sites are working again.

Enable the firewall within Plesk then add the needed rules to Windows Firewall (set the IP’s can connect on tcp/1433). Plesk does not have the ability to set the IP’s or IP range.

Resources
http://www.rackspace.com/knowledge_center/article/configuring-ms-sql-server-for-remote-access
http://www.rackspace.com/knowledge_center/article/creating-an-inbound-custom-allow-rule-for-windows-firewall-windows-2008

Normally, checking mail may produce an SSL error for plesk mail services. All clients Outlook, Mac mail, thunderbird, show a a message for ssl certificate. How to fix it.

You would need to purchase a SSL certificate for your servers hostname and set it up so it gets used for the mail service on the server. if you try and use mail.domain.com, it’ll still give an error.

Ref: http://kb.sp.parallels.com/en/1062

Services

Control Panel

  • Logs
    • Error log:
      /var/log/sw-cp-server/error_log

      and

      /var/log/sw-cp-server/sw-engine.log
    • Access log:
      /usr/local/psa/admin/logs/httpsd_access_log
    • Panel log:
      /usr/local/psa/admin/logs/panel.log
  • Services
    • Stop:
      /etc/init.d/psa stop
    • Start:
      /etc/init.d/psa start
    • Restart:
      /etc/init.d/psa restart
  • Configuration
    • PHP config:
      /usr/local/psa/admin/conf/php.ini
    • Panel config:
      /usr/local/psa/admin/conf/panel.ini
    • Web server config:
      /etc/sw-cp-server/conf.d/plesk.conf

Web Presence Builder

  • Logs
    • Error log:
      /usr/local/psa/admin/logs/sitebuilder.log
    • Install/upgrade logs:
      /usr/local/sb/tmp/
  • No service control (working via sw-cp-server service)
  • Configuration
    • /usr/local/sb/config
    • /etc/sw-cp-server/conf.d/plesk.conf
    • /usr/local/psa/admin/conf/php.ini

SSO

  • Logs
    • Error log:
      /var/log/sw-cp-server/error_log
    • SSO log:
      /var/log/sso/sso.log
  • Services
    • No service control (works via sw-cp-server service)
    • Manage settings:
      /usr/local/psa/bin/sso
  • Configuration
    • /etc/sso/sso_config.ini
    • /etc/sw-cp-server/conf.d/sso.inc

Backup Manager

  • Logs
    • Backup logs:
      /usr/local/psa/PMM/logs/backup-<datetime>
    • Restore log:
      /usr/local/psa/PMM/logs/restore-<datetime>
  • Functionality is controlled by the Plesk control panel service
  • Configuration
    • /etc/psa/psa.conf

Migration Manager

  • Logs
    • /usr/local/psa/PMM/logs/migration-<datetime>
  • Functionality is controlled by the Plesk control panel service.

Health Monitor manager

  • Logs
    • /usr/local/psa/admin/logs/health-alarm.log
  • Services
    • Stop:
      /etc/init.d/sw-collectd stop
    • Start:
      /etc/init.d/sw-collectd start
    • Restart:
      /etc/init.d/sw-collectd restart
  • Configuration
    • /usr/local/psa/admin/conf/health-config.xml
    • /usr/local/psa/var/custom-health-config.xml
    • /etc/sw-collectd/collectd.conf

Health Monitor Notification Daemon

  • Logs
    • /usr/local/psa/admin/logs/health-alarm.log
  • Services
    • Stop:
      /etc/init.d/psa-health-monitor-notificationd stop
    • Start:
      /etc/init.d/psa-health-monitor-notificationd start
    • Restart:
      /etc/init.d/psa-health-monitor-notificationd restart
  • Configuration
    • /usr/local/psa/admin/conf/health-config.xml
    • /usr/local/psa/var/custom-health-config.xml

MySQL

  • Logs
    • /var/log/mysqld.log
  • Services
    • Stop:
      /etc/init.d/mysqld stop
    • Start:
      /etc/init.d/mysqld start
    • Restart:
      /etc/init.d/mysqld restart
  • Configuration
    • /etc/my.cnf
    • /etc/mysql/my.cnf

      (Debian/Ubuntu)

PostgreSQL

  • Logs
    • /var/lib/pgsql/pgstartup.log
  • Services
    • Stop:
      /etc/init.d/postgresql stop
    • Start:
      /etc/init.d/postgresql start
    • Restart:
      /etc/init.d/postgresql restart
  • Configuration
    • /var/lib/pgsql/data/postgresql.conf

Apache

  • Logs
    • Global Access and Error logs:
      /var/log/httpd/
    • Domain logs:
      /var/www/vhosts/<domain>/logs
  • Services
    • Stop:
      /etc/init.d/httpd stop
    • Start:
      /etc/init.d/httpd start
    • Restart:
      /etc/init.d/httpd restart
  • Configuration
    • /etc/httpd/conf/httpd.conf
    • /etc/httpd/conf.d/zz010_psa_httpd.conf

      (includes generated configuration files with the rest of vhosts’ and server configuration)

  • NOTE: On SuSE, Debian, and Ubuntu, the service is called “apache2”. The path to its logs is
    /var/log/apache2

    and the path to configs is

    /etc/apache2

    .

NGINX

  • Logs
    • Error log:
      /var/log/nginx/error.log
    • Access log:
      /var/log/nginx/access.log
    • Domain logs:
      /var/www/vhosts/<domain>/logs/proxy_access*_log
  • Services
    • Stop:
      /etc/init.d/nginx stop
    • Start:
      /etc/init.d/nginx start
    • Restart:
      /etc/init.d/nginx restart
    • NOTE: To disable nginx, go to “Tools & Settings > Services Management” and stop nginx from there.
  • Configuration
    • /etc/nginx/nginx.conf
    • /etc/nginx/conf.d/zz010_psa_nginx.conf

      (includes generated configuration files with the rest of the vhosts’ and server configuration)

Tomcat

  • Logs
    • /var/log/tomcat5/*
  • Services
    • Stop:
      /etc/init.d/tomcat5 stop
    • Start:
      /etc/init.d/tomcat5 start
    • Restart:
      /etc/init.d/tomcat5 restart
  • Configuration
    • /etc/tomcat5/server.xml

FTP

  • Logs
    • /usr/local/psa/var/log/xferlog
    • /var/log/secure
  • No service control (works via xinetd service)
  • Configuration
    • /etc/xinetd.d/ftp_psa
    • /etc/proftpd.conf
    • /etc/proftpd.include

Xinetd

  • Logs
    • /var/log/messages
  • Services
    • Stop:
      /etc/init.d/xinetd stop
    • Start:
      /etc/init.d/xinetd start
    • Restart:
      /etc/init.d/xinetd restart
  • Configuration
    • /etc/xinetd.conf
    • /etc/xinetd.d/*

      (files with “.” in the name are ignored)

BIND

  • Logs
    • /var/log/messages
  • Services
    • Stop:
      /etc/init.d/named stop
    • Start:
      /etc/init.d/named start
    • Restart:
      /etc/init.d/named restart
  • Configuration
    • /etc/named.conf
  • NOTE: In Debian/Ubuntu, the service is called “bind9.”

Courier-IMAP

  • Logs
    • /usr/local/psa/var/log/maillog
  • Services
    • Stop:
      /etc/init.d/courier-imap stop
    • Start:
      /etc/init.d/courier-imap start
    • Restart:
      /etc/init.d/courier-imap restart
  • Configuration
    • /etc/courier-imap/imapd
    • /etc/courier-imap/imapd-ssl
    • /etc/courier-imap/pop3d
    • /etc/courier-imap/pop3d-ssl

Postfix

  • Logs
    • /usr/local/psa/var/log/maillog
  • Services
    • Stop:
      /etc/init.d/postfix stop
    • Start:
      /etc/init.d/postfix start
    • Restart:
      /etc/init.d/postfix restart
  • Configuration
    • /etc/postfix/master.cf
    • /etc/postfix/main.cf

Qmail

  • Logs
    • /usr/local/psa/var/log/maillog
  • Services
    • Stop:
      /etc/init.d/qmail stop
    • Start:
      /etc/init.d/qmail start
    • Restart:
      /etc/init.d/qmail restart
  • Configuration
    • Control files in
      /var/qmail/control/
    • /etc/xinetd.d/smtp_psa
    • /etc/xinetd.d/smtps_psa
    • /etc/xinetd.d/submission_psa

Horde

  • Logs
    • Error log:
      /var/log/psa-horde/psa-horde.log
  • No service control (works via Apache web-server)
  • Configuration
    • /etc/psa-webmail/horde/horde.conf
    • /etc/psa-webmail/horde/horde/conf.php

Roundcube

  • Logs
    • Error log:
      /var/log/plesk-roundcube/errors
  • No service control (works via Apache web-server)
  • Configuration
    • /etc/psa-webmail/roundcube/*

Mailman

  • Logs
    • /var/log/mailman/*
  • Services
    • Stop:
      /etc/init.d/mailman stop
    • Start:
      /etc/init.d/mailman start
    • Restart:
      /etc/init.d/mailman restart
  • Configuration
    • /etc/httpd/conf.d/mailman.conf
    • /usr/lib/mailman/Mailman/mm_cfg.py
    • /etc/mailman/sitelist.cfg

SpamAssassin

  • Logs
    • /usr/local/psa/var/log/maillog
  • Services
    • Stop:
      /etc/init.d/spamassassin stop
    • Start:
      /etc/init.d/spamassassin start
    • Restart:
      /etc/init.d/spamassassin restart
  • Configuration
    • /etc/spamassassin/local.cf
    • /var/qmail/mailnames/<domain>/<mailbox>/.spamassassin/user_prefs

Parallels Premium Antivirus

  • Logs:
    • /usr/local/psa/var/log/maillog
    • /var/drweb/log/*
  • Service control:
    • Stop:
      /etc/init.d/drwebd stop
    • Start:
      /etc/init.d/drwebd start
    • Restart:
      /etc/init.d/drwebd restart
  • Configuration:
    • /etc/drweb/*

Kaspersky Antivirus

  • Logs:
    • /usr/local/psa/var/log/maillog
  • Service control:
    • Stop:
      /etc/init.d/kavehost stop
    • Start:
      /etc/init.d/kavehost start
    • Restart:
      /etc/init.d/kavehost restart
  • Configuration:
    • /opt/kav/sdk8l3/etc/kav-handler.cfg
    • /etc/kavehost.xml

phpMyAdmin

  • Logs:
    • Error log:
      /var/log/sw-cp-server/error_log
  • No service control (working via sw-cp-server service).
  • Configuration:
    • /usr/local/psa/admin/htdocs/domains/databases/phpMyAdmin/libraries/config.default.php

phpPgAdmin

  • Logs
    • Error log:
      /var/log/sw-cp-server/error_log
  • No service control (working via sw-cp-server service).
  • Configuration:
    • /usr/local/psa/admin/htdocs/domains/databases/phpPgAdmin/conf/config.inc.php

Logrotate

  • No service control. Executed by the daily maintenance task:
    /etc/cron.daily/50plesk-daily
  • Configuration
    • /usr/local/psa/etc/logrotate.conf
    • /usr/local/psa/etc/logrotate.d/*

Webalizer

  • No service control. Executed by the daily maintenance task:
    /etc/cron.daily/50plesk-daily
  • Configuration
    • /srv/www/vhosts/system/<domain>/conf/webalizer.conf

AWstats

  • No service control. Executed by the daily maintenance task:
    /etc/cron.daily/50plesk-daily
  • Configuration
    • /usr/local/psa/etc/awstats/awstats.<domain>-*.conf

Watchdog (monit)

  • Logs:
    • /usr/local/psa/var/modules/watchdog/log/wdcollect.log
    • /usr/local/psa/var/modules/watchdog/log/monit.log
  • Service control:
    • Stop:
      /usr/local/psa/admin/bin/modules/watchdog/wd --stop
    • Start:
      /usr/local/psa/admin/bin/modules/watchdog/wd --start
    • Restart:
      /usr/local/psa/admin/bin/modules/watchdog/wd --restart
  • Configuration:
    • /usr/local/psa/etc/modules/watchdog/monitrc
    • /usr/local/psa/etc/modules/watchdog/wdcollect.inc.php

Watchdog (rkhunter)

  • Logs:
    • /var/log/rkhunter.log
  • Service control:
    • Start:
      /usr/local/psa/admin/bin/modules/watchdog/rkhunter
  • Configration:
    • /usr/local/psa/etc/modules/watchdog/rkhunter.conf

Plesk Firewall

  • Service control:
    • Stop:
      /etc/init.d/psa-firewall stop
    • Start:
      /etc/init.d/psa-firewall start
    • Restart:
      /etc/init.d/psa-firewall restart
  • Configuration:
    • /usr/local/psa/var/modules/firewall/firewall-active.sh
    • /usr/local/psa/var/modules/firewall/firewall-emergency.sh
    • /usr/local/psa/var/modules/firewall/firewall-new.sh

Plesk Firewall (IP forwarding)

  • Service control:
    • Stop:
      /etc/init.d/psa-firewall-forward stop
    • Start:
      /etc/init.d/psa-firewall-forward start
    • Restart:
      /etc/init.d/psa-firewall-forward restart
  • Configuration:
    • /usr/local/psa/var/modules/firewall/ip_forward.active
    • /usr/local/psa/var/modules/firewall/ip_forward.saved

IP Address Banning (Fail2Ban)

  • Service control:
    • Stop:
      /etc/init.d/fail2ban stop
    • Start:
      /etc/init.d/fail2ban start
    • Restart:
      /etc/init.d/fail2ban restart
  • Configuration: A set of IPTables rules. By default:-
    • iptables -N fail2ban-plesk-login
    • iptables -A fail2ban-plesk-login -j RETURN
    • iptables -A INPUT -p tcp -m multiport --dports 8880,8443 -j fail2ban-plesk-login

Apache fails to restart on plesk server on CentOS 6.5

# service httpd restart
Stopping httpd:                                            [FAILED]
Starting httpd: Syntax error on line 55 of /etc/httpd/conf/plesk.conf.d/ip_defalt/domain.com.conf:
SSLCertificateFile: file '/usr/local/psa/var/certificates/cert-6xg952' does notexist or is empty

Solution:

# /usr/local/psa/admin/sbin/httpdmng --reconfigure-all
# service httpd restart

edit /etc/my.cnf to show the following…

[mysqld]
port = 3306
# bind-address = 10.10.0.1
# skip-networking
....

Where,

* bind-address : local IP address to bind to. If you wish mysql listen on all IPs, don’t use this option.

* skip-networking : Don’t listen for TCP/IP connections at all. All interaction with mysqld must be made via Unix sockets. This option is highly recommended for systems where only local requests are allowed. Since you need to allow remote connection this line should be removed from file or put it in comment state.

Restart MySQL.

# service mysqld restart

Now you should grant access to remote IP address, login to Mysql:

# mysql -uadmin -p`cat /etc/psa/.psa.shadow` mysql

For example if you want to allow access to database called ‘foo’ for user ‘bar’ and remote IP 192.168.0.1(The IP you are connecting from) then you need to type following commands at “mysql” prompt:

mysql> GRANT ALL ON foo.* TO bar@'192.168.0.1' IDENTIFIED BY 'PASSWORD';

If you want to grant remote access for all databases to any IP:


mysql> GRANT ALL PRIVILEGES ON *.* TO 'USERNAME'@'%' IDENTIFIED BY 'PASSWORD' WITH GRANT OPTION;

Be sure to check that Iptables is set up with the info to allow the remote connection

# iptables -A INPUT -i eth0 -p tcp -m tcp --dport 3306 -j ACCEPT

To add to an existing database:

Other sources:
http://www.cyberciti.biz/tips/how-do-i-enable-remote-access-to-mysql-database-server.html

There are two files that matter:


# /var/www/vhosts/default/htdocs/index.html
# /var/www/vhosts/.skel/0/httpdocs/index.html

Also, if present:


# /var/www/vhosts/default/httpsdocs/index.html
# /var/www/vhosts/.skel/0/httpsdocs/index.html

Windows Plesk files are in similar locations — C:\inetpub\vhosts\ instead of /var/www/vhosts

Edit index.html after backing up.

nginx: [emerg] bind() to 68.168.98.181:443 failed (99: Cannot assign requested address)
nginx: configuration file /etc/nginx/nginx.conf test failed

You can disable nginx which should force the configuration to rebuild:

/usr/local/psa/admin/bin/nginxmgr -d

You can also try the steps below:

http://kb.sp.parallels.com/en/114245

If you get the error:

Apache config (14180811290.93120100) generation failed: Template_Exception: nginx: [emerg] bind() to 68.168.98.181:80 failed (99: Cannot assign requested address)

Re-read the IP’s in plesk. Then try again.

Plesk Mail not working. Loogs show:

Dec 3 16:20:17 webserver postfix/cleanup[32266]: warning: connect to Milter service unix:/var/spool/postfix/ctmilter/ctmilter.sock: No such file or directory
Dec 3 16:20:17 webserver postfix/cleanup[32266]: A8D731406FD6: milter-reject: CONNECT from localhost[127.0.0.1]: 4.7.1 Service unavailable - try again later; from=<psaadm@webserver.domain.com> 

The Postfix config ‘/etc/postfix/main.cf’ contains entries with extra commas:


# grep milters /etc/postfix/main.cf    
smtpd_milters = ,, inet:127.0.0.1:12768 unix:/var/spool/postfix/ctmilter/ctmilter.sock   
non_smtpd_milters = ,, inet:127.0.0.1:12768 unix:/var/spool/postfix/ctmilter/ctmilter.sock   

smtpd_milters = ,, inet:127.0.0.1:12768

became

smtpd_milters = inet:127.0.0.1:12768

Then restart postfix,

# service postfix restart

Other sources:
http://kb.sp.parallels.com/en/121170
http://kb.sp.parallels.com/en/116748

The update of Parallels Panel has failed: “Syntax error in file panel.inf3: Error parsing Element”

Cause

The issue is temporary and caused by network connectivity issue to one of the autoinstaller mirrors.
Resolution

As a workaround use another autoinstaller mirror, add the following IP addresses for autoinstall-win.pp.parallels.com to the hosts file:

93.184.221.133 US, Kansas
68.232.34.73 US, California
72.21.81.253 US, California
46.22.75.111 EU, United Kingdom
72.21.89.132 EU, Germany

For example:

93.184.221.133 autoinstall-win.pp.parallels.com