Including Directives into Web Server Configuration File - Plesk
Note: you can change the location of virtual host directories using the transvhosts.pl utility, which is located either in /usr/local/psa/bin/ or /opt/psa/bin/ directory, depending on your operating system.
You can include domain-specific Apache configuration directives into web server configuration file. In Parallels Plesk Panel, each domain has virtual hosts configuration stored in a separate file httpd.include.
On all Linux systems, this file is located in the directory /var/www/vhosts/domain-name/conf/.
On FreeBSD systems, this file is located in the directory /usr/local/psa/home/vhosts/domain-name/conf/.
To use custom directives or redefine those inserted by Parallels Plesk Panel, you need to create the files vhost.conf or vhost_ssl.conf with necessary directives in the directory /path_to_vhosts/domain-name/conf/ for a domain, and /path_to_vhosts/domain-name/subdomains/subdomain-name/conf/ for a subdomain.
Resource: http://parallels.com/Plesk/
Restoring Mail Configuration in Plesk
Sometimes, Parallels Plesk Panel mail server configuration becomes corrupt and it is necessary to restore it. The restoration is carried out by internal mchk utility, intended for use by Parallels Plesk Panel.
However, as administrator, you can use it for restoring the Qmail and Courier-imap configuration when needed.
By default mchk is running in the background mode.
To execute it in the foreground, use the -v option. For example:
/usr/local/psa/admin/sbin/mchk -v
Reference : http://parallels.com/Plesk/
IPsec Host-to-Host Configuration
For a host-to-host connection, you need the following information:
The IP address for both hosts.
A unique name to identify the IPsec connection and distinguish it from other devices or connections (for example, ipsec0).
A fixed encryption key or one automatically generated by racoon.
A pre-shared authentication key that is used to initiate the connection and exchange encryption keys during the session.
For example, suppose Workstation A and Workstation B want to connect to each other through an IPsec tunnel. They want to connect using a pre-shared key with the value of ‘buddies’ and the users agree to let racoon automatically generate and share an authentication key between each host. Both host users decide to name their connections ipsec0.
The following is the ifcfg file for Workstation A for a host-to-host IPsec connection with Workstation B (the unique name to identify the connection in this example is ipsec0, so the resulting file is named /etc/sysconfig/network-scripts/ifcfg-ipsec0):
DST=X.X.X.X TYPE=IPSEC ONBOOT=yes IKE_METHOD=PSK
Workstation A would replace X.X.X.X with the IP address of Workstation B, while Workstation B replaces X.X.X.X with the IP address of Workstation A.
The connection is set to initiate upon boot-up (ONBOOT=yes) and uses the pre-shared key method of authentication (IKE_METHOD=PSK).
The following is the content of the pre-shared key file (called /etc/sysconfig/network-scripts/keys-ipsec0) that both workstations need to authenticate each other.
The contents of this file should be identical on both workstations and only the root user should be able to read or write this file.
For Security chmod to 600
chmod 600 /etc/sysconfig/network-scripts/keys-ipsec0
Configuration Files in Webmin
Most Webmin modules work by editing configuration files on your system, like
/etc/exports for NFS shares,
/etc/passwd for users
/etc/fstab for filesystems.
Each module knows which configuration files it manages, and what commands need to be run to activate them. Not all modules actually deal with config files though - for example, the MySQL module works by executing SQL commands.
As such, it cannot participate in the configuration backup process.
More in details at http://doxfer.com/Webmin/
Webmin Backup Configuration Files module
Most Webmin modules work by editing configuration files on your system, like /etc/exports for NFS shares, /etc/passwd for users and /etc/fstab for filesystems.
Each module knows which configuration files it manages, and what commands need to be run to activate them.
Not all modules actually deal with config files though - for example, the MySQL module works by executing SQL commands.
The Backup Configuration Files module
To perform an immediate config backup, follow these steps :
Click on the Backup now tab.
In the Modules to backup list, select the modules you want to backup config files for, such as Users and Groups. Multiple modules can be selected by ctrl-clicking.
In the Backup destination field, select Local file and enter a path to write the backup to. This should be given a tar.gz extension, as that is the file format used.
Click the Backup Now button.
