403 Error When Pulling from Repository After 6 Months of Normal Usage

phuoc_pham
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 8, 2025

 

Hi Bitbucket Community,

I’ve been using my repository on Bitbucket without any issues for the past 6 months. I could push and pull code normally every day. However, today I suddenly encountered the following error when trying to pull from the repository:

 

remote: The requested repository either does not exist or you do not have access. If you believe this repository exists and you have access, make sure you're authenticated. fatal: unable to access 'https://bitbucket.org/company/repositoryn_name.git/': The requested URL returned error: 403


 

I’ve verified that:

  1. The repository still exists.
  2. My credentials (username and password or SSH key) are correct.
  3. I haven’t changed any configurations related to Git or Bitbucket.

This issue appeared out of nowhere, and I haven’t made any changes to my setup. Everything was working fine until today.

Does anyone know what could be causing this issue? Could it be related to recent changes in Bitbucket’s authentication system or repository permissions?

Thanks in advance for your help!

1 answer

0 votes
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 9, 2025

Hello @phuoc_pham ,

and welcome to the Community!

The error you are currently receiving is related to authentication, meaning the credentials provided by you or any sort of caching mechanism you have on your machine does not have access to the content in question.

The first important step in narrowing down the issue is to understand which protocol you're currently using: HTTPS or SSH.

  • If you're using HTTPS, ensure that your username and app password are correct. Bitbucket requires an app password instead of your account password for Git operations.

  • If you're using SSH, verify that your SSH key is added to your Bitbucket account. You can check and manage your SSH keys in your Bitbucket account settings.

    If you have multiple keys in your machine, it may also be the case the wrong key is being used by SSH. To confirm the order of the keys being attempted during the git command, you can try to execute the git operation using the verbose flags below : 

    GIT_TRACE_PACKET=1 GIT_TRACE=1 GIT_SSH_COMMAND="ssh -vvv" git clone git@bitbucket.org:<workspace>/<repository>.git

Could you try those suggestions and let us know how it goes ?

Thank you, @phuoc_pham !

Patrik S 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events