Author: admin

Cpanel how to change ip address for addon domain

It’s not directly possible from WHM inteface. But you can manaully edit then cpanel config files and assign dedicated IP for the addon domain and then install the SSL

Edit the file

Code:

/var/cpanel/userdata/username/addon-domain.com

and change the IP to a dedicated IP. Also edit the DNS entires for the addon domain and set the New IP there.

Now rebuild the apache configuration files

Code:

/scripts/rebuildhttpdconf

[Total: 0    Average: 0/5]

How to change documentroot in cPanel for primary domain

ssh [email protected]

sudo su – root

Edit the following file:

/var/cpanel/userdata/USER/DOMAIN

Important! If you have an SSL certificate on the account, you may need to edit the following file as well.

/var/cpanel/userdata/USER/DOMAIN_SSL

You should see the file like the following. The areas to edit are in RED.

customlog:

format: combined

target: /usr/local/apache/domlogs/domain.com

format: “\”%{%s}t %I .\\n%{%s}t %O .\””

target: /usr/local/apache/domlogs/domain.com-bytes_log

documentroot: /home/USER/public_html

group: USER

hascgi: 1

homedir: /home/USER

ip: 0.0.0.0

owner: root

phpopenbasedirprotect: 1

port: 80

scriptalias:

path: /home/USER/public_html/cgi-bin

url: /cgi-bin/

serveradmin: [email protected]

serveralias: www.domain.com

servername: domain.com

usecanonicalname: ‘Off’

user: USER

Change the following lines in the file:

documentroot: /home/USER/public_html

path: /home/USER/public_html/cgi-bin

The changes will look like the following:

documentroot: /home/USER/public_html/new_doc_root_dir

path: /home/USER/public_html/new_doc_root_dir/cgi-bin

When finished editing the document root, run the following scripts while logged in as the ROOT user.:

/scripts/rebuildhttpdconf

service httpd graceful

[Total: 0    Average: 0/5]

Dovecot starting error

 

Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /etc/dovecot/sni.conf line 59: ssl_cert: Can’t open file /var/cpanel/ssl/installed/certs/01_webinf_ro_c1633_68425_1463431906_17b38c7a1f52478c8da1879eb6e668d2.crt: No such file or directory

################################################################################################################

Fix:

/scripts/build_mail_sni –rebuild_map_file –rebuild_dovecot_sni_conf

[Total: 1    Average: 1/5]

Cpanel exclude files/folders from backup

Global exclude file

To exclude files or directories from your backups for all user accounts, add those files or directories to the /etc/cpbackup-exclude.conf file.

The backup system excludes the following files and directories for all users’ backups by default:

1
2
3
4
5
6
7
8
9
10
*/.wysiwygPro_*
*/core.[0-9]
.MirrorSearch
.cpan
.cpanel/caches
.cpanel/datastore
.cpcpan
.sqmailattach
access-logs
public_ftp/.ftpquota

Local exclude file

To exclude files or directories from an individual user’s backups, add the files or directories to exclude to the cpbackup-exclude.conf file in the user’s directory, one per line.

If the file does not already exist, you must create it. To do this, run the following command:

touch /home/username/cpbackup-exclude.conf

Notes:

  • In this example, username represents the name of the user who owns the files or directories.
  • If you enter a directory name, the backup system excludes all of the files that are inside the directory.
  • Do not include leading or trailing characters of any kind, such as slashes (/) or periods (.).
  • The global and local exclude files apply to the account backups that you manage in WHM’s Backup section (Home >> Backup) and the Download or Generate a Full Website Backup feature in cPanel’s Backups interface (Home >> Files >> Backups).
  • If you initiate a Home Directory backup in cPanel’s Backups interface (Home >> Files >> Backups), the global and local exclude files do not affect the contents of the backup file.

Via command line:

/scripts/pkgacct username /path/where/it/should/go backup

/scripts/pkgacct username /path/where/it/should/go userbackup

[Total: 0    Average: 0/5]

