Managing Log Files and Log Rotation

Plesk allows managing log files and log rotation settings from the control panel. To access these functions, click the  Log Manager icon on the Domain Administration page. The Log Manager page will open:

• Define the number of log file's lines to be displayed at once. To do that, type in the number of lines in the Lines of log file to be displayed input field prior to selecting a log file for viewing.


• View a log file. To this effect, click on a log file's name in the list. The log file contents will be displayed in a separate Log File Viewer window.


• Save a log file on your local machine. To do that, click on the appropriate  icon. After that you will need to specify the location on your local machine and the file name for the downloaded log file to be saved, and then click Save.


• Delete log files. To this effect, select the corresponding checkboxes, and click Remove Selected.

To configure the log rotation preferences, follow these steps:

1. Click the  Log Rotation icon on the Log Files Management page. The Log Rotation Preferences page will open:


2. Click the  Enable or  Disable icon respectively to enable/disable log rotation.


3. Select the log rotation condition:                                                                                      a)  log file size - enter the size in kilobytes in the appropriate field.


4. Specify the maximum number of log files in the appropriate input field, if desired. The maximum number is the number of processed files to be kept for each log file.


5. Select the Compress log files checkbox to enable compression.


6. If desired, in the Send processed log files to e-mail input field, enter the e-mail address, for the processed log files to be delivered to.


7. Click OK to submit changes.

How to create custom error pages

Resolution

If it is necessary to use .php., .asp, etc applications on the domain.

First of all make sure that this extension is allowed in IIS and for the domain.

In Plesk Control Panel create a virtual directory for custom error document files: Domains, domain.name, Web Directories, AddNewVirtualDirectory (it will be created on the server in %plesk_vhosts%\domain.name\httpdocs\)

Create a new file (script that will be run on this error):

Domains, File Manager, httpdocs, Created Virtual Directory, Add new File

Choose created file to be processed for the needed error:

Domains, domain.name, Web Directories, Error Documents, needed error , Location.
It needs to specify it in the following manner:

Type: URl

Location: /Created_Virtual_Directory/file.name

Note: Do not create custom files in %plesk_vhosts%\domain.name\error_docs\ directiry, it will not be processed, because %plesk_vhosts%\domain.name\httpdocs\ used as home directory for custom files.

Error while restarting Qmail from Plesk

“Unable to make action: Unable to manage service by mailmng: mailmng: Service qmail failed to start

0: /usr/local/psa/admin/htdocs/server/restart_services.php:28 psaerror(string “Unable to make action: Unable to manage service by mailmng: mailmng: Service qmail failed to start”)”

This error will occur if the sendmutex log file is missing. This can be resoved by creating this file.

touch /var/qmail/queue/lock/sendmutex
chown qmails:qmail /var/qmail/queue/lock/sendmutex
/etc/init.d/qmail restart

How to install Installatron on a Plesk Windows server

1. Requirements

Check that your server meets the requirements for Installatron.

2. Install Installatron

Download and run the below Windows installation wizard. Windows Administrative privileges will be required.

http://data1.liquenox.com/installatron/installatron_setup.exe

If you experience any errors, see troubleshooting.

3. Use Installatron

Installatron is now ready to use in Plesk for Windows.

The admin login will find the administration tool in Server > Installatron Admin.

Client logins will find the reseller administration tool in Clients > Installatron Admin.

Domain logins will find the script installer tool under Installatron.

DNS not working for a domain in a plesk panel (Windows)

Symptom:
When you are in dedicated Box of windows and using a plesk and you are getting a page not found for a domain name while other domains are working fine in a same box.
All the setting you think are fine and even name server are pointing well then there is a chance of DNS misconfig

Resolution: Editing the Plesk DNS zone database

When the DNS zone for a domain is managed via Plesk, the status for this domain in the dns_zone table of the database is temporarily set to a value of 2 (to lock it for any further changes) and is then set back to a value of 0 value when the changes are processed. If for some reason the process is interrupted (Plesk restarts for example) the status field value may not get changed back to 0 and stays as 2. Therefore any changes are no longer recorded until the status is changed back to 0.

Please note: to isolate database issues with Plesk and your own web services (MySQL or MS SQL), we recommend and setup Plesk to use MS Access databases. If you have setup Plesk to use MySQL or MS SQL databases you will need to use your preferred database viewer to find the necessary DNS zone table. You can view MS SQL instructions below.

