ServerBuddies Support Blog

SSL on the server’s main domain with DirectAdmin

If an Admin wishes to add an SSL certificate on the main server’s domain, they must do it manually. To do this, the Admin must obtain the certificate and key (explained in just a moment). After these have been acquired, the Admin will have to edit /etc/httpd/conf/httpd.conf file and scroll to the very bottom. You should see 2 virtual host directives. With the one that says <VirtualHost :443> you must modify the SSL tags.

Set:

You have a few options when it comes to obtaining the key and certificate. First you can create you own self signed certificate. You can do this by typing the following:

The second line is to remove the password from the key so that apache won’t hang on bootup waiting for the key password. Those commands will create a self signed certificate (remove the key.temp file after you’re done) but if you want to use an authority to sign your certificate (removes the annoying popup), you’ll need to create a certificate request:

and you send the certificate.request file to to certificate authority to be signed. They will send you a signed certificate which you will install using the apache tags noted above (and you can delete the certificate.request file, it’s not needed).

Source and Credit - http://www.directadmin.com

To make a domain secure Web content available in Plesk

After migration, secure Web content (available via the https protocol) become unavailable. The reason is that in Parallels Plesk Panel, secure Web content can be stored either in a directory different from the directory with common Web content (default option), or in the same directory.

To make a domain secure Web content available, enable the Use a single directory for housing SSL and non-SSL content option.

Go to the domain Home page > Web site: Web Hosting Settings > Preferences: Use a single directory for housing SSL and non-SSL content checkbox.

Prevent subdomains and domain aliases in the DNS zones belonging to other users in Plesk.

By default, users can create new subdomains and domain aliases in the DNS zones belonging to other users. This means that they can set up Web sites and e-mail accounts which could be used for spamming, fishing or identity theft.

To prevent users from setting up domains and domain aliases in the DNS zones belonging to other users:

1. Go to Settings > Restrict Creation of Subzones (in the DNS group).
2. Select the Do not let users create DNS subzones in other users’ DNS superzones check box.
3. Click OK.

If you want to change the settings for recursive domain name service:

Go to Home > DNS Settings (in the Server group) > DNS Recursion.

Select the option you need:
* To allow recursive queries from all hosts, select Allow for all requests.
* To allow recursive queries from your own server and hosts from your network, select Allow for local requests only.
* To allow recursive queries only from your own server, select Deny.
Click OK.

Transferring User Accounts, Domain Names and Web Sites to Plesk Panel

You can transfer data (user accounts, settings, Web sites and e-mail) to your Parallels Plesk Panel from other hosting servers managed by earlier versions of Parallels Plesk Panel or other Web hosting software.

Data transfers from Windows-based servers to Linux/Unix-based servers are not supported by the Migration Manager function available from the Parallels Plesk Panel; however, you can transfer data from a Windows-based server to a Linux/Unix-based server by backing up data on a source server and then restoring them on the destination server using the command line backup and restore utilities.

Go to Home > Migration Manager (in the Help & Support group).
To check if there are any updates for Migration Manager components, click Synchronize. These updates may include files of migration agents that enable support for transferring data from hosting platforms other than Parallels Plesk Panel.

Click Start New Migration.
Leave the Transfer data from another server option selected, and specify the following options:

The source server’s address. Specify either the IP address or the host name of the server, from which you want to transfer data.
The login name and password used for logging in to the source server.

Select the type of operating system running on the source host. (This option is available if you are using Parallels Plesk Panel 9 for Windows hosting platform.)
Specify the path to the directory where temporary files will be stored.

Specify whether you want to transfer all data related to user accounts and domains from the source server, or only specific items.

Select the data compression option, if you pay per the amount of transferred data, or if you want to save bandwidth. Data compression saves bandwidth, but consumes more disk space.
Click Next>>. The migration manager will connect to the specified server and gather information about the business objects of the source hosting platform.

If you are transferring data from hosting platforms other than Parallels Plesk Panel, select the version of the migration agent that must be used and then click Next >>. Parallels Plesk Panel automatically selects the appropriate agent version; however, if data transfer fails, you can try selecting another version of migration agent.

Source : parallels.com/Plesk/