The Perfect Server – Ubuntu 15.10 (nginx, MySQL, PHP, Postfix, BIND, Dovecot, Pure-FTPD and ISPConfig 3)

1. Preliminary Note

In this tutorial, I will use the hostname server1.example.com with the IP address 192.168.1.100 and the gateway 192.168.1.1 for the network configuration. These settings might differ for you, so you have to replace them where appropriate.  Before proceeding further, you need to have a basic minimal installation of Ubuntu 15.10 as explained in tutorial.

The steps in this tutorial have to be executed as root user, so I will not prepend “sudo” in front of the commands. Either Login as root user to your server before you proceed or run:

sudo su

to become root when you are logged in as a different user on the shell.

The commands to edit files will use the editor “nano”, you can replace it with an editor of your choice. Nano is an easy to use file editor for the shell. If you like to use nano and haven’t installed it yet, run:

apt-get install nano

2. Update Your Linux Installation

Edit /etc/apt/sources.list. Comment out or remove the installation CD from the file and make sure that the universe and multiverserepositories are enabled. It should look like this:

nano /etc/apt/sources.list

#

# deb cdrom:[Ubuntu-Server 15.10 _Wily Werewolf_ - Release amd64 (20151021)]/ wily main restricted

#deb cdrom:[Ubuntu-Server 15.10 _Wily Werewolf_ - Release amd64 (20151021)]/ wily main restricted

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://de.archive.ubuntu.com/ubuntu/ wily main restricted
deb-src http://de.archive.ubuntu.com/ubuntu/ wily main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://de.archive.ubuntu.com/ubuntu/ wily-updates main restricted
deb-src http://de.archive.ubuntu.com/ubuntu/ wily-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://de.archive.ubuntu.com/ubuntu/ wily universe
deb-src http://de.archive.ubuntu.com/ubuntu/ wily universe
deb http://de.archive.ubuntu.com/ubuntu/ wily-updates universe
deb-src http://de.archive.ubuntu.com/ubuntu/ wily-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://de.archive.ubuntu.com/ubuntu/ wily multiverse
deb-src http://de.archive.ubuntu.com/ubuntu/ wily multiverse
deb http://de.archive.ubuntu.com/ubuntu/ wily-updates multiverse
deb-src http://de.archive.ubuntu.com/ubuntu/ wily-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://de.archive.ubuntu.com/ubuntu/ wily-backports main restricted universe multiverse
deb-src http://de.archive.ubuntu.com/ubuntu/ wily-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu wily-security main restricted
deb-src http://security.ubuntu.com/ubuntu wily-security main restricted
deb http://security.ubuntu.com/ubuntu wily-security universe
deb-src http://security.ubuntu.com/ubuntu wily-security universe
deb http://security.ubuntu.com/ubuntu wily-security multiverse
deb-src http://security.ubuntu.com/ubuntu wily-security multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu wily partner
# deb-src http://archive.canonical.com/ubuntu wily partner

Then run:

apt-get update

To update the apt package database and then:

apt-get upgrade

to install the latest updates (if there are any). If you see that a new kernel gets installed as part of the updates, you should reboot the system afterward:

reboot

3. Change the Default Shell

/bin/sh is a symlink to /bin/dash, however we need /bin/bash, not /bin/dash. Therefore we do this:

dpkg-reconfigure dash

Use dash as the default system shell (/bin/sh)? <– No

If you don’t do this, the ISPConfig installation will fail.

 

4. Disable AppArmor

AppArmor is a security extension (similar to SELinux) that should provide extended security. It is not installed by default from onwards 13.10. We will cross check if it is installed. In my opinion you don’t need it to configure a secure system, and it usually causes more problems than advantages (think of it after you have done a week of trouble-shooting because some service wasn’t working as expected, and then you find out that everything was ok, only AppArmor was causing the problem). Therefore, I disable it (this is a must if you want to install ISPConfig later on).

We can disable it like this:

