Aza
Verified User
After about a year our DirectAdmin "lifetime" license expired.
DirectAdmin says the license has not expired, but that their logs indicate that our server is no longer using the main server IP on record when validating the DirectAdmin license.
SSHing in to the main CentOS 6.3 server IP of record and running "/sbin/ifconfig" confirms that eth0 is in fact set to the main server IP of record.
A check of /usr/local/directadmin/conf/directadmin.conf shows "ethernet_dev=eth0"
Yet for some reason DirectAdmin is using eth0:4 when calling home to verify our license. The verification fails because the communication is not from the registered eth0 main server IP on record.
We've been without a control panel for three days and DirectAdmin's support has been positively glacial. Replies take a frustrating 24 hours.
Do you have any idea about what might be causing DirectAdmin to elect to use eth0:4 instead of eth0 when calling home to validate our license?
Regards.
Aza D. Oberman
DirectAdmin says the license has not expired, but that their logs indicate that our server is no longer using the main server IP on record when validating the DirectAdmin license.
SSHing in to the main CentOS 6.3 server IP of record and running "/sbin/ifconfig" confirms that eth0 is in fact set to the main server IP of record.
A check of /usr/local/directadmin/conf/directadmin.conf shows "ethernet_dev=eth0"
Yet for some reason DirectAdmin is using eth0:4 when calling home to verify our license. The verification fails because the communication is not from the registered eth0 main server IP on record.
We've been without a control panel for three days and DirectAdmin's support has been positively glacial. Replies take a frustrating 24 hours.
Do you have any idea about what might be causing DirectAdmin to elect to use eth0:4 instead of eth0 when calling home to validate our license?
Regards.
Aza D. Oberman