CP+ 3.x Documentation Admin Guide

Default Website Configuration

Related Docs:   Adding Websites   Managing Websites

The Default Website Configuration page is divided into sections:

 

Simple Configuration

 

Server Settings

Some of these options:

  • BIND setup and configuration enabled?: if enabled, then a set of domain name records for the new virtual host will be created. It automatically creates a host record for www and mail, the domain name itself and an MX record.
  • Mailbox and alias configuration enabled?: if this option is enabled, it allows to configure local email addresses and aliases.
  • Mail server to configure: choose one of the listed mail servers, or set Detect automatically.
  • Apache setup and configuration enabled?: if enabled, virtual hosts will be setup in the Apache httpd.conf file.
  • Webalizer report generation enabled?: if enabled, and Webalizer is installed, then the Webalizer report will be automatically generated for each new domain. The Webalizer is a fast, free web server log file analysis program. It produces highly detailed, easily configurable usage reports in HTML format, for viewing with a standard web browser.
  • SSL website setup enabled?: SSL (Secure Sockets Layer) is applied to the protected data exchange between Web-browsers and Web-servers.
  • MySQL/PostgreSQL setup and configuration enabled?: if enabled, options to setup database users and permissions for new domain users will be provided.
  • FTP setup and configuration enabled?: if this option is enabled, it allows to create and configure virtual ProFTPd/VSFTPd servers.
  • Logrotate log file truncation enabled?: if this option is enabled, it allows to configure LogRotate for website.
  • Quota setup for domain and mail users?: if enabled, this option will setup the hard and soft quota limits for each new domain user and mailbox user on the system.
  • Quota type to set: Hard quotas are strictly enforced by the system, and will prevent users from using any more than the allowed disk space. Soft quotas are only advisory, and will merely generate a warning when exceeded.

Make sure to click Save to preserve changes.

 

Defaults For New Domains

Some of these options:

  • Home directory base: specifies the default home directory base location.
  • Shell for mailbox users: specifies the default shell of new local and virtual domain mailbox users.
  • Shell for FTP users: specifies the shell that FTP users will be assigned. By default /bin/false is used.
  • Shell for jailed FTP users: applies to users who are jailed into their own home directory on login.
  • Shell for domain users: new virtual domain users will default to the shell specified here.
  • Include domain name in usernames?: specifies how new usernames will be created for virtual domain mail users. If Always is selected, the domain name will always be appended to the end of the username.
  • Domain name style in usernames: configures how the usernames are generated for virtual domains. If Full domain name is selected, the fully qualified domain name will be appended to domain mailbox users. If First part of domain is selected, the name will exclude the top level domain.

Make sure to click Save to preserve changes.

 

VPOPMail Options

Make sure to click Save to preserve changes.

  • Base directory for VPOPMail: VPOPMail uses a balanced directory tree that grows as needed, the base of that directory is specified here.
  • VPOPMail user: user account under which the VPOPMail server will run. This should not be an account with privileges beyond what is necessary to operate and deliver mail to the directory specified in the previous option.
  • VPOPMail group: group under which the VPOPMail server will run.
  • Path to autorespond program: if the autorespond program is installed, specify its location here.

 

Default Limits For New Domains

Some of these options:

  • Default database name restriction: determines whether a user with database creation privileges can name the database anything he likes.
  • Include alias domains in limits?: Alias domains are domains that point to an existing domain for some or all services. To consider alias domains as part of the domain they alias for quota purposes, select yes here. If the account limits will be specified separately, select no.
Make sure to click Save to preserve changes.

 

Advanced Configuration

 

Domain Template Details

  • Skeleton directory for files: points path to skeleton directory - template for creating domain's home directory (default path is /etc/skel).
  • Users visible in chooser: points users, visible for popup-forms "Select User.." in domain-owner's interface (you can set them as list of users or you can point list of groups, which from selected users are).
  • Groups visible in chooser: point groups, visible for popup-forms "Select Group.." in domain-owner's interface ( substitution ${GROUP} is used as default).
  • Root directory in file chooser: sets the root directory for popup-forms "Choose File.." in domain-owner's interface.

Make sure to click Save to preserve changes.

 

Networking Settings

  • Network interface for virtual addresses: allows to choose which interface to use for virtual domains, if server has multiple interfaces.
  • Base number for virtual interfaces: the system can automatically calculate new virtual host IP addresses for you, based on incrementing up from the last used address. By default, it starts with the primary address on the interface selected in the previous option.
  • Default virtual server IP address: the system will, if possible, choose for virtual hosts to listen on all IPs. If there is not an appropriate VirtualHost directive to permit this, it will use the IP address specified here. The default is the address of the network interface specified in the Network interface for virtual addresses option above.
  • Default IP address for DNS records: if you operate a type of device that leads to your server operating on a different address than the world sees when talking to your virtual domains, you may wish to alter the value here.
  • Delete all Apache virtual hosts in domain when deleting?: selects whether all virtual hosts within the domain will be removed on deletion of a virtual server account.
  • All Apache virtual servers are name-based?: with name-based virtual hosting, the server relies on the client to report the hostname as part of the HTTP headers, so many different hosts can share the same IP address.

