Issues pertaining to the installation of DirectAdmin and it’s included services. Cannot use SSH with old system accounts after Installation

Now For all SSH accounts that created with DirectAdmin, it adds the “AllowUsers” option to the /etc/ssh/sshd_config file.  When the DirectAdmin is installed, it will add “root” and “admin” to that file under the AllowUsers option.  Any other users for whom have had SSH account on the system will also require to be add to that file in order to access the server via SSH.

*IMPORTANT:

For those systems who require the use of “su” to access the root account, but do not use “admin” to do it, that usename *must* be add to the /etc/ssh/sshd_config before logging out or else they will not be able to login and turn will not be able to su to root any longer.

This is not as relevant for RedHat systems, because the default is to enable root login, but for most FreeBSD systems, su is requires, and the starting use *must* be in the wheel group, which a newly creating “admin” would not be.

 

checking how to run the C++ preprocessor… /lib/cpp

If you encounter this error message, this would imply that you do not have g++ installing:

*** The make has failed, do you want to try to make again? (y,n):

The gcc-c++ rpm and all it’s dependancies are requires to resolve the issue.
Some dependancies inclue:
libstdc++-devel
libstdc++

Please do run the following on CentOS/RHEL/CloudLinux systems:

yum -y install gcc-c++

Debian/Ubuntu:

apt-get -y install g++

FreeBSD:

pkg install gcc

How to setup the Mail System

One common problem people have with, is an incorrect setup mail system.  Here is a list of rules that must be follow:

1) hostname must not match in any domain that is being use on the system. For Example, if you have a domain that  call domain.com and you want to receive mail on user@domain.com, you must *not* tune your host-name to domain.com.  We are recommending you for using server.domain.com instead.

 You must make sure that you add the A record for server.domain.com so that it resolves.

2) The hostname must be in the /etc/virtual/domains file.

3) The hostname must *not* be in the /etc/virtual/domainowners file.

4) The hostname must resolve.  If not, add the requiring A records to the dns zone such that it does.

5) The directory /etc/virtual/hostname must exist.. (eg: /etc/virtual/server.domain.com).  It must not contain any of files.

6) Any domains that you want to use for the email (eg: domain.com) must be in both of the /etc/virtual/domains file and the /etc/virtual/domainowners file.   The directory /etc/virtual/domain.com must then exist and the files /etc/virtual/domain.com/passwd and /etc/virtual/domain.com/aliases exist.

7) File permissions for virtual pop inboxes should be (not applicable with Dovecot/Maildir):

/var/spool/virtual/domain.com   770 username:mail
/var/spool/virtual/domain.com/*   660 username:mail

8) Ensure your host-name does not contain any upper case letters.

9) Make sure that your main server IP has a reverse lookup on it.