1. To view and edit the Plesk DNS zone database you will need to use an MS Access database viewer such as MDBPlus, and then open up the pleskmain.db located at:C:\Program Files (x86)\Parallels\Plesk\admin\db – Note: password is the same as Plesk admin login.


2. Check dns_zone records for the problem domain’s entry (domain.com for example):
   
   
   
   1. if there are multiple entries for the same domain; remove the entry that has the incorrect setting of 2;
   
   
   2. if there is only one entry for the domain, adjust the value in the “status” column from 2 back to 0.
   
   
   
   


3. Save the database.


4. Go back into Plesk and navigate to the DNS zone settings tab for the affected domain.


5. Select “Restore Defaults” to rebuild the appropriate entries for the domain

You should now be able to resolve the domain correctly.

For Plesk installations setup to use MS SQL as the default Plesk database:

1. Login via MSSQL Server Management Studio Express or your preferred MS SQL management tool.


2. Expand the Plesk database.


3. Expand the “tables” section.


4. Scroll down to “dbo.dns_zone“, right-click on this and choose “open table”


5. Delete or modify the erroneous entry as in Step 2. above.

changing the smtp port to 26 in plesk

a) Add the following to /etc/services smtp-26 26/tcp mail

b) Copy /etc/xinetd.d/smtp_psa to /etc/xinetd.d/smtp_psa-26

c) Change the first line from service smtp to service smtp-26

d) Restart xinetd

How to Backup & restore Linux Plesk 8 on domain level

Backup

Create backup

/usr/local/psa/bin/pleskbackup -vvv domains domain.be /home/root/psabackup

Move backup to another server

sftp root@newserverip put /home/root/psabackup

Restore

Create map file

/usr/local/psa/bin/pleskrestore --create-map /root/psabackup -map /root/backup.map

Edit map file

Edit /root/backup.map.

The value between []’s should be replaced with the client name where you want to restore to. Change IP’s by adding -> new IP.

Example; [clientname]

domain.be 85.158.105.250->85.158.105.252
mysql::@localhost:3306

Restore using map file

/usr/local/psa/bin/pleskrestore --restore /root/psabackup -level domains -verbose -map /root/backup.map

How to update awstats in Plesk manually

Update awstats in Plesk Manually

To update stats manually for a domain, you can run the following command. Replace the “domain.com” with the domain name.

$ /usr/local/psa/admin/sbin/statistics –calculate-one –domain-name=domain.com

To generate stats for all the domains in the server, use the following command.

$ /usr/local/psa/admin/sbin/statistics

If you receive any error, please make sure that the binaries are present in the path specified in the configuration file ‘/etc/psa/psa.conf’

$ grep AWSTAT /etc/psa/psa.conf

will return the path

AWSTATS_ETC_D /etc/awstats

AWSTATS_BIN_D /var/www/cgi-bin/awstats

AWSTATS_TOOLS_D /usr/share/awstats

AWSTATS_DOC_D /var/www/html/awstats

Make sure that the following files are present in the correct location.

awstats_buildstaticpages.pl: /usr/share/awstats/awstats_buildstaticpages.pl

awstats.pl: /var/www/cgi-bin/awstats/awstats.pl

Update awstats in Plesk Manually

To update stats manually for a domain, you can run the following command. Replace the “domain.com” with the domain name.

$ /usr/local/psa/admin/sbin/statistics –calculate-one –domain-name=domain.com

To generate stats for all the domains in the server, use the following command.

$ /usr/local/psa/admin/sbin/statistics

If you receive any error, please make sure that the binaries are present in the path specified in the configuration file ‘/etc/psa/psa.conf’

$ grep AWSTAT /etc/psa/psa.conf

will return the path

AWSTATS_ETC_D /etc/awstats

AWSTATS_BIN_D /var/www/cgi-bin/awstats

AWSTATS_TOOLS_D /usr/share/awstats

AWSTATS_DOC_D /var/www/html/awstats

Make sure that the following files are present in the correct location.

awstats_buildstaticpages.pl: /usr/share/awstats/awstats_buildstaticpages.pl

awstats.pl: /var/www/cgi-bin/awstats/awstats.pl

Plesk error: Unable to open logs

