Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Gitlab Cloudbuild Setup Error: Fingerprint Already Taken on first time set-up

Discussion in 'Unity Build Automation' started by hoperin, Sep 11, 2018.

  1. hoperin

    hoperin

    Joined:
    Feb 9, 2014
    Posts:
    52
    So, pretty much the title says it all -- I'm setting up Cloudbuild for my project for the first time. My project is a private Gitlab repository. When I try to add a the SSH key that Unity Cloudbuild generated for me as a new Deploy Key to the repository's settings within Gitlab, I get this error:

    Fingerprint has already been taken, Deploy keys projects deploy key fingerprint has already been taken.

    I've tried generating the SSH key with the SHH and the HTTP repo url in unity -- i always get the same key no matter what.

    No one else has been working on this project & I have never added any other deploy keys. I've checked against the SSH keys added to my Gitlab account as well -- no duplications. Ive also never used Cloudbuild on this computer before, though its a work computer and it may have been used on other Cloudbuild projects in the past...

    Is there any way to generate a new key, seeing as Gitlab flat refuses to take this one? Or is there a known solution to this issue?

    I found this thread -- https://forum.unity.com/threads/using-cloud-build-with-gitlab.405028/#post-3385571 -- where it seems to be the same issue, but none of the solutions there made any difference.
     
    nickfourtimes likes this.
  2. ollieblanks

    ollieblanks

    Unity Technologies

    Joined:
    Aug 21, 2017
    Posts:
    459
  3. marauderkr

    marauderkr

    Joined:
    Jun 10, 2014
    Posts:
    46
    hello,
    I tried to regenerate with the CB API and it keeps telling me "Error: Not authorized. The server does not recognize the client."
    Yet my role is "manager" as required.

    EDIT: i had to enter my orgs API key (though I was logged in in CB)
    but now it worked.
     
    Last edited: Sep 29, 2021