Make sure to click Save to preserve changes.

 

Actions Upon Domain And User Creation

  • From: address for email sent by CP+: CP+ sends email to users for a number of reasons, such as disk usage quota overage, bandwidth usage overage, account creation, etc. You may choose what address will be used in the From: field of these messages.
  • Template file for email to new mailboxes: if new mailboxes created should automatically be sent a message, you may specify it here.
  • Template file for email to servers over traffic limit: notifies a domain owner if the traffic usage for the domain has surpassed the quota. You may use the default message, or create your own and specify it here.
  • Template file for email to servers approaching bandwidth limit: notifies a domain owner if the bandwidth usage for the domain is approaching the quota. You may use the default message, or create your own and specify it here.

Make sure click Save to preserve changes.

 

Settings For New Websites

Some of these options:

  • Default Unix group for domain owners: by default, the group for the Unix user who is created to own this domain's files will be the same as the group for its mail users. However, you can select an existing group on the server instead, which can be useful if you have some kind of group-based access restrictions in force.
  • Automatically add appropriate SuExec directive?: SuExec is a feature of Apache that allows CGI scripts to be executed with only the privileges of the owner of the directory where the script is located. It also introduces other protections to help prevent insecure script usage. SuExec is highly recommended except for in environments where all domain owners are trusted users.
  • Write logs via program? (Handles missing log directory): provides a special log writer application that solves the problem of users deleting their own log directory, which can cause Apache to fail on startup.
  • Add Apache user to Unix group for new servers?: determines whether the user that Apache runs as will be added to the new virtual host group.
  • Permissions on website subdirectory: specifies the initial permissions on the files and directories within the website subdirectory specified in the previous option. If SuExec has been enabled, and the Apache user is added to the virtual server user group, these permissions can be tightened to prevent other users from seeing the contents of the website directory: the owner can read, write and execute, the group can read and execute, and others have no permissions to read, write or execute files within the directory.
  • Subdirectory for Webalizer statistics: if Webalizer log report analysis is enabled, this option will specify where the reports are generated.
  • Password-protect statistics?: if Webalizer log reports should be protected by a password, select yes here.
  • Create alias websites by: a domain alias is a new domain that simply forwards web requests and email to the primary domain that it is an alias of. Currently, web traffic can be directed to the primary domain via a set of ProxyPass rules, a Redirect rule, or simply adding a ServerAlias to the parent domain.
  • Port number for virtual hosts: specifies the port on which the virtual host will listen. By default, it will listen on the same default port as the system-wide Apache configuration specifies (normally 80).
  • Configure CP+ to use same SSL cert for IP?: if this template will be used exclusively for SSL-capable websites, you can enable this option.
  • Configure End User to use same SSL cert for IP?: if this template will be used exclusively for SSL-capable websites, you can enable this option.
  • Template Webalizer configuration: if domains created from this template should have a Webalizer configuration different from the default, you may specify a configuration file containing your preferences here.

Make sure to click Save to preserve changes.

 

DNS Records

  • BIND DNS records for new domains | Record mode: allows to add custom DNS records to automatically created records for new domain, or use only custom records. The records should be in the following format:
    name(space) type(space) value
  • Create new domains in view: specifies DNS view for the created domain.

Make sure to click Save to preserve changes.

 

ProFTPd Directives

  • FTP directives for new servers: allows to specify exactly what options will be enabled on a newly generated virtual server.
  • Anonymous FTP subdirectory to create: allows to choose name of anonymous FTP subdirectory (/home/ftp as default) or in user's home. It is necessary to change also value of anonymous in “ProFTPd directives for new servers” block above.

Make sure to click Save to preserve changes.

 

EMail Settings For New Domains

  • Email message to send upon server creation: creating new domain you can send e-mail messages to domain owner (e-mail address, noticed when you added website) and some other e-mail addresses. You can edit message text and subject.

Make sure to click Save to preserve changes.

 

Default Database Details

Some of these options:

  • Wildcard for additional allowed databases: allows to use wildcard for databases, associated with domain.
    Ex.: database names may save as domainname_databasename.
  • Create database as well as login?: allows to create MySQL databases or just its MySQL-logins while you create a new domain.
  • Update databases password to match server?: allows/denies correspondence of MySQL password and domain's password.

Make sure to click Save to preserve changes.


Home   Features   Pricing   Resellers   Docs   News   Contact
© Copyright 1998-2006. Positive Software Corporation.
All rights reserved.
Disclaimer