While restarting  apache we face the following error in/var/log/httpd/error_log unable to open logs

You need to just fire the below commands and it done:

# echo $ulimit

If it is blank or a low value, try executing the command

# ulimit -n 65536

This is should fix the issue and apache should be working fine.

How to install Plesk license

To install the Plesk License you can use  License Manager function available in the Plesk administrator control panel >>> Server >>> License Management >>> Upload license.

That's all you have to do.

How to backup the Plesk server

The following procedure makes a complete backup of Plesk. The backup includes the domain and account structures, domain names, email accounts.1. You would need to log into the server through ssh.

2. Change into a directory were you would like the backup of Plesk to be saved. In this example I have made a directory called backup and changed into this directory

# mkdir home/backup

# cd home/backup/

3. Type the following the command to start the Plesk backup procedure. This would make a complete backup (-F), to the directory location /home/backup (-f)

# /usr/local/psa/bin/psadump -F -f /home/backup/

You will see the messages that the backup is in progress. After you will see the message

“Server backup is successfully completed”

4. After the backup is complete you can check the archive file which looks similar to;

1 root root 7568786 Oct 11 12:14 psa-7.1.4-p15160828.pureserver.info-20041011.12.archive

You may now save this file to another server via FTP if you wish.

NOTE: A ftp backup of Plesk can also be done using the following format

: @ storing the backup file on remote ftp server.

5. To restore the backup you would need to change back into the home/backup directory and run the following command

/usr/local/psa/bin/psarestore -f psa-7.1.4-p15160828.pureserver.info-20041011.12.archive -m map_ip -s shell_ma

NOTE:

The restore backup might fail on the 1st run. The reason for this is Plesk looks for the map_ip and shell_map files which may not be located, so on the first run it creates the files. If you run the restore command again the procedure would now start to restore Plesk on the system. If you do not get the following message then run the command again for the third time;

“Server restoration is completed”

You can also review the psadump and psarestore logs located at /var/log/ on the server.

Additional options that can be used for making the backup

Options:

* -h – This help.

* -F – Make (f)ull dump(it is default option, -C option is not supported now).

* -z – Enable gzip compression for result dump file.

* -f

* /fullpath/filename – regular file,

* /fullpath/ – dir for dumpfile with default name,

* – – use stdout for output,

* : @

I prefer not to do it this way because the file is too large, making a daily backup very tedious. Most importantly, you cannot roll back your plesk server to an earlier version this way unless you keep the old backup as well. It is a matter of preference and the users ability.

I recomend tar’ing your backups separately.

Create Cron jobs that back up each of the following directory’s

/boot: Files important for boot process

/etc: System configuration files

/home: Domains and home directories of users

/root: Homedirectory of root

/var/lib/mysql: MySQL-Databases

/var/logs: Log-files

/var/spool/mail: User-mailboxes

/var/spool/cron: Cron-Jobs

/usr/lib/python2.1/site-packages: PLESK Configuration

Here is an example:

15 1 * * * tar czvf /home/backup/sql.tar.gz /var/lib/mysql

This will run at 1:15am everyday of every week and of every month and back up the /var/lib/mysql directory naming it sql.tar.gz and storing it in the /home/backup directory.

I store my backups in a newly created directory under my home directory because of space. *Please note*: if you do the same, you must not backup the whole /home directory because if you do you will create an infinite loop, backing up your backup, over and over.

I also recomend you backup domains individually so you are not stuck with a huge tar file. Restoration depends on how fast you can upload your data and set-up the server, that is why I choose the later because I can easily reconfigure plesk and individually upload the tars 10 times faster then uploading a 2 gig file that takes a long time to execute.

# /usr/local/psa/bin/psadump -F -f /home/backup/

You will see the messages that the backup is in progress. After you will see the message

“Server backup is successfully completed”

4. After the backup is complete you can check the archive file which looks similar to;

1 root root 7568786 Oct 11 12:14 psa-7.1.4-p15160828.pureserver.info-20041011.12.archive

You may now save this file to another server via FTP if you wish.

NOTE: A ftp backup of Plesk can also be done using the following format

: @ storing the backup file on remote ftp server.

5. To restore the backup you would need to change back into the home/backup directory and run the following command

/usr/local/psa/bin/psarestore -f psa-7.1.4-p15160828.pureserver.info-20041011.12.archive -m map_ip -s shell_ma

