My config.yml looks like: version: 2.0 jobs: build: environment: BUNDLE_PATH: vendor/bundle docker: - image: circleci/ruby:2.3-node-browsers environment: DATABASE_HOST: 127.0.0.1 DATABASE_USER: ubuntu DATABASE_PASSWORD: "" RAILS_…

Search the forum, that error has come up a few times :slightly_smiling_face:

I did before I post. Found several tips, and I am looking for if there is any documentation on this. The documentation I followed didn’t solve my problem.

I doubt there’d be official CircleCI documentation; general usage problems tend not to appear in docs, which are much more about things going right! I suppose it is conceivable that it could go in a FAQ though. However, as I say, I think it has been covered here. Further tips to try: log in via S…

I was reading this Permissions and access during deployment . I have added private key of my hose to the settings page, as name app.example.com, so cat ~/.ssh/config should have an entry like IdentityFile /home/circleci/.ssh/id_rsa_app.example.com as per the documentation, but I see like: circleci@…

Possibly. That looks like something that CircleCI would have set up. I’m assuming that you’re doing a checkout from one place (e.g. GitHub) and deploying to another (e.g. Digital Ocean). Thus, there should not be a name clash, since it should be differentiated by the Host. However, yes, if you are …

Try this command before connect to host: ssh-keyscan -H app.example.com >> ~/.ssh/known_hosts

[image] geidivan: app.example.com > I tried what you said. But not sure why am I getting public key denied error. #!/bin/bash -eo pipefail ssh-keyscan -H app.example.com > >> ~/.ssh/known_hosts echo $CIRCLE_BRANCH if [ "${CIRCLE_BRANCH}" == "master" ]; then bundle exec mina deploy TO=produ…

I would suggest authorizing a different key, removing the current key, and adding the newly authorized key back through the CircleCI interface. I’m not entirely sure why this happens, but in my own personal use I’ve found this resolved the problem.

The authenticity of host 'app.example.com (xxx.xxx.xx.xxx)' can't be established

Build Environment

aruprakshit August 7, 2018, 1:58pm 7

I found a thread discussing the same. But it was not completed, so not sure how the OP solved it.

Topic		Replies	Views
SSH issues Deployments ssh , keys , circle-yml , 2.0	1	3800	April 7, 2020
Authenticity of host can't be established. Are you sure you want to continue connecting (yes/no)? Build Environment	9	24313	October 24, 2018
The authenticity of host 'heroku.com (50.19.85.132)' can't be established Deployments heroku	2	6713	April 1, 2018
The authenticity of host sub.domain.com (0.0.0.0) can't be can't be established. Are you sure you want to continue connecting (yes/no)? Deployments ssh	3	4376	January 24, 2019
SCP authenticity requires input, freezes build Deployments circle-yml	3	4394	March 18, 2018

The authenticity of host 'app.example.com (xxx.xxx.xx.xxx)' can't be established

Related topics