ssh -vvv <backup_user>@<SFTP_IP>)/var/log/vmware/applmgmt/applmgmt.log):YYYY-MM-Date [3154]INFO:plugins.SftpStorageIOLib:Executing command to get remote root: ssh -q -p 22 -i /root/.ssh/id_rsa -o UserKnownHostsFile=/root/.ssh/br_temp_known_hosts 'backup_user@sftp_ip' echo ~2025-06-19T04:15:16 AM UTC [3154]INFO:plugins.SftpStorageIOLib:Authorizing localhost with command sshpass -f /tmp/tmpsnksqb9kssh-copy-id -i /root/.ssh/id_rsa.pub -p 22 -o UserKnownHostsFile=/root/.ssh/br_temp_known_hosts backup_user@sftp_ipYYYY-MM-Date [3154]ERROR:plugins.SftpStorageIOLib:Failed to authorize local host with command: sshpass -f /tmp/tmpsnksqb9k ssh-copy-id -i /root/.ssh/id_rsa.pub -p 22 -o UserKnownHostsFile=/root/.ssh/br_temp_known_hosts backup_user@sftp_ip. Will proceed with backup through curlYYYY-MM-Date [3154]INFO:plugins.SftpStorageIOLib:Executing command to get remote root: ssh -q -p 22 -i /root/.ssh/id_rsa -o UserKnownHostsFile=/root/.ssh/br_temp_known_hosts 'backup_user@sftp_ip' echo ~YYYY-MM-Date [3154]DEBUG:plugins.SftpStorageIOLib:Passwordless ssh tunnel is not working, falling back to CURLYYYY-MM-Date [3154]ERROR:plugins.FtpStorageIOLib:sftp cmd failed. RC: 22, Err: curl: (22) The requested URL returned error: 502, Cmd: ['/usr/bin/curl', '--fail', '-u', 'BACKUP_USER:****', '--connect-timeout', '120', '--ssl-reqd', '-k', '--proxy','http://PROXY_IP:8080/', '--proxytunnel', '--silent', '--show-error', '--list-only', 'sftp://SFTP_IP:22/data/vcsa/']This issue is encountered when the vCenter Server tries to (unsuccessfully) establish the SSH connection with the SFTP backup server using a configured proxy.
To solve this issue, add the FQDN and the IP address of the SFTP backup server to the NO_PROXY rule in the proxy configuration of the vCenter Server Appliance:
# cp /etc/sysconfig/proxy /etc/sysconfig/proxy.bak# vi /etc/sysconfig/proxyExample:
NO_PROXY="localhost, 127.0.0.1, <SFTP_IP>, <SFTP_FQDN>"# service-control -- stop --all && service-control --start --allI some situations a service restart might not be sufficient to apply the change. Should the issue persist past the restart, please attempt to reboot the complete VCSA.