service apparmor stop
update-rc.d -f apparmor remove
apt-get remove apparmor apparmor-utils

5. Synchronize the System Clock

It is a good idea to synchronize the system clock with an NTP (network time protocol) server over the Internet. Simply run

apt-get install ntp ntpdate

and your system time will always be in sync.

 

6. Install Postfix, Dovecot, MariaDB, phpMyAdmin, rkhunter, Binutils

We can install Postfix, Dovecot, MariaDB (as MySQL replacement), rkhunter, and binutils with a single command:

apt-get install postfix postfix-mysql postfix-doc mariadb-client mariadb-server openssl getmail4 rkhunter binutils dovecot-imapd dovecot-pop3d dovecot-mysql dovecot-sieve sudo

MariaDB is a fork of the MySQL database server, developed by the original MySQL developer Monty Widenius. According to tests found on the internet, MariaDB is faster than MySQL and it’s development is going on with more pace, therefore, most Linux Distributions replaced MySQL with MariaDB as default “MySQL alike” database server. In case that you prefer MySQL over MariaDB, replace “mariadb-client mariadb-server” in the above command with “mysql-client mysql-server”.

You will be asked the following questions:

General type of mail configuration: <– Internet Site
System mail name: <– server1.example.com

Next open the TLS/SSL and submission ports in Postfix:

Next open the TLS/SSL and submission ports in Postfix:

nano /etc/postfix/master.cf

Uncomment the submission and smtps sections as follows – add the line -o smtpd_client_restrictions=permit_sasl_authenticated,reject to both sections and leave everything thereafter commented:

[...]
submission inet n       -       -       -       -       smtpd
  -o syslog_name=postfix/submission
  -o smtpd_tls_security_level=encrypt
  -o smtpd_sasl_auth_enable=yes
  -o smtpd_client_restrictions=permit_sasl_authenticated,reject
#  -o smtpd_reject_unlisted_recipient=no
#  -o smtpd_client_restrictions=$mua_client_restrictions
#  -o smtpd_helo_restrictions=$mua_helo_restrictions
#  -o smtpd_sender_restrictions=$mua_sender_restrictions
#  -o smtpd_recipient_restrictions=permit_sasl_authenticated,reject
#  -o milter_macro_daemon_name=ORIGINATING
smtps     inet  n       -       -       -       -       smtpd
  -o syslog_name=postfix/smtps
  -o smtpd_tls_wrappermode=yes
  -o smtpd_sasl_auth_enable=yes
  -o smtpd_client_restrictions=permit_sasl_authenticated,reject
#  -o smtpd_reject_unlisted_recipient=no
#  -o smtpd_client_restrictions=$mua_client_restrictions
#  -o smtpd_helo_restrictions=$mua_helo_restrictions
#  -o smtpd_sender_restrictions=$mua_sender_restrictions
#  -o smtpd_recipient_restrictions=permit_sasl_authenticated,reject
#  -o milter_macro_daemon_name=ORIGINATING
[...]

Restart Postfix afterward:

service postfix restart

