Common Deployment Errors

Unfortunately, there can be a number of issues you might run into when running a deployment. You can find more information about these errors and how to solve them below.

• 452 Transfer aborted. No space left on device
• 552 Disk full - please upload later
• Automatic Deployments not working
• Bad message
• bash: command not found
• Branches master not tracked, deployment not required
• Closed Stream
• Deployment timed out, exceeded 6 hours
• Error communicating with your server: 426 Failure reading network stream.
• Error communicating with your server: Connection reset by peer
• Error communicating with your server: Net::ReadTimeout
• Error: no such file open
• Execution of {command} timed out after x minutes
• Failure write
• Files uploading unexpectedly
• FTP data connection errors
• General SFTP write failure
• No files are uploading
• No route to host
• npm - no such file or directory
• Permission Denied
• SFTP - Error no such file
• Shopify - Error communicating with your server: Cannot overwrite generated asset
• SVN timeout error - The server sent a truncated HTTP response body
• Temporary failure in name resolution
• The SSH public key (host key) of your server has changed
• We couldn't access your repository. Please ensure the authentication details are correct.
• We couldn't login to your server. Please ensure credentials are correct.