Just in case the problem still exists or anyone else has the same problem (I had it too...), here is the solution: You need the server's adress in the [user]/.ssh/known_hosts file, which as the name implies tells the scp command to accept this server's fingerprint. The easiest way to get this done is to do a manual deploy command on the server. This will lead to a something like that: ... [INFO] [deploy:deploy] The authenticity of host '###.###.###.###' can't be established. RSA key fingerprint is d7:bd:11:1c:74:43:24:31:e1:b8:b8:fe:e9. Are you sure you want to continue connecting? (yes/no):
Answering the question with 'yes' the known_hosts file will be created or the key will be added to an existing file. Continuum doesn't do that (maybe a point for future releases) and that's why this error message appears. Any later deployments to this server will use this fingerprint for authentification and no message appears. M -- View this message in context: http://www.nabble.com/Site-distribution-url-examples--tf1901554.html#a7987836 Sent from the Continuum - Users mailing list archive at Nabble.com.