What's new

Welcome to Ruzgar.com

Join us now to get access to all our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, and so, so much more. It's also quick and totally free, so what are you waiting for?

Ask question

Ask questions and get answers from our community

Answer

Answer questions and become an expert on your topic

Contact us

Contact the site administrator directly.

Groups

Just like Facebook join them and enjoy.

Directadmin Connection Problem

ruzgar

Administrator
Staff member
Joined
Oct 3, 2021
Messages
37
Reaction score
0
Points
6
From time to time we make updates or some setting changes in directadmin.

Sometimes, even though we update, the update warnings do not go away and we feel the need to restart the server.

In this case, you may have problems accessing sites or directadmin after the server restarts.

To understand why this is happening, first connect to your server via SSH as root and understand the error messages.

Code:
sudo systemctl status directadmin.service
Code:
sudo tail -f /var/log/httpd/error_log
Code:
sudo tail -f /var/log/directadmin/system.log

You don't need to run the codes one after the other. Each code will return separate results and will help you find what the problem is.
You can request support by typing the error messages you receive here, or you can search the web and try the suggested solutions.

Reconfiguring and updating directadmin may solve your problem. For this, you can paste the following codes into the same main SSH:
This process will take about 10 minutes.
Code:
cd /usr/local/directadmin/custombuild
./build update
./build all d
./build rewrite_confs

At the end of the update, you can restart your server.

If the system still hasn't come up, type
Code:
/usr/local/directadmin/directadmin
to see the results. The direct admin can link you to the help. You can follow that link.

In General, the problems connecting to DirectAdmin will be solved with the following codes, but we recommend that you try the above methods and fully understand the subject.
Code:
/sbin/service iptables stop
/sbin/chkconfig iptables off
[ICODE]

If that doesn't work either, try to understand the problem with [CODE]tail /var/log/directadmin/error.log
.

The problem may be incorrect Ethernet settings. You can check the ethernet_dev settings at /usr/local/directadmin/conf/directadmin.conf. You can see which device name your server is connecting to by typing /sbin/ifconfig into ssh. After checking, check if the setting of
Code:
ethernet_dev=[B]eth0[/B]
at /usr/local/directadmin/conf/directadmin.conf is correct. Correct it if it's wrong.

Incorrect or non-existent licenses or identifying your license to the wrong IP can also cause Directadmin connection problems. Perform control from the directadmin panel.

The server may have added your IP address to the blacklist due to too many false login attempts and incorrect firewall settings. In this case, you will not be able to access the server. Check if the ip is located at /usr/local/directadmin/data/admin/ip_blacklist by learning about you. In order not to experience this situation again, enter a value higher than 10 in the Brute Force Login Dedection section.

If you couldn't solve the problem, you can try to start directadmin manually. The code to start directadmin manually is as follows:

Code:
cd /usr/local/directadmin
./directadmin b200

You can press CTRL (Command for Macs) + C to stop the ongoing SSH command.

If you are using CENTOS 7, you can turn off the firewall with the following codes.

Code:
systemctl disable firewalld
systemctl stop firewalld

If you do not know whether port 2222 is open or if you want to open port 2222 when the firewall is open, you can use the code below.
Code:
firewall-cmd --permanent --zone=public --add-port=2222/tcp
 
shape1
shape2
shape3
shape4
shape5
shape6
Top