I am unable to access Bitbucket after having verified my invitation to a new repo.

Question

I accepted an invitation to a new repository. I am still able to login to Atlassian. However, when I attempt to switch to Bitbucket, I am forced to a page that reads:

Resource not found

Return to the previous page or go back to your dashboard.

Even if I attempt to go to my dashboard, I am forced back to this same error page. I have no ability to access Bitbucket.

Patrik S · Answer

Hello @Kevin Barthman ,

This is a known bug in the platform that was reported to our engineering team on BCLOUD-23018.

I see you already added your comment on that bug, so I would suggest adding yourself as a watcher to be notified of any future updates provided by our development team about the fix implementation.

Thank you for reporting this @Kevin Barthman !

Patrik S

Kevin Barthman · Answer

I ran into this same issue. Invited to a brand new workspace, accepted that invite, and lost complete ability to navigate to any other page other than the Resource Not Found page. Another and myself were just trying to manually migrate a git repository to bitbucket from another site and were starting with a brand new fresh workspace. No repository setup yet, they just invited me to the workspace with default permissions.

@Patrik S The only way I was able to get to any other page was through your instructions  through https://community.atlassian.com/t5/Bitbucket-questions/how-to-fix-completely-broken-web-access-after-login-404-error/qaq-p/2385368 , in particular accessing via https://bitbucket.org/account/workspaces/ , but I could still end up in the same state.

I think that the only way we were able to solve this was granting me admin privileges for the workspace. We created a repository too but I do not think that actually helped get me out of the 404 page, maybe it did, we didn't test exhaustively.

This is not a feasible solution, and I believe this could cause people to completely turn away from bitbucket and believe it is down, or at worst be used maliciously (inviting someone to a workspace without privileges and getting them into a 404 if they accept, or removing privileges of someone already in a workspace). You can't even access the support community through the bitbucket itself as there is no link to it when you're in this state. You can't log out to reset things. You have to google search for solutions and hope this answer comes up.

If the admin of the workspace is not available or unwilling to resolve the issue, then you are stuck in this state as well until you discover this workaround.

Luckily I do believe I discovered some details that would be helpful to solve the issue:

My theory is that whenever you login to bitbucket, it takes you to the last workspace you accessed. If you are in this state of getting 'Resource Not Found' on a particular workspace, and it was the last one you accessed, you will have no option out unless you path to the specific URL of another workspace or the general workspaces URL. Every time you log in it will force you to go straight to the last workspace.

If you access another functional workspace just once, then whenever you login you will see your whole dashboard and have the top bar with the ability to access your profile / settings. Try to access the culprit workspace and then you're back in that same state.

I would propose a few fixes:

* If the last workspace you accessed is not one you have proper permissions under, do not set it as your default workspace and redirect you to a non-workspace specific dashboard
* Do not show a 404 on a workspace you have joined but do not have correct privileges for. You know it exists, tell the user you don't have permissions instead
* Update the links on the 404 page to take you to a page that does not take into account the last workspace you used in case this redirect loop happens in other situations
* A better 404 page for this particular situation that gives you the top bar to be able to access your account information; I'm assuming on the backend if you don't have access it just pushes you into a default 404 in case the whole site is down, so I could potentially see this being used maliciously to query for workspaces that exist but I'm extending too far past my knowledge at this point

Patrik S · Answer

Hello @Andrew Coggins ,

thank you for reaching out.

It seems you are currently a member of just one workspace that has no repositories in it. Also, the group you are currently a member of in that workspace has no access to anything.

In this case, could you ask an admin of the workspace to try to create a test repo, and then grant you/the group you are part of, access to that workspace?

That should give you the required permissions to open that workspace.

Thank you, @Andrew Coggins !
Patrik S