Authentification failed with new token

[pushpathadam]

Hi,

I'm a free tier user with a few static sites that I maintain using git to update bitbucket cloud.

I haven updated some of them in a while but they are still active on bitbucket. I created an API token and was able to update one site with the following command syntax: 

git remote set-url origin https://x-token-auth:TOKEN@Bitbucket.org/REPOSITORY

I tried the the same token on another repository and got this message:

remote: You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated.

fatal: Authentication failed for 'my repository'

I created a new token and got the same message. The repository exists. 

• Are there any restrictions on the number of tokens or repositories I might be hitting with the free tier?
• Are the API-tokens meant to be shared across repositories or is it one API-token per repository?

I appreciate any insight, I'm a sporadic user and try to keep up with the latest updates. 

Best 

Tom

[Brant Schroeder]

@pushpathadam take a look at this KB article https://support.atlassian.com/bitbucket-cloud/kb/the-requested-repository-either-does-not-exist-or-you-do-not-have-access-error-in-ssh-git-operations/ 

[pushpathadam]

Thanks Brant! 

It worked after I created an api access tokens at each repository level. Took a bit to find out where that existed but the article really helped.

I must have gotten lucky with my account level token.

-Tom