The authenticity of host 'gitlab.com (54.93.71.23)' can't be established

How to Use GitLab
1

After I added ssh key and try to push my files i seen this message

The authenticity of host 'gitlab.com (54.93.71.23)' can't be established.
ECDSA key fingerprint is SHA256:HbW3g8zUjNSksFbqTiUWPWg2Bq1x8xdGUrliXFzSnUw.
Are you sure you want to continue connecting (yes/no)?

Any Suggestions?

2

Type yes to continue. You can see the ssh fingerprints in https://about.gitlab.com/gitlab-com/settings/

3 Likes
3

thanks axil for reply , now after type yes as you mentioned , i face new issue

 GitLab: Deploy keys are not allowed to push code.
 fatal: Could not read from remote repository

Do you faced this issue before ?

4

It seems that you used a deploy key which will not work. They are only used to read.

Instead, add it to your account in https://gitlab.com/profile/keys.

1 Like
5

thanks axil for your help , now its working well , i was adding the key on the project not on my profile , sorry from a long time i am did not deploy a new key, but Gitlab the best for me it deserve it.
Thanks Again axil :thumbsup:

1 Like
6

I cannot find the link to the ssh fingerprints at the link you posted: all I could find is here but the fingerprint seems to have changed since then.

7

This page seems to no longer have the ssh fingerprints, and, after a thorough google search, they don’t seem to be available from a reliable online source. Bummer :confused:

8

Hi, the settings have been moved under https://about.gitlab.com/gitlab-com/settings/ :slight_smile:

2 Likes
9

Thanks!

It seems the link from https://about.gitlab.com/gitlab-com/ was never updated. Under “Where can I find detailed information on GitLab.com’s settings, such as SSH host keys and its runners?”, the “GitLab.com settings” link returns a 404.

10

Oops, nice catch! I submitted an MR https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/7358/diffs.

11

Great, thanks again.

12

This error is concerning, though, because the security risks ought to be addressed, so this message doesn’t happen.

13

I have solved this issue by deleting my .git folder and gitignore file, after this I re-initialized the git with git init and did all the process again to push my code

15

For future visitors, the appropriate, permanent reference for this appears to be on docs.gitlab.com.

@axil The URL from MR #7358 is now either a 404, or it hangs until the browser (Firefox) finally reports “a script on this page is slowing down Firefox.” Is that a concern?

Philosophically speaking, aren’t the SSH host key fingerprints important enough to merit a prominent place on the website, perhaps in the site footer? I’m not singling out GitLab here, I believe it’s a common deficiency, and extends to things like developers’ GPG signing keys, too.