Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Clarification on syntax of FTP path field for scheduled backups?

Looking at the documentation I expected the path field to be completed in the format /path/to/ftpfolder, with the server IP and login credentials being provided separately in the configuration window. Trying that way isn't accepted as "path cannot begin with / or \".

OK. I tried path/to/ftpfolder which ran though failed to complete successfully.

OK. Can I contact the FTP server from the XG, yup - Ping response fine.

OK. Can I connect and write to /path/to/ftpfolder from a client machine, using the same credentials and on the same VLAN the XG is on, yup - file transferred.

OK. Try FTP://<serverIP>/path/to/ftpfolder:21 - nope, invalid characters in path field again.

Has anyone managed to do this successfully? If so, how did you format the path string in the configuration window?



This thread was automatically locked due to age.
  • Hey Daniel,

    Would you be able to send a quick screenshot of how you configured the Backup/FTP settings you have?

    So when you enter in path/to/ftpfolder/ you can save, but when actually completing the backup is not successful - is that correct?
  • Hi,

    Thanks for getting back to me.

    The backup configuration screen and error message is;

    The server is reachable.....

    And other tests for FTP for the same user to the same location came up as follows;

    The sending end....

    ..... and the receiving end - the folder I'm trying to backup to.

    I though the FTP path on the XG might need to start with a "/" but that's not allowed, I also tried to send to the default ftpaccess user's home folder on the target server but that didn't work either.

    I appreciate your help, let me know if you need anything else. 

  • Hi Daniel,

    I was able to test and success an FTP backup on my MAC. After I enabled FTP server on Mac, I was able to send configuration to a Folder on Desktop. See attachments.

    Luk

  • Thanks Luk,

    Seems clear the problem is somewhere in the backup infrastructure then, not the XG.

    I know where to focus my efforts now, much appreciated.
  • Luk, try as I might I can't get this to work at all. It shouldn't be this hard! I have created a Windows FTP server, which again I have verified working when writing files from other machines.

    I have checked the ftpproxy.log  from the advanced shell (per this) on the XG though that only contains service status messages - I want to check the FTP requests the XG is making and the responses (if any) it is getting as I'm starting to wonder if they're even getting off the XG or if it's a routing issue.

    Which log should I be looking into please?

  • Daniel,
    connect to XG using SSH then option 5 and option 3. Move to folder /var/tslog and have a look at this 2 files:

    validationError.log
    tomcat.log (much better)

    Luk
  • Luk,

    Last configuration on XG;

    Returned tailed validationError.log and tomcat.log seem to suggest at IPv4 validation error and/ or an attempt to write to local host. Would you mind taking a look please?

  • Daniel,

    could you try to backup to 192.168.1.x ip address? For example 1.102 host? Run an FTP server on your Windows Machine or enable FTP server on MAC.

    Luk
  • Thanks Luk, I'll do that later and let you know.

    Another thought, I can open a connection from the XG to the FTP server via telnet without any issues - 192.168.1.2 is the LAN default gateway for all VLANs, set via static route on the XG;

    If you let me have a script to manually kick off the backup from the CLI I can open another shell session a give it whirl?

  • Daniel,

    XG stores configuration inside folder /var/conf/backupdata.
    You can download configuration to ftpserver using command:
    ftpput "ftpserverip" -v -u "username" -p "password" filename

    Try and let's see what problem you have.

    Luk