All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Directadmin issue
Hello,
I have some problem with DA after update DA.
The ip of this machine () does not match the ip in the license file.
Check the value of your ethernet_dev=eth0 setting in your /usr/local/directadmin/conf/directadmin.conf file and the output of /sbin/ifconfig
My ifconfig:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet IP netmask 255.255.255.255 broadcast 0.0.0.0
inet6 IP prefixlen 64 scopeid 0x0
inet6 IP prefixlen 64 scopeid 0x20
ether 96:00:00:66:21:5b txqueuelen 1000 (Ethernet)
RX packets 4185 bytes 326491 (318.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4944 bytes 407465 (397.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 166 bytes 27282 (26.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 166 bytes 27282 (26.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Any help. Thanks
Comments
Did your IP change? Does the IP in ifconfig show licensed on http://license.directadmin.com/ ?
Not Changed ip address.
Check if the outgoing IP is still the same:
dig +short myip.opendns.com @resolver1.opendns.comThis is not working. But this dig -4 TXT +short o-o.myaddr.l.google.com @ns1.google.com return the correct ip. Not changed
less /var/log/directadmin/system.log
2020:09:23-00:18:40: Clean shutdown successful
2020:09:23-00:19:01: named restarted
2020:09:23-00:19:01: directadmin started
2020:09:23-00:47:47: signal TERM received. Waiting for children to exit
2020:09:23-00:47:48: Clean shutdown successful
2020:09:23-00:49:02: named restarted
2020:09:23-00:49:02: directadmin started
2020:09:23-05:01:02: Running Backup: type=admin owner=admin id=1
2020:09:23-16:18:37: signal TERM received. Waiting for children to exit
2020:09:23-16:18:37: Clean shutdown successful
2020:09:23-16:19:01: named restarted
2020:09:23-16:19:01: directadmin started
less /var/log/directadmin/errortaskq.log
2020:09:22-21:23:02: Error getting user 'admin' domain config file for domain (null)
2020:09:22-22:35:03: service directadmin wasn't running, starting directadmin
2020:09:22-23:03:02: service directadmin wasn't running, starting directadmin
2020:09:22-23:03:32: Error starting service directadmin : uid 0 gid 0 : /usr/bin/systemctl start directadmin.service >/dev/null 2>/dev/null : returned 1
2020:09:22-23:03:37: service directadmin didn't start, re-starting directadmin
2020:09:23-00:05:01: service directadmin wasn't running, starting directadmin
2020:09:23-00:05:07: service directadmin didn't start, re-starting directadmin
2020:09:23-00:06:01: service directadmin wasn't running, starting directadmin
2020:09:23-00:06:06: service directadmin didn't start, re-starting directadmin
2020:09:23-00:07:01: service directadmin wasn't running, starting directadmin
2020:09:23-00:07:06: service directadmin didn't start, re-starting directadmin
2020:09:23-00:08:01: service directadmin wasn't running, starting directadmin
2020:09:23-00:08:06: service directadmin didn't start, re-starting directadmin
2020:09:23-00:09:01: service directadmin wasn't running, starting directadmin
2020:09:23-00:19:01: service directadmin wasn't running, starting directadmin
2020:09:23-00:49:02: service directadmin wasn't running, starting directadmin
2020:09:23-16:19:01: service directadmin wasn't running, starting directadmin
(END)
Is this a vps?
Yes
https://help.directadmin.com/item.php?id=30
If this doesn’t fix it, try reaching out to your license vendor (Host) or if you got it from DA directly, reach out to them.
Why not contact the support since they will normally need to login into the server to troubleshoot this and fix it instead of wasting your time here ?
but don't reach out to DA if its a personal or trial license - use their community support
Feel free to open a guest ticket and mention that I promised support on this. Would be interested to see what the issue is. Please don't use e-mail; our support address is flooded by shared hosting customers who think we are their host
The end is clearly nigh.
Technically.......
This probably means Cpanel has the same issue.
It would be interesting to know how they thought that DA is their hosting provider.
I mean I wouldn't mind
i have seen lots of people ask for Cpanel/DirectAdmin support instead of direct contact to main providers. they provide supports.
I dont have support from provider.
Thanks,
Need to mention that error is related to Skin. After resarch I restore Enhanced skin, but not evolution (default one before update DA). So, error log was showing wrong error type - license issue. And it waste my time searching about solution related to license. Maybe its known issue when system lost skin or after update it gone and you get error or login blank page. If you already loged in error type is error document not found.