NOTE:

The restore backup might fail on the 1st run. The reason for this is Plesk looks for the map_ip and shell_map files which may not be located, so on the first run it creates the files. If you run the restore command again the procedure would now start to restore Plesk on the system. If you do not get the following message then run the command again for the third time;

“Server restoration is completed”

You can also review the psadump and psarestore logs located at /var/log/ on the server.

Additional options that can be used for making the backup

Options:

* -h – This help.

* -F – Make (f)ull dump(it is default option, -C option is not supported now).

* -z – Enable gzip compression for result dump file.

* -f

* /fullpath/filename – regular file,

* /fullpath/ – dir for dumpfile with default name,

* – – use stdout for output,

* : @

I prefer not to do it this way because the file is too large, making a daily backup very tedious. Most importantly, you cannot roll back your plesk server to an earlier version this way unless you keep the old backup as well. It is a matter of preference and the users ability.

I recomend tar’ing your backups separately.

Create Cron jobs that back up each of the following directory’s

/boot: Files important for boot process

/etc: System configuration files

/home: Domains and home directories of users

/root: Homedirectory of root

/var/lib/mysql: MySQL-Databases

/var/logs: Log-files

/var/spool/mail: User-mailboxes

/var/spool/cron: Cron-Jobs

/usr/lib/python2.1/site-packages: PLESK Configuration

Here is an example:

15 1 * * * tar czvf /home/backup/sql.tar.gz /var/lib/mysql

This will run at 1:15am everyday of every week and of every month and back up the /var/lib/mysql directory naming it sql.tar.gz and storing it in the /home/backup directory.

I store my backups in a newly created directory under my home directory because of space. *Please note*: if you do the same, you must not backup the whole /home directory because if you do you will create an infinite loop, backing up your backup, over and over.

I also recomend you backup domains individually so you are not stuck with a huge tar file. Restoration depends on how fast you can upload your data and set-up the server, that is why I choose the later because I can easily reconfigure plesk and individually upload the tars 10 times faster then uploading a 2 gig file that takes a long time to execute.

How to change the smtp port to 26 in plesk

a) Add the following to /etc/services smtp-26 26/tcp mail

b) Copy /etc/xinetd.d/smtp_psa to /etc/xinetd.d/smtp_psa-26

c) Change the first line from service smtp to service smtp-26

d) service  xinetd restart

MySQL database not listed in Plesk interface

This usually happens when the database is not created via Plesk. Instead, it might have been created via SSH.

To get around this, there are two ways :

1. This is the simpler of the two.

Just take a dump of the database.

mysqldump -u <username> -p <password> databasename > databasename.sql

Drop the database.

mysql -u <username> -p <password>
drop database <databasename>

Create the database via Plesk.
Plesk Control Panel >> Domains >> Mysql Database >> Add Database

Restore the database.

mysql databasename < databasename.sql

2. Another method is a bit complex one and is advised for expert users only.

After taking a backup of the current psa database, you will have to edit it from the backend and add the database details in the database table manually.

Plesk Binaries

Located in the %plesk_bin%\ directory

1) websrvmng.exe

To install hosting for a domain

Quote:

websrvmng.exe --install-vhost --vhost-name=<domain name>

To remove hosting for a domain

Quote:

websrvmng.exe --remove-vhost --vhost-name=<domain name>

To reconfigure hosting for a domain

Quote:

websrvmng.exe --reconfigure-vhost --vhost-name=<domain name>

To reconfigure a subdomain

Quote:

websrvmng.exe --update-subdomain --vhost-name=<domain name> --subdomain=<subdomain>

Passwords for system user and IIS user can be unsynchronized or synchronised using

Quote:

websrvmng.exe --update-anon-password --domain-name=<domain name>

To reconfigure webmail

Quote:

websrvmng.exe --reconfigure-webmail defpackagemng.exe" --fix --type=webmail

2) mchk.exe

To Reset server-wide and domain's mail settings forcefully

Quote:

mchk.exe --all --fix-all

To Check and restore mail settings for a domain defined

Quote:

mchk.exe --domain --domain-name=sampledomain.com

To Check and restore only server-wide mail settings

Quote:

mchk.exe --global-settings

3) protdir.exe

Quote:

