Unable to Validate Destination - SSH

JetBackup uses public-key authentication to connect to and validate your SSH Destination. This needs to be configured and enabled on your destination server so that it does not prompt for a password when authenticating through a public-key. You can verify public-key authentication is enabled by attempting to ssh from your jetbackup server to your destination server while using the ssh key.

ssh -p XXXX user@hostname -i /path/to/public/key

If the above command prompts a password input, then public-key authentication is not enabled.

Additional troubleshooting steps include:

  • Specifying the absolute path of the backup directory for your ssh user (/home/sshuser/backuppath) when adding the destination.
  • Check that the user is able to access the Backup Directory (chmod 0755 /home/sshuser/backuppath).
  • Verify that the user you're connecting to has permission to access SSH in your Destination.
  • Make sure the SELinux is disabled in the destination server. SELinux in “enforcing” mode on a destination server may cause connection issues with JetBackup. Please disable SELinux and reboot the backup server in order to make the changes take effect and then try to add the ssh destination again.

If you continue to run into the same error, please open a ticket with support at support@jetapps.com.

  • 0 Bu dökümanı faydalı bulan kullanıcılar:
Bu cevap yeterince yardımcı oldu mu?

İlgili diğer dökümanlar

Backblaze/S3 - Excessive Storage Use by JB5

We have received some reports of excessive Storage use by JetBackup 5 in the S3 Bucket. For...

My S3 Vendor is not included in the supported list on JetBackup 5?

You can find a small list of S3 Vendors that are supported with the new S3 Compatible plugin at...

S3 Common Issues / Failed to upload file

S3 destinations can often hit request limits when destinations are configured with high...

S3 Compatible - "Error: The key 'XXXX' is not valid (InvalidAccessKeyId)"

Here are some helpful tips to troubleshoot the error "Error: The key 'XXXX' is not valid...

SSH Destination hitting "SSH Multiplexing Limit"

When receiving an error like the following: [ERROR] Failed transferring account "accountName"...