Archive

Posts Tagged ‘WHM’

WebHost Manager 11 Documentation - Account Information - List Parked Domains

January 5th, 2009
No comments

Warning: file_get_contents(http://ecs.amazonaws.com/onca/xml?Service=AWSECommerceService&AWSAccessKeyId=1TJ8QTQ6ZFCVAJ3X1T02&AssociateTag=ii0c3-20&Operation=ItemSearch&SearchIndex=Books&ResponseGroup=Small,Images&Keywords=account) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 400 Bad Request in /home/manusia2/public_html/wp-content/plugins/amazonfeed/php/amazonfeed.class.php on line 271

This function displays all domains that are parked on top of another domain. For more information about parking a domain, refer to Park or Point a Domain.

Steps
  1. To access the Account Information Menu, click on Account Information, on the main screen of your WebHost Manager interface.
  2. Click on List Parked Domains.
  3. A list of parked domains will now appear.
Tags: account, cPanel, domain, WHM, WHM

Related posts

WHM , , ,

WebHost Manager 11 Documentation - Security

January 5th, 2009
No comments

Manage SSH Keys

SSH allows secure file transfer and remote logins over the Internet. Your secure connection via SSH is encrypted. You can manage your SSH keys to allow automation when logging in via SSH. You can import existing keys, generate new keys, and manage/delete keys.

Generate A New Key

Steps
  1. To access the Manage SSH Keys feature, click on Security, on the main screen of your WebHost Manager interface.
  2. Then click on Manage SSH Keys.
  3. Click on the Generate a New Key link.
  4. Set the following:
  • Key Name (defaults to id_dsa) - Enter the key name for your SSH client.
  • Key Password (blank for none) - Enter the password, if applicable, for your SSH client. Otherwise, leave empty or blank for none.
  • Key Type- Choose from the following:
  • Key Size - Choose from the following:
    • 1024
    • 2048
    • 4096
  1. Click on the Generate Key button.
  2. You should see a list of messages stating the status of your SSH Key generation.
  3. Go back to the Manage SSH Keys page. You should see your new key listed in the “Name” column in the “Public Keys” table. Find your key. You should see a “not authorized” message in the “Authorization Status” column. Now you need to authorize your key by clicking on the Manage Authorization link in the “Actions” column.

NOTE: Your new SSH key is also created in the “Private Keys” table.

  1. When the page loads, you will see the name of the key you are authorizing. Click on the Authorize button.
  2. After you have authorized your public key, click on the “Return to SSH Manager” link.
  3. The “Authorization Status” column should now show “authorized” for your public key.

Import Key

Steps
  1. Click on the Import Key link.
  2. Set the following:
  • Choose a name for this key (defaults to id_dsa)
  • Private key passphrase (Needed for PPK import only)
  1. Next, paste the Private Key in the text box (you can also paste a PPK file as well).
  2. Paste the Public Key in the text box (4th text box shown).
  3. Click on the Import button.

NOTE: You don’t have to import both keys. It is perfectly acceptable to just import a public OR private key if that is all you need on the server.

Defining The Public Keys Table

The Public Keys Table consist of three columns, containing the following information:

  • Name - This entry is the name of your public key.
  • Authorization Status - This entry indicates the status of your public key’s authorization. You manually authorize the key by clicking on the Manage Authorization link in the “Actions” column as defined below. The two messages in the “Authorization Status” column are as follows:
    • authorized
    • not authorized
  • Actions
    • Delete Key - Click on this link to delete the associated public key.
    • View/Download Key - Click on this link to view or download the associated public key.
    • Manage Authorization - Click on this link to authorize the associated public key.

Defining The Private Keys Table

The Private Keys Table consist of two columns, containing the following information:

  • Name - This entry is the name of your private key.
  • Actions
    • Delete Key - Click on this link to delete the associated private key.
    • View/Download Key - Click on this link to view or download the associated private key.
Tags: cPanel, password, ssh, WHM, WHM

Related posts

WHM , , ,

Easy Apache 3 n PHP - Common Questions 2

January 4th, 2009
No comments

What permissions do my PHP scripts need?

As mentioned in the previous section, all of the PHP configurations supported by cPanel require appropriate read access the the script. If the “nobody” user will be executing it, the “nobody” user much be capable of reading it. Generally speaking, this means 0644 permissions should be adequate for all setups.

I changed the PHP configuration, but PHP doesn’t seem to be working properly.

First, perform a HARD restart of Apache. If that doesn’t fix the problem, verify that the “Include /usr/local/apache/conf/php.conf” directive is in httpd.conf

If that is okay, check the error log for obvious problems.

If nothing particularly revealing is in the logs, check the .htaccess files in all directories leading to the script for bad AddHandler directives.

How do I get PHP working in /usr/local/apache/htdocs?

The answer to this question depends largely on how PHP is being handled.

DSO
Should work by default without any tweaking.
SuPHP
Versions of cPanel/WHM before revision 19254 did not add the directives required to run PHP scripts using mod_suphp in the main apache document root. To fix this issue, update cPanel, run “/usr/local/cpanel/bin/apache_conf_distiller –update –main” and “/scripts/rebuildhttpdconf“. This should add suPHP_UserGroup directives to the default Virtual-Hosts in httpd.conf and mod_suphp should begin serving PHP requests directed at those hosts. PHP scripts will must be owned by the “nobody” user and group.
CGI/FCGID
These should work by default, but /usr/local/apache/htdocs must be configured with the ExecCGI directory option. The standard httpd.conf file shipped with Apache does not have this option set.
Tags: Apache, cPanel, EasyApache, htaccess, php, WHM

Related posts

EasyApache , , , ,

Apache n PHP Customization - Using Custom Configure Flags

January 4th, 2009
No comments

Modifying your configure flags can break the compilation of Apache. cPanel is not responsible for custom changes and provides no warranty of any kind with this information. Proceed with caution.

EasyApache also allows you to specify any configure option supported by Apache and/or PHP. To add configuration options, simply place the option in the appropriate file (one option per line, format: option=value):

Configure Option Examples

If the file contains the following lines:

--with-someoption
–path-to-something=/usr/bin/something
–my-option=

The following will be added to the configure line:

--with-someoption --path-to-something=/usr/bin/something --my-option

You’ll notice that the configure line has “–my-option” instead of “–my-option=”. This is because the file is parsed and then properly formatted options are merged into the configure data structure.

Skipping your Custom Options

If needed, you can skip building with these custom options by running EasyApache with the –skip-rawopts flag like so:

/scripts/easyapache --skip-rawopts

Through WHM, you can skip the options by clicking on the Help Link inside the Apache Update interface and then making sure the option for Do not use raw opts support is checked.

Tags: Apache, cPanel, EasyApache, php, raw, WHM

Related posts

EasyApache , , , ,

Apache n PHP Customization - Modifying Environmental Variables

January 4th, 2009
No comments

Modifying your Apache or PHP Variables can break the compilation of Apache. cPanel is not responsible for custom changes and provides no warranty of any kind with this information. Proceed with caution.

EasyApache has the ability to let you change, add, or append to any environment variables you may want. These changes must be made on the command line before running /scripts/easyapache or Apache Update through WHM.

Adding or Changing Variables

First, create a file in /var/cpanel/easy/apache/rawenv/ with the name of the environmental variable.

For example, you could edit the PATH variable by creating /var/cpanel/easy/apache/rawenv/PATH. The contents of this file should be the value of the variable. Assuming your desired $PATH is “/bin:/usr/bin:/sbin:/usr/sbin“, the file would contain only: /bin:/usr/bin:/sbin:/usr/sbin

Appending Variables

However, for the PATH variable, it is not ideal to replace it as your path needs might change. Instead, you can append your PATH change by creating a /var/cpanel/easy/apache/rawenv/.append_PATH file. In that file, simply place the path you wish to append to $PATH. For example: :/home/bin

Prepending Variables

You can also prepend variables by adding a .prepend_VARIABLE file.

Skipping your Custom Options

If needed, you can skip building with these custom options by running EasyApache with the –skip-rawenv flag like so:

/scripts/easyapache --skip-rawenv

Through WHM, you can skip the options by clicking on the Help Link inside the Apache Update interface and then making sure the option for Do not use raw env support is checked.

Tags: Apache, cPanel, EasyApache, php, raw, WHM

Related posts

EasyApache , , , ,