Restore through FTP - No Data to Show

[area62]

When i try to restore a backup from a FTP server, DirectAdmin is saying "No Data to Show".

When i connect with FileZilla to the FTP server i see some .tar.gz files of the users i selected to backup.

 

[scsi]

I would just manually move the file over then.

 

[area62]

That would take a while, DirectAdmin must be able to find the backups on the FTP server else the backup option to FTP is useless.

 

[DirectAdmin Support]

Hello,

1) Ensure the path is correct. Sometimes adding or removing a trailing / character can make a difference. The path should be relative to your login home, not the disk home.

2) The listing script is at:

/usr/local/directadmin/scripts/ftp_list.php

3) I'd recommend manually testing the /usr/bin/ncftpls binary, with it's options, to see if it works at that level, eg:

/usr/bin/ncftpls -l -f /root/test.config -P 21 -t 10 "ftp://1.2.3.4/path"

where you'd create /root/test.config with the code:

host 1.2.3.4
user ftp_username
pass ftp_password

and see what that gives you.

John

 

[area62]

1) trailing / makes no difference
2) checked the file and modified it to make it work (see below)
3) test runs fine, it returns the complete listing

I modified the ftp_list.php file and now it shows the backup files.

What i did:

cat $DUMP | grep -v -e '^d' | awk '{ print $9; }'

Replaced with

cat $DUMP | grep -v -e '^d' | awk '{ print $4; }'

So i print the 4th parameter instead of the 9th

But after the next update my modification is gone i guess?

 

[donkeyKICK]

Thanks for the fix, but I am concerned that a DA update will undo this.

 

[DirectAdmin Support]

Hello,

Copy the script:

/usr/local/directadmin/scripts/ftp_list.php

into

/usr/local/directadmin/scripts/custom/ftp_list.php

and edit the custom version.
The custom version will be safe from update overwrites.

John

 

[donkeyKICK]

When I tried that John, I got:

Unable to read %s/usr/local/directadmin/scripts/custom/ftp_list.php
FTP information invalid.
​

 

[DirectAdmin Support]

That just means that the diradmin user cannot read it.
Chmod it to 644 and/or chown to diradmin:diradmin.

John

 

[donkeyKICK]

Sure 'nuff, you're right. Working! I've been having this trouble for a very long time.