protdir.exe --create Protected_Dir -domain domain1.com -add_user MyGuest -passwd "MyPass"

To set a password for the user of a web-protected directory:

Quote:

protdir.exe --update Protected_Sample -domain somewhere.com -update_user johndoe -passwd Password1

To remove protected directory user:

Quote:

protdir.exe --update Protected_Dir -remove_user johndoe

4) Subdomain.exe

Quote:

subdomain.exe --create subdomain2 -domain domain1.com -hard_quota 50 -ssi true

To remove subdomain1.somewhere.com from somewhere.com domain:

Quote:

subdomain.exe --remove subdomain1 -domain somewhere.com

To change the existing subdomain name

Quote:

subdomain1.somewhere.com to the new one - subdomain1_new.somewhere.com

Quote:

subdomain.exe --update subdomain1 -domain somewhere.com -new_name subdomain1_new

To enable FrontPage support for subdomain1.somewhere.com:

Quote:

subdomain.exe --update subdomain1 -domain somewhere.com -fp true

To retrieve information on subdomain1.somewhere.com:

Quote:

subdomain.exe --info subdomain1 -domain somewhere.com

5) domain.exe

Quote:

domain.exe --create domain1.com -clogin John_Doe -dom_user false -www true -hosting true -ip 143.230.22.14 -cgi true -notify false

To retrieve sampledomain.com domain information:

Quote:

domain.exe --info sampledomain.com

To rename sampledomain.com domain to sampledomain1.com domain:

Quote:

domain.exe --update sampledomain.com -new_name sampledomain1.com

To enable domain user account with password "somepass" for sampledomain.com domain:

Quote:

domain.exe --update sampledomain.com -dom_user true -du_passwd somepass

To set name for domain user of a sampledomain.com domain to "John":

Quote:

domain.exe --update sampledomain.com -du_pname "John"

To enable hosting for sampledomain.com domain:

Quote:

domain.exe --update sampledomain.com -hosting true

6) plesksrvmng.exe

To reset the password for admin control panel

Quote:

plesksrvmng.exe

To get the existing password for the admin control panel

Quote:

plesksrvmng.exe -get

7) statistics.exe

Updates the statistics for all domains on the server

Horbe/webmail is not working in plesk

Error when trying to connect to http://webmail.domain.tld/

A fatal error has occurred DB Error: connect failed Details have been logged for the administrator.

#  cat /etc/psa/.psa.shadow > etc/psa/.webmail.shadow

# chown apache.apache /etc/psa/.webmail.shadow

# chmod 600 /etc/psa/.webmail.shadow

You may have a problem with your file:

# /etc/psa/.webmail.shadow

Plesk Binaries

Located in the %plesk_bin%\ directory

1) websrvmng.exe

To install hosting for a domain

Quote:

websrvmng.exe --install-vhost --vhost-name=<domain name>

To remove hosting for a domain

Quote:

websrvmng.exe --remove-vhost --vhost-name=<domain name>

To reconfigure hosting for a domain

Quote:

websrvmng.exe --reconfigure-vhost --vhost-name=<domain name>

To reconfigure a subdomain

Quote:

websrvmng.exe --update-subdomain --vhost-name=<domain name> --subdomain=<subdomain>

Passwords for system user and IIS user can be unsynchronized or synchronised using

Quote:

websrvmng.exe --update-anon-password --domain-name=<domain name>

To reconfigure webmail

Quote:

websrvmng.exe --reconfigure-webmail defpackagemng.exe" --fix --type=webmail

2) mchk.exe

To Reset server-wide and domain's mail settings forcefully

Quote:

mchk.exe --all --fix-all

To Check and restore mail settings for a domain defined

Quote:

mchk.exe --domain --domain-name=sampledomain.com

To Check and restore only server-wide mail settings

Quote:

mchk.exe --global-settings

3) protdir.exe

Quote:

protdir.exe --create Protected_Dir -domain domain1.com -add_user MyGuest -passwd "MyPass"

To set a password for the user of a web-protected directory:

Quote:

protdir.exe --update Protected_Sample -domain somewhere.com -update_user johndoe -passwd Password1

To remove protected directory user:

Quote:

protdir.exe --update Protected_Dir -remove_user johndoe

4) Subdomain.exe

Quote:

subdomain.exe --create subdomain2 -domain domain1.com -hard_quota 50 -ssi true

