FTP Restore Directory Listing Issue

blaszlo

Verified User
Joined
Jun 9, 2008
Messages
116
Hey guys,

I have several different Admin level backups setup to backup users every night and upload via FTP to another server. The backups are working great and just as I want, but the restore function does not.

When I got to the Restore screen and click Update Files, it does not pull a directory listing. Just to state the obvious, the username/password, host IP and remote path are the exact same as the ones used to do the backups.

Any ideas?
 

Attachments

  • Screenshot.jpg
    Screenshot.jpg
    91.1 KB · Views: 87
Be sure the remote path is correct and that you are not using capitals in the directory structure where there are no capitals.
 
the H in "Host" is upper-case. Just to check, I have tried it with the remote path filled in, empty, uppercase and lowercase.

Again, these settings are the same for the backup as it is for the restore, and the backups work perfectly. Using the same settings I can connect to the FTP site with Filezilla and get a perfect Dir listing.

Very confused.
 
You clicked that update files button right?

If you did then I dont know... check the logs in /var/log/directadmin to see if you can find any information... I have never tried this feature before.
 
When I got to the Restore screen and clicked Update Files, it does not pull a directory listing

In /var/log/directadmin/2011-Jun-30.log I have the following errors that don't seem very helpful. There is nothing other to report int he other logs in this directory

30/06/2011:14:21:58 192.168.80.180 BAD REQUEST unknown
30/06/2011:14:22:00 192.168.80.180 BAD REQUEST unknown
30/06/2011:14:22:00 192.168.80.180 BAD REQUEST unknown

Not sure where to go from here...
 
Are you restoring to a new server, where the user doesn't exist? As recently as two nights ago (using 3.8.4) that works for me.

If you're restoring to the same server then check permissions and owneships of everything in the directories with the problem. Though based on the error message this doesn't seem to be the likely cause, it's worth checking.

Jeff
 
Back
Top