Troubleshooting Tip: FortiGate configuration backup to FTP server returns error message

[nweckel]

Description	This article provides troubleshooting steps for when the backup of a configuration file from a FortiGate to an FTP server is unsuccessful. The CLI output will return an error like the following: Connect to ftp server xxx.xxx.xxx.xxx:yy ... Please wait... Send config file to ftp server via vdom root failed. Command fail. Return code 10
Scope	Backup of a configuration file from all FortiOS versions to an FTP server.
Solution	Verify that the command syntax is correct. The correct syntax is as follows: execute backup config ftp <backup_filename> <ftp_server>[<:ftp_port>] [<user_name>] [<password>] [<backup_password>] The following information regarding the back up of the configuration in FortiOS using the CLI can be found in the FortiGate administration guide Run a packet capture using the following CLI commands: diagnose sniffer packet any "host <ftp_server> and port <ftp_port>" 6 0 l Packet capture can also be done via the GUI under Network -> Diagnostics, as described in the FortiGate administration guide In the packet capture, verify that the TCP handshake between the FortiGate and the FTP server is successful. If it is unsuccessful, check connectivity between the FortiGate and the FTP server. If it is successful, the FTP server will return an error message with the reason it closes the connection. Common error messages include: 530 Authentication failed: incorrect username or password. 530 Valid hostname is expected: credentials should follow format <host_header>|<user_name> or host header is misconfigured on the FTP server. 550 no such file or directory: wrong path on the FTP filesystem. 550 Permission Denied: The user does not have written permission in the directory. Example Packet Captures: Invalid FTP  Password: FTP Upload Denied: