# Cannot reconnect BitBucket account

**URL:** <https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588>\
**Category:** Integrations and Accounts\
**Created:** [January 6, 2023, 10:52am UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588 "2023-01-06T10:52:35Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![paulmiller3000](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/paulmiller3000/32/23243_2.png) [@paulmiller3000](https://discuss.circleci.com/u/paulmiller3000)\
**Post date:** [January 6, 2023, 10:52am UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/1 "2023-01-06T10:52:35Z")

</div>

I followed the instructions at [CircleCI security alert: Rotate any secrets stored in CircleCI](https://circleci.com/blog/january-4-2023-security-alert/) to disconnect Bitbucket. Now I wish I hadn’t.

I was able to reauthenticate with GitHub, but cannot see my Bitbucket projects. That’s because, after revoking app permissions in Bitbucket, CircleCI still shows Bitbucket under account integrations.

 ![image](https://global.discourse-cdn.com/circleci/original/3X/f/b/fbf14aa117c74dbd9becf13435b43b2568dac967.jpeg)

There is no way to remove it from this page. I’ve searched the forums and it looks like this cannot be solved by the user (which is sort of not really a good user experience).

When I open CircleCI, it asks me to select an organization:

![image](https://global.discourse-cdn.com/circleci/original/3X/1/3/1325f2cd422ecded0ad3f0aaf138bd177408a23b.png)

My Bitbucket organization does not appear.

Selecting GitHub takes me to Projects, which displays the following:

 ![image](https://global.discourse-cdn.com/circleci/original/3X/3/b/3b802bdbabb12086260e82a3dcb10d9578ee31e1.png)

Refreshing and clearing cache does nothing.

Ironically, if I do a hard refresh, I see my projects for just a second before the above error appears. Dev Tools shows the following:

 ![image](https://global.discourse-cdn.com/circleci/original/3X/e/6/e646eec9f850b5d32b20f48f8f4cb5be8bfbfa59.png)

Any recommendations? We are now dead in the water because we cannot build our application!

---

<div class="post-metadata">

**Author:** ![pollingj](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/pollingj/32/31991_2.png) [@pollingj](https://discuss.circleci.com/u/pollingj)\
**Post date:** [January 6, 2023, 11:50am UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/2 "2023-01-06T11:50:49Z")

</div>

We are suffering with the same issue. Some of our devs appears to be able to get in, and some can’t.  
My personal experience was multi browsers and multi times of revoking and some how, some way, I got a recaptcha form to appear and suddenly my Bitbucket organisations reappeared.

---

<div class="post-metadata">

**Author:** ![paulmiller3000](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/paulmiller3000/32/23243_2.png) [@paulmiller3000](https://discuss.circleci.com/u/paulmiller3000)\
**Post date:** [January 6, 2023, 12:41pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/3 "2023-01-06T12:41:47Z")

</div>

Thank you. I tried clearing cache and a different browser. No luck. Support told me to clear cache and cookies. Did that again, no luck and advised them. Waiting to hear back.

Based on what you and Support said, sounds like a lot of people have this issue. In my searching, it’s been a bug for awhile. Hopefully this prompts CircleCI to finally fix it.

---

<div class="post-metadata">

**Author:** ![pollingj](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/pollingj/32/31991_2.png) [@pollingj](https://discuss.circleci.com/u/pollingj)\
**Post date:** [January 6, 2023, 2:23pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/4 "2023-01-06T14:23:57Z")

</div>

Support are currently helping our team out by deleting the tokens on their side, and that appears to have worked.

---

<div class="post-metadata">

**Author:** ![paulmiller3000](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/paulmiller3000/32/23243_2.png) [@paulmiller3000](https://discuss.circleci.com/u/paulmiller3000)\
**Post date:** [January 6, 2023, 2:29pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/5 "2023-01-06T14:29:23Z")

</div>

What specifically did you do? I deleted mine in Bitbucket but still have the ghost connection in CircleCI.

---

<div class="post-metadata">

**Author:** ![paulmiller3000](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/paulmiller3000/32/23243_2.png) [@paulmiller3000](https://discuss.circleci.com/u/paulmiller3000)\
**Post date:** [January 6, 2023, 3:23pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/6 "2023-01-06T15:23:21Z")

</div>

With the lack of documentation and no answer from Support, we used this as the kick in the pants to finally move our legacy repo from Bitbucket to GitHub. Good riddance to Bitbucket!

Unfortunately, we still have this error for GitHub, even though we reauthenticated:

 ![image](https://global.discourse-cdn.com/circleci/original/3X/1/0/1038ad0a5d5cef4b62f6bbae5b15da366ff833ad.png)

---

<div class="post-metadata">

**Author:** ![pollingj](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/pollingj/32/31991_2.png) [@pollingj](https://discuss.circleci.com/u/pollingj)\
**Post date:** [January 6, 2023, 3:49pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/7 "2023-01-06T15:49:23Z")

</div>

CircleCI had to remove the ghost token for us.

---

<div class="post-metadata">

**Author:** ![ChristopherN](https://avatars.discourse-cdn.com/v4/letter/c/ba8739/32.png) [@ChristopherN](https://discuss.circleci.com/u/ChristopherN)\
**Post date:** [January 6, 2023, 4:01pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/8 "2023-01-06T16:01:39Z")

</div>

I have the same problem, tried multiple browser and sessions, but that did not fix anything.

---

<div class="post-metadata">

**Author:** ![paulmiller3000](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/paulmiller3000/32/23243_2.png) [@paulmiller3000](https://discuss.circleci.com/u/paulmiller3000)\
**Post date:** [January 6, 2023, 5:47pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/9 "2023-01-06T17:47:38Z")

</div>

Unfortunately, CircleCI Support has not been responsive. Hopefully someone else will post here with a solution, if one exists on the user side.

---

<div class="post-metadata">

**Author:** ![paulmiller3000](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/paulmiller3000/32/23243_2.png) [@paulmiller3000](https://discuss.circleci.com/u/paulmiller3000)\
**Post date:** [January 6, 2023, 6:32pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/10 "2023-01-06T18:32:18Z")

</div>

![image](https://global.discourse-cdn.com/circleci/original/3X/f/b/fb479c871e0d1920e015095b7caecfc07efc962c.png)

---

<div class="post-metadata">

**Author:** ![paulmiller3000](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/paulmiller3000/32/23243_2.png) [@paulmiller3000](https://discuss.circleci.com/u/paulmiller3000)\
**Post date:** [January 6, 2023, 9:14pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/11 "2023-01-06T21:14:08Z")

</div>

@DrTorte with CircleCI Support had to take care of it on his end. We’re back up and running. Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [January 16, 2023, 9:14pm UTC](https://discuss.circleci.com/t/cannot-reconnect-bitbucket-account/46588/12 "2023-01-16T21:14:09Z")

</div>

Closed on January 16, 2023, 9:14pm UTC

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
