Virtualmin backup fails with: Uploading archive to FTP server ... Connection refused

I get this:

Backup failed! See the progress output above for the reason why. Total backup time was 00 minutes, 04 seconds.

Virtual servers that failed :
   name.com
Sent by Virtualmin at: https://myserver

Testing backup destination /backups/mytest/24/01/25 on FTP server myname.myserver.com ..
.. done

Creating backup for virtual server name.com ..
   Copying virtual server configuration ..
   .. done

   Backing up Cron jobs ..
   .. none defined.

   Copying records in DNS domain ..
   .. done

   Saving mail aliases ..
   .. done

   Saving mail and FTP users ..
   .. done

   Backing up mail and FTP user Cron jobs ..
   .. none to backup

   Copying Apache virtual host configuration ..
   .. done

   Copying Apache log files ..
   .. done

   Copying Logrotate configuration ..
   .. done

   Dumping PostgresSQL database name_com ..
   .. done

   Creating TAR file of home directory ..
   .. done

   Uploading archive to FTP server myname.myserver.com ..
   .. upload failed! Failed to connect to 38.43.14.104:59900 : Connection refused

.. completed in 4 seconds

And if I purposely put in incorrect details I get this:

Backup failed! See the progress output above for the reason why. Total backup time was 00 minutes, 00 seconds.

Virtual servers that failed :
   name.com
Sent by Virtualmin at: https://myname

Testing backup destination /backups/mytest/24/01/25 on FTP server myname.myserver-com ..
Failed to connect to FTP server : PASS **************** failed : Login incorrect.

So it looks like when the credentials are correct (as per the first example above) it passes the Vritualmin test… but why does it then go on to fail and say connection refused? Seems very odd :confused:

I get the same with SSH - test works but actual transfer fails:

Backup failed! See the progress output above for the reason why. Total backup time was 00 minutes, 04 seconds.

Virtual servers that failed :
   name
Sent by Virtualmin at: https://mysite

Testing backup destination /backups/name2/24/01/25 on SSH server myname.my-backup.com ..
.. done

Creating backup for virtual server name ..
   Copying virtual server configuration ..
   .. done

   Backing up Cron jobs ..
   .. none defined.

   Copying records in DNS domain ..
   .. done

   Saving mail aliases ..
   .. done

   Saving mail and FTP users ..
   .. done

   Backing up mail and FTP user Cron jobs ..
   .. none to backup

   Copying Apache virtual host configuration ..
   .. done

   Copying Apache log files ..
   .. done

   Copying Logrotate configuration ..
   .. done

   Dumping MariaDB database name_com ..
   .. done

   Dumping PostgresSQL database name_com ..
   .. done

   Creating TAR file of home directory ..
   .. done

   Uploading archive to SSH server myname.my-backup.com ..
   .. upload failed! myname@myname.my-backup.com's password:
/backups/name2/24/01/25: No such file or directory

Check the log on the receiving end. It should give a reason. The name you gave backup name looks wrong. Forward slashes are directory names, like the back name have is like FourHour-25-01-2024, the date is added, in the form I use FourHour-%d-%m-%Y.

1 Like

Good catch - though I am still getting the same (initial test works but then when it tries to upload it says connection refused: .. upload failed! Failed to connect to 38.43.14.104:59900 : Connection refused

This is what I have for the destination - does it look ok? /backups/mysitename-%d-%m-%Y

Where will the logs be?

The ftp server should have logs, where they are depends on the server configuration so I can’t really tell you. The port 59900

has me confused, not sure why it would have that. FTP port is normally 21.

yep, that should work

1 Like

Yeah that is odd - I’ve not specified 59900 anywhere. So it sounds like it could be a bug then? The test goes through fine but the uploading doesn’t.

Edit: I think I know what it is! My firewall is blocking port 59900!

Adding port 59900 to the firewall has fixed it :smiley:

I also used this format instead ‘/backups/mysitename/-%d-%m-%Y’ as it keeps all the domains backups in separate folders.

Thanks for your help Stefan!

1 Like

I’ve never backup with ftp, strange it would use that port. Glad its fixed.
P.S. Did you use example.com:21 in the ftp server section?

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.