I successfully used the SSH option on a private BitBucket repo two days ago, and now CircleCI does not believe I have any SSH keys registered. When I use this option, I get:
Failed to enable SSH
No SSH key is found. Please make sure you’ve added at least one SSH key in your VCS account.
I am using an organisation BitBucket account and a free tier CircleCI account.
I have tried deleting unused accounts in my SSH keys UI:
That did not help. I also deleted a public key (that had previously been successful) and re-added it, also to no avail.
When this was working two days ago, I did not use add_ssh_keys, so I assume that is not required. I will, however, try that. It does not seem to be mentioned in the docs.
I assume that SSH keys should be registered as per these instructions, rather than using the read-only SSH keys that one can register per project.
This might be a bug on our end introduced by a recent internal change that we have made to our BitBucket system (BitBucket are switching off their 1.0 API in April and we had to migrate to version 2 (sounds very familiar )).
Lovely, thanks @marc - if you need any logs/timings, I can ping you the name of the private repo via PM.
Let me know when it is rolled back, and I’ll test it. Would a Rebuild with SSH be okay, or would I need to push a commit and then Rebuild that? (I think there are quite a few things in Circle where a rebuild keeps a lot of old context).
I never thought to reply earlier. The rollback will have gone live this morning about 20 minutes after my message. On my phone so I can’t check the precise details!
Hello @halfer, big fan! Thanks for everything you do. The rollback went live, but it looks like that change was unrelated to this issue since it’s still happening. Could you DM me some job links that show the issue with no keys found? I’ll add them to my report so we can get this sorted.
Sure, I’ll ping you something via PM. I’m probably being as daft as a brush, but as far as I can tell, the config is effectively unchanged since SSH sessions last worked.
I’m running into the same issue. Yesterday I could SSH into the container, now I get the failure message. No SSH key is found. Please make sure you've added at least one SSH key in your VCS account
I’m a bit stuck without the ssh ability (local build only takes me so far).
Do we have any window into how long it’s going to take to get a response to our ticket on this issue? It’s blocking current work. Considering moving to a different CI platform over it.
It’s being actively investigated now. There was a bit of a delay with the US holiday, but we have our engineering team investigating and I have made the support manager aware of your ticket.
Hi guys. What status of this issue? I have same problem. My ssh key from Bitbucket don’t use on ssh debug. I got : No SSH key is found. Please make sure you've added at least one SSH key in your VCS account
I don’t have a solution yet, we are working with BitBucket to see what may have changed since it seems the API call we use related to the SSH keys no longer wants to use the creds we are passing. We are aware of the pain this is causing and are trying for a solution as soon as possible.
)).
