Deployment issues

This article covers issues in transfer actions: SSH, SFTP, FTP/FTPS, rsync, and other that use the SSH protocol to connect.

By issues, we mean that:

  • the action fails
  • the action test doesn't work
  • browse path doesn't work

Example errors include:

# Failed to get operation result within specified timeout: 60000
# Connection timed out
# Server response: DefaultAuthFuture[ssh-connection]: Failed (IOException) to execute: Connection reset by peer
# Server response: java.net.SocketTimeoutException: connect timed out
# RequestError: connect ETIMEDOUT

Solution

In 9 out of 10 cases the cause of errors are our deployment IPs being blocked on the user side, either in full or in part.

To solve this, you need to whitelist Buddy's deployment IPs on your server / firewall / AWS security group or any other security system employed by user's hosting.

If you are 100% sure that all IPs have been whitelisted and the problem is still occurring, the best shot is to access the server and check the logs for errors about dropped connections from our IPs. Depending on the action type, the logs you are after will most likely concern SSH and FTP protocols, firewall logs, or access logs from your hosting provider. Then, proceed with the solutions below.

In case of hosting services, a much less probable (yet still possible) is a setting that blocks traffic from other countries.

Other user cases

I. Deployment in progress suddenly fails

In this case, a deployment that's in progress for a while fails on a specific file/directory, or after a period of time.

  1. If the deployment was in progress for 1h 30min, then most probably the default timeout setting stopped the upload. Click Retry to proceed with the deployment (bear in mind that if you're deploying thousands of files from scratch you may need to do it a couple of times).
  2. Check your server for free space. Surprisingly, no space on device is one of the most common errors in cases like this.
  3. Check if the user provided in the deployment action has full write access to create files and folders in the directory in which the upload is failing.

II. No more authentication methods available

If you are getting:

Server response: No more authentication methods available

it means that the credentials provided in the action are either incorrect or incomplete. The most common cases include mistyped password, or choosing an incorrect authentication method (e.g. you provide an SSH key while the server requires both the key and username/password).

III. SSL/TLS authentication not allowed

If you are getting:

502 SSL/TLS authentication not allowed

it means that the server doesn't support SSL/TLS and you should use the regular FTP action, not FTPS.