no github repository access anymore: ssh public key already in use...

I wanted to add a new repository to UCB and it didn’t work (no access), so I tried to add the displayed public ssh key to my account on github again. To clean up, I first deleted my old UCB public key I had there from the access list and then tried to add the new one, but it failed with the message “Key is already in use”. I don’t know if the old one was the same or not, but now all my projects don’t work anymore because they have no access to the repositories.

When I asked the github support, they said that the key is in use by another account, and it can’t be added by more than one at the same time. Is this public key unique for my account or is it the same for everybody?

I’m using the new beta and everything worked without problems before… what could be the issue here?

Update: It looks like all the projects I set up before the update don’t work anymore, new ones work perfectly. I also noticed that all the old projects share the same ssh key, is this intended? For the new project, I added the key as deploy key in github and it seems to work. Can we expect that all projects have unique keys? (because if not, it can’t be used as deploy keys with more than one repository)

Update 2: The github support says that somebody else has this key entered in his account. I definitely didn’t give it to anybody and I have only one account.

Seems like I have the same situation here :S

The SSH key is shared across the organization, so it will be the same for all projects within that org.

We provide the public key, which means you can configure as many hosts as you want with access to that public key. The restriction about adding a key more than once is something enforced by Bitbucket, GitHub, etc- not by us.

Hope this helps. Let me know what happens :slight_smile:

  • Sophia

At the @SophiaC told me about Unity DevOps Build Automation and I created a new key!

Generating a new key was the solution for my project :slight_smile:

1 Like