RSA fingerprint missing for github.com

jongear · January 14, 2019, 10:06pm

The authenticity of host 'github.com (192.30.253.112)' can't be established.
RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
Are you sure you want to continue connecting (yes/no)? 
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

https://travis-ci.com/jongear/minidrone-ble/jobs/170325754#L213-L217

jongear · January 14, 2019, 10:48pm

Works when adding

‘echo -e “Host *\n\tStrictHostKeyChecking no\n” >> ~/.ssh/config’

BanzaiMan · January 15, 2019, 12:03am

How are you trying to connect to GitHub? Perhaps via git+ssh instead of https?

jongear · January 18, 2019, 4:13pm

I’m using semantic-release to tag and drop a released copy of my npm package back onto my github repo. I’m actually not sure what semantic-release is using. I believe it’s ssh but not certain.

github.com

semantic-release/semantic-release/blob/master/docs/usage/ci-configuration.md#ci-configuration

# CI configuration

## Run `semantic-release` only after all tests succeeded

The `semantic-release` command must be executed only after all the tests in the CI build pass. If the build runs multiple jobs (for example to test on multiple Operating Systems or Node versions) the CI has to be configured to guarantee that the `semantic-release` command is executed only after all jobs are successful. This can be achieved with [Travis Build Stages](https://docs.travis-ci.com/user/build-stages), [CircleCI Workflows](https://circleci.com/docs/2.0/workflows), [Codeship Deployment Pipelines](https://documentation.codeship.com/basic/builds-and-configuration/deployment-pipelines), [GitLab Pipelines](https://docs.gitlab.com/ee/ci/pipelines.html#introduction-to-pipelines-and-jobs), [Codefresh Pipelines](https://codefresh.io/docs/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines), [Wercker Workflows](http://devcenter.wercker.com/docs/workflows) or [GoCD Pipelines](https://docs.gocd.org/current/introduction/concepts_in_go.html#pipeline).

See [CI configuration recipes](../recipes/README.md#ci-configurations) for more details.

## Authentication

**semantic-release** requires push access to the project Git repository in order to create [Git tags](https://git-scm.com/book/en/v2/Git-Basics-Tagging). The Git authentication can be set with one of the following environment variables:

| Variable                        | Description                                                                                                                                                                                                                  |
|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `GH_TOKEN` or `GITHUB_TOKEN`    | A GitHub [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line).                                                                                                    |
| `GL_TOKEN` or `GITLAB_TOKEN`    | A GitLab [personal access token](https://docs.gitlab.com/ce/user/profile/personal_access_tokens.html).                                                                                                                       |
| `BB_TOKEN` or `BITBUCKET_TOKEN` | A Bitbucket [personal access token](https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html).                                                                                                 |
| `GIT_CREDENTIALS`               | [URL encoded](https://en.wikipedia.org/wiki/Percent-encoding) Git username and password in the format `<username>:<password>`. The username and password must each be individually URL encoded, not the `:` separating them. |

Alternatively the Git authentication can be set up via [SSH keys](../recipes/git-auth-ssh-keys.md).

This file has been truncated. show original

BanzaiMan · January 18, 2019, 4:32pm

Hmm. Documentation indicates that it’s using HTTPS, but the error message (and your workaround) is not consistent with HTTPS. :-/

jongear · January 18, 2019, 4:42pm

Yeah, I’m not really sure why it’s suddenly having issues. I’ve used semantic-release on other projects without any issues. However, the main difference is on those projects I did not use matrix. For this project I need to be certain it builds on different versions of node on different operating systems so I employed a matrix. Maybe that’s the differentiator from a standard travis build that doesn’t require the StrictHostKeyChecking trick to allow semantic-release to work

github.com

jongear/minidrone/blob/master/.travis.yml#L59-L69


- name: '[OSX] Node.js v10.x xcode10'
  sudo: required
  os: osx
  osx_image: xcode10
  node_js: '10'
  script:
    - npm run build
    - npm run report-coverage
  after_success:
    - 'echo -e "Host *\n\tStrictHostKeyChecking no\n" >> ~/.ssh/config'
    - semantic-release

Topic		Replies	Views
Travis-ci.org - build cannot clone private Bitbucket repository Atlassian Bitbucket	2	3017	April 13, 2020
GitHub pages deployment fails with "missing github_token" Deployment	4	1892	November 16, 2019
Travis CI Build failed: peer fingerprint did not match Travis CI Discussions & Feedback	2	750	October 8, 2020
I'm having trouble getting travis to authenticate with and deploy builds to github Deployment	2	1150	January 22, 2020
Travis CI Linux hosts certificate store not up to date Linux build-env , travis-build , bug	2	1466	June 9, 2022

RSA fingerprint missing for github.com

Related Topics