Hello,
Please note, for fastest response, please contact us:
http://www.directadmin.com/support.html
Note that I've seen a few systems recently where admin's have manually changed the server IP to becomed "owned". This causes many problems.. we don't recommend modifying DA data files manually.
In any case, on the assumption your Server IP is
1.2.3.4:
1) Make sure that a virtualhost for
1.2.3.4 does *not* exist in /etc/proftpd.vhosts.conf. If there is one (likely) then delete the entry from the file, and restart proftpd.
2) Edit:
/usr/local/directadmin/data/admin/ips/
1.2.3.4
Set the following values to:
Code:
netmask=[B]255.255.255.0[/B]
ns=[B]ns1.ifyouhaveitset.com[/B]
reseller=
status=server
value=[B]1[/B]
where the
bold items should be set to something appropriate for your system. The netmask should self explanitory. The ns value can be blank if you want, or to an ns value.. it's mainly cosmetic. The value is the number of users on that IP.. if it was owned, this will likely be 1.
3) From there, check:
/usr/local/directadmin/data/users/
username/ftp.passwd
ftp accounts for the server IP should be in /etc/proftpd.passwd. The ftp.passwd file is for owned IPs accounts only. But since the server IP was manually changed, that generally causes the problem. Also note that the username format in ftp.passwd can be slightly different (the @domain.com is missing for the default domain, so needs to be added before you dump the ftp passwd into /etc/proftpd.passwd)
If you've followed a guide to change the server IP to an owned one, please let me know where it is, so that I can make a note about why it shouldn't be followed. There have been a few reports of this recently (but DA hasn't been changed recently), hence I'm suspecting people following a similar guide which is causing the issue.
John