Reaching out to others! Free & Open Source Software, Kannada, L10n, L18n Data Science, Cloud Computing & more…

Resync IIS anonymous username and password on Plesk server

Many customers are prompted for passwords while accessing the sites hosted on Plesk windows servers. If you do not provide the password and cancel the password prompt, you will get the following error on browser:

HTTP Error 401.1 – Unauthorized: Access is denied due to invalid credentials.
Internet Information Services (IIS)

You get this error while your domains anonymous username and passwords are out of sync with IIS. This can be fixed by running a Plesk tool (You will find it only if your server is managed via Plesk Panel) as follows:

C:\Program Files\SWsoft\Plesk\admin\bin\websrvmng.exe —update-anon-password —domain-name=

Please replace with your domain name. The above command syncs IIS.

What if it turns out to be a server wide issue?

Right. Check out the following command to see how you can sync all the website’s anonymous users passwords with IIS.

C:\Program Files\SWsoft\Plesk\admin\bin\websrvmng.exe —update-anon-passwords-all

Enjoy!

Errors while logging into Plesk panel

Symptoms
When attempting to log into Plesk Control Panel the following error is displayed:

Unable to connect to database: saved admin password is incorrect. 0: C:\\Program Files\\SWsoft\\Plesk\\admin\\auto_prepend\\auth.php3:56 psaerror(string “Unable to connect to database: saved admin password is incorrect.”)

Resolution
Such problem occurs when password of admin in Plesk does not match the one set in Plesk database in MySQL.Please find all the steps below:Retrieve the current password using the command as below:

%plesk_bin%\plesksrvclient.exe -get

1. Then it needs to be configured within Plesk MySQL, following the steps below:

-  Edit MySQL configuration file my.ini located in %plesk_dir%\mysql\data\.
-  Add the skip_grant_tables=1 parameter into the [PleskSQLServer] section.
-  Restart the Plesk SQL Server service.

2. Log into Plesk MySQL.
%plesk_dir%\mysql\bin\mysql.exe -P8306 mysql
Execute the following query:
update mysql.user set password=password('current_password') where user='admin';
3. Remove skip_grant_tables=1 from within the [PleskSQLServer] section within %plesk_dir%\mysql\data\my.ini

4. Restart service Plesk SQL Server.

The password should have been assigned.

Note: For the latest Plesk versions in case of MSSQL using as db provider, please use the following KB to change passwod for user admin (replace sa with admin in mssql query).

Source: Parallels KB

Plesk: Repair/rebuild all Qmail configuration files

How do I repair/rebuild all Qmail configuration files and restore settings for all mailboxes?

Resolution:
This can be done with Plesk mchk utility:

# /usr/local/psa/admin/bin/mchk

Synopsis:
mchk [OPTION]
–without-spam – restore all settings except for SpamAssassin configuration
–with-spam – restore all settings
–spam-only – restore only SpamAssassin settings

This utility rebuilds in line with Plesk database Qmail control files in the /var/qmail/control, /var/qmail/users directories and mail users’ settings. Also, it sets proper ownership/permissions for all mailboxes (/var/qmail/mailnames/*).

Example:

# /usr/local/psa/admin/bin/mchk --with-spam

Source: Parallels KB

Plesk/HSPComplete Fix: Unable to resolve hostname

Dig and ping fails on the server though network configuration is found to be fine. No iptables or other firewalls installed on the server.You might face this issue even during the Plesk installation / re-installation.

Resolution :
To fix it you should specify full hostname of the server in the form of “hostname.domain.tld” instead of just “hostname”. Also you should be able to ping the server by hostname. Please follow these steps to resolve this original issue:

1) Run the command below to specify a new hostname of the server. For example it will be “plesk.yourdomain.com”:
# hostname plesk.yourdomain.com

2) Add the following line to the /etc/hosts file, when ip.address is a real IP address of the server:

ip.address.of.your.server plesk.yourdomain.com plesk

3) Change the following variable in the /etc/sysconfig/network file:

HOSTNAME=plesk.yourdomain.com

4) Restart network service
# /etc/init.d/network restart

5) Please make sure that you are able to ping the server by the new hostname:
# ping plesk.yourdomain.com

You should get the following output of ping command:

PING plesk.yourdomain.com (192.168.45.8) 56(84) bytes of data.
64 bytes from plesk.yourdomain.com (192.168.45.8): icmp_seq=1 ttl=64 time=0.086 ms
64 bytes from plesk.yourdomain.com (192.168.45.8): icmp_seq=1 ttl=64 time=0.086 ms
64 bytes from plesk.yourdomain.com (192.168.45.8): icmp_seq=1 ttl=64 time=0.086 ms

6) If ping doesn’t work be sure that ICMP ECHO packets are allowed with:

# /sbin/sysctl net.ipv4.icmp_echo_ignore_all
net.ipv4.icmp_echo_ignore_all = 0

If the server is still not accessible by the hostname then please make sure that firewall is not enabled. In this case you need to turn off any firewall on the server.

Source: https://kb.parallels.com

WordPress Automatic upgrade

We are lazy enough to take some trouble to get the software installations upgraded. SysAdmins always want something to automate checks, patch management etc. I was wondering if its possible to automate WordPress upgrades. Then I found this wonderful plugin called WordPress Automatic Upgrade Plugin by keithdsouza, ronalfy. It has helped me to save time on performing 5 steps upgradation process of WP. No more shell access or SVN setup required for upgrades.

My Dashboard with “Automatic upgrade” option in Manage section.

FYI: This plugin turns out to be handy for website owners, who use Cpanel and other control panel’s to install and manage wordpress blogs. These webhosting control panels will have their own upgrade windows until which users might not be able to enjoy the releases rolled out by wordpress.

I shall write more about the plugins which I use in my blog to help you all with your wordpress installation.

Unable to start IMAP/POP3 Server (Courier-IMAP) from Plesk Panel

If you’re unable to restart IMAP/POP3 Server (Courier-IMAP), have a look at the logs at /var/log/messages :

Following errors were found while digging the logs

Jul 29 22:42:21 asap3d courier-imap:    Starting pop3 succeeded
Jul 29 22:42:21 asap3d pop3d-ssl.rc: bind: Address already in use
Jul 29 22:42:21 asap3d pop3d-ssl.rc: ll_daemon_start: Resource temporarily unavailable

Above error will pop in due to incorrect courier-pop3d configuration or courier-pop3d is enabled via xinetd on the server.

If you find courier-pop3d and courier-pop3ds configured via xinetd, do disable it by editing the files under /etc/xinetd.d. Once this is done, restart xinetd and then try restarting  IMAP/POP3 Server (Courier-IMAP) from Plesk Service Management. It should work fine.

In the following example, check line number 3 (disable = yes) which disables the service under xinetd.

service pop3
{
disable = yes
flags = NODELAY
socket_type = stream
wait = no
user = root
server = /usr/bin/tcp-env
server_args
= -R -f /usr/lib/courier-imap/etc/

pop3d /usr/lib/courier-imap/sbin/pop3login /usr/lib/courier-imap/libexec/authlib/authpsa /usr/lib/courier-imap/bin/pop3d
Maildir
log_type = FILE /var/log/pop3d.log
log_on_success = PID HOST EXIT DURATION
log_on_failure = HOST ATTEMPT
}