To remove subdomain1.somewhere.com from somewhere.com domain:

Quote:

subdomain.exe --remove subdomain1 -domain somewhere.com

To change the existing subdomain name

Quote:

subdomain1.somewhere.com to the new one - subdomain1_new.somewhere.com

Quote:

subdomain.exe --update subdomain1 -domain somewhere.com -new_name subdomain1_new

To enable FrontPage support for subdomain1.somewhere.com:

Quote:

subdomain.exe --update subdomain1 -domain somewhere.com -fp true

To retrieve information on subdomain1.somewhere.com:

Quote:

subdomain.exe --info subdomain1 -domain somewhere.com

5) domain.exe

Quote:

domain.exe --create domain1.com -clogin John_Doe -dom_user false -www true -hosting true -ip 143.230.22.14 -cgi true -notify false

To retrieve sampledomain.com domain information:

Quote:

domain.exe --info sampledomain.com

To rename sampledomain.com domain to sampledomain1.com domain:

Quote:

domain.exe --update sampledomain.com -new_name sampledomain1.com

To enable domain user account with password "somepass" for sampledomain.com domain:

Quote:

domain.exe --update sampledomain.com -dom_user true -du_passwd somepass

To set name for domain user of a sampledomain.com domain to "John":

Quote:

domain.exe --update sampledomain.com -du_pname "John"

To enable hosting for sampledomain.com domain:

Quote:

domain.exe --update sampledomain.com -hosting true

6) plesksrvmng.exe

To reset the password for admin control panel

Quote:

plesksrvmng.exe

To get the existing password for the admin control panel

Quote:

plesksrvmng.exe -get

7) statistics.exe

Updates the statistics for all domains on the server

Updater fails with the error during Plesk upgrade: "Autoinstaller busy".

Symptoms
Update with Server > Updater hangs for a long time and then reports error like:

Error: autoinstaller__status_known
Error: Autoinstaller busy.
Warning: Installation is in progress.

Cause
SWsoft Plesk panel times out waiting for response from autoinstaller utility (~5 minutes). It may happen because of high server load or very slow network connection between Plesk server and autoinstall.plesk.com repository server.

Usually this may happen with Plesk for FreeBSD versions starting from 8.1.0 and later, because it takes time for autoinstaller to download, extract and make indexes of SWsoft ports collection.
Resolution
Increase timeout values to greater ones (for example 30 minutes) in the Plesk panel server and Plesk panel PHP configuration files:

/usr/local/psa/admin/conf/httpsd.conf:
Timeout 1800

/usr/local/psa/admin/conf/php.ini:
max_execution_time = 1800

Then restart Plesk panel to accept changes and continue update.

Windows 2003 plesk 8.4 – IP address conflict

While working on a windows 2003 server which has a plesk 8.4 control panel, I got the following error:

Unable to add ip xx.xx.xx.xx with mask 255.255.255.0 to interface PublicNetwork, WMI error code 42
Execute file name: C:\Program Files\SWsoft\Plesk\admin\bin\ifmng.exe

This means that there is an IP conflict, to get this fixed – you have to contact your dedicated server provider and ask them to remove the IP address or to provide a new IP address.

Repair and rebuild Qmail configuration files on plesk

If for some reasons you’re having problems with the mail issues related to qmail server, you can repair and rebuild the qmail configuration files on your linux plesk dedicated server and at the same time restore settings for all the mailboxes which are present on your server.

To get this done, plesk have an utility named mchk and you can use it as below:

Restore all settings except for SpamAssassin configuration

root# /usr/local/psa/admin/bin/mchk --without-spam

Restore all settings

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

Restore only SpamAssassin settings

root# /usr/local/psa/admin/bin/mchk --spam-only

That’s it!

Horde login failed on linux plesk

while logging to webmail got an error “Horde login failed” , had tried to reset the password of the email address but that did not fix the issue. After further investigating what I found is that I was unable to telnet the IMAP port – the command used for this is:

root# telnet localhost 143

Then, checked with ifconfig and got the output:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet6 ::1 prefixlen 128

The line “inet 127.0.0.1 netmask 0xff000000” was missing, to get this fixed I executed the below command:

root# ifconfig lo0 127.0.0.1 netmask 255.0.0.0

Then, I have tried to login using Horde and it worked perfectly fine.