SSH-Access key not expiring

[Steven Tschache]

I've removed an SSH-Access-Key in May and trying to add this back in now in July, it's saying: Key already exists... may need to wait up to 30 days for expiry.

Clearly, it's been ~60 days now and still unable to add the key.

Any workaround?

[Theodora Boudale · Accepted solution]

Hi Steven,

The message about SSH keys taking up to 30 days to delete is applicable when deleting an account, workspace, or repos that have SSH keys. If you simply remove an SSH key, the deletion happens immediately.

Access keys can be added to multiple projects and repos. An access key cannot be added to an account's or workspace's SSH keys. Similarly, an account's or workspace's SSH key cannot be added as an access key.

The error message indicates that the SSH key is most likely added to an account or workspace.

I would suggest checking the following places:

Account SSH keys

Check the keys listed in https://bitbucket.org/account/settings/ssh-keys/, in case this key is already added to your account's SSH keys. You can select the pencil icon that edits each key, in order to view each key's value.

Workspace SSH keys

I can see that you are an administrator of several workspaces.

Go to this page https://bitbucket.org/account/workspaces/ to see all your workspaces listed, and select Manage for each workspace > select SSH keys, and then check the SSH keys listed there.

If you still cannot figure it out, please feel free to let me know and I can create a support ticket for you. You can then share the public key in the ticket and we can check where this key is added.

Kind regards,
Theodora

[Steven Tschache]

Perfect, thx... Workspace was the location!

Very confusing, but solved my problem!

[Steven Tschache]

Additional info when trying to add the key in different areas of Bitbucket