Bitbucket keeps redirecting to different workspace

Jakub Klas

When i am trying to use bitbucket, in my company instance, but when i try to use bitbucket it redirects me to different workspace and never shows the right one. Even when i change the workspace manualy. It still doesnt show me the right workspace and shows me the wrong one. I even told my manager to remove me from the wrong workspace, it still shows up. 
Therefor, i dont see any repozitories and even clonning doesnt work. But i should have all the rights to write in those repositories and projects. 

Arkadiusz Wroblewski

Hello and Welcome @Jakub Klas 

this usually happens when Bitbucket keeps dropping you into the last / “default” workspace for your account and then keeps redirecting back to it. There’s no reliable “set my default workspace” switch, so you can feel stuck even if you manually change it.

What to do:

Don’t start from the Bitbucket home page

Open the correct workspace directly and bookmark it:

https://bitbucket.org/<your-workspace-id>/

Use that bookmark instead of going to bitbucket.org first.

Make sure you actually left the wrong workspace

It’s not enough to remove you from a repo/project, if you’re still a workspace member, Bitbucket may keep landing you there.

Avatar (top right) → All workspaces → leave the wrong one (or have an admin remove you from the workspace itself).

Confirm you’re logged into the right Atlassian account

A very common cause is being signed in with a different Atlassian account / email alias than the one your company granted access to. If you have multiple accounts, Bitbucket will show you “empty” workspaces and cloning will fail.

Quick test:

open an incognito/private window

log in once (correct account)

go straight to the workspace URL from step 1

If cloning still doesn’t work

Then it’s not only the redirect, it’s access/auth:

wrong account session

no repo permission in the correct workspace

SSH key / app password missing for that account

At that point ask the workspace admin to confirm:

you are added to the correct workspace (not only a project)

you have repo permissions in that workspace

 

Have a great Day.