FATAL Error when performing a 'Fetch' operation from Repo

martin.blocher

Hello Atlassian Support,

 

Unfortunately, I'm having a problem with one repository which prevents me from doing anything with it. When trying to 'Fetch' from the repository I get the following error:

A few details:

• I have contacted the IT Team of my company which checked my credentials and assessed that everything is fine with them;
• My colleagues can work with the repo with no problem;
• I'm able to work with all other repos (which are set up in the same manner) except this one;
• Sometimes instead of getting that error I get one that requires me SSH authentication, this is inconsistent as our team is currently only using HTTPS authentication, and my colleagues have no problem;
• I've also successfully refreshed my authentication and tried to 'Fetch' once again, but the behavior is the same.

Please have a look at this when you can and come back to me, as you can imagine this limits my workflow quite a bit.

 

Many thanks for your attention.

 

Martin Blocher

Patrik S

Hello @martin.blocher and thank you for reaching out to the Community!

It seems like you are using Sourcetree as a GUI, and I suspect it may be playing a role in this issue. In order to rule out Sourcetree and check if everything is correct with your network/credentials, I'd like to ask for you to try cloning the repository directly from the terminal (or Git bash if you are using Windows).

The clone command using HTTPS would be: 

git clone https/{username}:{app_password}@bitbucket.org/{workspace}/{repository}.git

where:

• username: your bitbucket account username (not email address). You can find your account's username by navigating to your personal bitbucket settings.
• app password: a user-level token used to authenticate git over HTTPS. If you haven't already, you can create a new app password.

If the clone in the terminal (or Git Bash) completes successfully, the issue is likely with your Sourcetree configuration, so I would suggest trying to reinstall Sourcetree.

However, if the issue also happens locally in your terminal, we kindly ask you to share the log output of the clone command so we can help identify what else could be leading to the error.

Hope that helps! Should you have any questions, feel free to ask.

Thank you, @martin.blocher !

Patrik S