Tips for fixing common problems….-The ip of this machine () does not match the ip in the license file

Tips for fixing common problems….-The ip of this machine () does not match the ip in the license file–If you get the message: The ip of this machine () does not match the ip in the license file

machine , when you trying to start DirectAdmin (or ( instead of ()) then the ethernet_dev setting is in your directadmin.conf files isn’t setup correctly.



if you want to see which device name your IP is on.  Common devices names/formats are: eth0, eth0:1, eth1, venet0:0, etc..

Please Note that you can specify the sub-device name to get different IPs.

Once you know the device name, edit /usr/local/directadmin/conf/directadmin.conf
Change (or add) the setting:


where you would replace eth0 with the name of the Ethernet device you should be using.

Starting sshd: /etc/ssh/sshd_config line 371: too many allow users

If there you get the following error when you are trying to start sshd:

Starting sshd: /etc/ssh/sshd_config line 371: too many allow users

that means that there are too many “AllowUsers” lines in the file.

What you can do then, is remove *all* AllowUsers lines from the /etc/ssh/sshd_config, edit /usr/local/directadmin/conf/directadmin.conf.


Save/exit, restart DirectAdmin.


touch /etc/ssh/sshd_config.plecibo

and then you can  just double check one more time that there are *no* AllowUsers lines in your /etc/ssh/sshd_conf file.

Try Restart sshd:

What this will do is have DA add/remove any users to a file that is a plecibo, which does not have any effect.
As long as there are no AllowUsers lines in the main /etc/ssh/sshd_config file, then all users are allowing to connect.

If there one or more AllowUsers lines are present in the main sshd_config file, then only those, hence the importance to not have any show up.

Make fully sure you have restarted DA before leaving the system alone, else you migh allow ssh to 1 user, thus blocking root or any other user ssh access.

Please Note that the /etc/ssh/sshd_config file that can be edited from within the Admin Level -> File Editor, so do not fret if you mess it up.  You can fix it through DA.

How to debug a segfault within DirectAdmin

If there you get a message “A segmentation fault has occurred”, this is a program error generally due to either incompatible binaries for your OS, or incorrect handling of data.

The first thing you should do is go to:
Admin Level -> Licenses/Updates
and check to ensure that the OS the binaries are compiling for match the OS you are using.

To debug it, the first thing you should do then  is to check your:
to see what the problem was.  There will be a segfault message with a program location.

To further debug the error, mainly for reporting to us, you would need to install “gdb” to debug the binary.
You will also need to be able to reliably dulicate the segfault.

1) Login to DA normally, and go to the page such that you are one click away from generating the segfault.

2) Login to ssh as root and type:

cd /usr/local/directadmin
killall -9 directadmin
gdb directadmin
run s

This will be loaded up a single process non-forked copy of DirectAdmin.  It only gets 1 call to it, then it will be quitting.

3) Go back to your “1 click away” browser, and submit the form to generate the segfault.  You will probably not get any output which is fine.

4) Back to ssh again, gdb should have been pointed out that the program sefaulted.  Type bt full

to dump the memory for the programs location.  Copy/paste that entire output and send it to us.

Leave a Reply

Your email address will not be published. Required fields are marked *