We want MariaDB/MySQL to listen on all interfaces, not just localhost. Therefore we edit /etc/mysql/mariadb.conf.d/mysqld.cnf (for MariaDB or /etc/mysql/my.cnf (for MySQL) and comment out the line bind-address = 127.0.0.1:

MariaDB

nano /etc/mysql/mariadb.conf.d/mysqld.cnf

[...]
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address           = 127.0.0.1
[...]

Then we restart MariaDB:

service mysql restart

The systemd service name for MariaDB and MySQL is “mysql”, so the restart command is the same for both database servers.

Now we set a root password in MariaDB. Run:

mysql_secure_installation

You will be asked these questions:

Enter current password for root (enter for none): <– press enter
Set root password? [Y/n] <– y
New password: <– Enter the new MariaDB root password here
Re-enter new password: <– Repeat the password
Remove anonymous users? [Y/n] <– y
Disallow root login remotely? [Y/n] <– y
Reload privilege tables now? [Y/n] <– y

Then run this command to disable the UNIX auth plugin for the root user:

echo “update user set plugin=” where User=’root’;flush privileges;” | mysql –defaults-file=/etc/mysql/debian.cnf mysql

To allow password based authentication from PHPMyAdmin.

MySQL

nano /etc/mysql/my.cnf

[...]
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address           = 127.0.0.1
[...]

Then we restart MySQL:

service mysql restart

The systemd service name for MariaDB and MySQL is “mysql”, so the restart command is the same for both database servers.

For MySQL and MariaDB:

Now check that networking is enabled. Run:

netstat -tap | grep mysql

The output should look like this:

[email protected]:~# netstat -tap | grep mysql
tcp        0      0 *:mysql                 *:*                     LISTEN      8032/mysqld
[email protected]:~#

 

7. Install Amavisd-new, SpamAssassin, And ClamAV

To install amavisd-new, SpamAssassin, and ClamAV, we run

apt-get install amavisd-new spamassassin clamav clamav-daemon zoo unzip bzip2 arj nomarch lzop cabextract apt-listchanges libnet-ldap-perl libauthen-sasl-perl clamav-docs daemon libio-string-perl libio-socket-ssl-perl libnet-ident-perl zip libnet-dns-perl

The ISPConfig 3 setup uses amavisd-new which loads the SpamAssassin filter library internally, so we can stop SpamAssassin to free up RAM:

service spamassassin stop
update-rc.d -f spamassassin remove

 To update the ClamAV antivirus signatures and starte the Clamd service. The update process can take some time, don’t interrupt it.

freshclam
service clamav-daemon start

[Total: 0    Average: 0/5]

Activare “My outgoing server (SMTP) requires authentication.” in functie de clientul de email utilizat

Microsoft Outlook Express and Outlook 2000

1.) Click Tools

2.) Click Accounts

3.) Click the Mail tab

4.) Double-click on the BlueTie account

5.) Verify that the email address is entered in all lowercase letters (General Tab)

6.) Click the Servers tab.

7.) Verify that “Server Requires Authentication” is checked

8.) Click the Settings button and verify that “Login using same settings as my incoming mail server” is selected

9.) Click ‘Apply’ (if available), then ‘OK’, and then ‘Close’.

Microsoft Outlook 2002 (XP) and 2003

1.) Click Tools

2.) Click Email Accounts

3.) Click View or Change Existing Email Accounts

4.) Click Next

5.) Double-click on the BlueTie account

6.) Click on More Settings and then click the Outgoing Server tab.

7.) Verify that “SMTP server requires authentication” is checked and “Use same settings as my incoming mail server is selected”

8.) Click ‘OK’, then ‘Next’, and then ‘Finish’

9.) Click send / receive to check for errors

Mozilla Thunderbird

1.) Click Tools

2.) Click Account Settings

3.) Click Outgoing Server from the left

4.) Select the BlueTie outgoing server

5.) Click the Edit button

6.) Verify that Use Name and Password is checked

7.) Verify the username is entered correctly

Apple Mail

1.) Click Mail

2.) Click Preferences

3.) Click the BlueTie account

4.) Click the Account Information button

5.) Click the Server Settings button

6.) Verify that Authentication is set to Password

7.) Verify that username and password are entered correctly

Microsoft Entourage

1.) Click Tools

2.) Click Accounts

3.) Click Mail

4.) Double-click on the BlueTie account

5.) Click Account Settings

6.) Click the Advanced Sending Options button

7.) Verify that “SMTP server requires authentication” is checked and “Use same settings as receiving mail server” is selected

8.) Close the window by clicking the box in upper-left corner

Qualcomm Eudora

1.) Click the Eudora menu

2.) Click Preferences

3.) Click the Checking Mail icon

4.) Verify that ‘Authentication’ is set to Passwords

5.) Click the Sending Mail icon

6.) Verify that Allow Authorization is checked

[Total: 0    Average: 0/5]