Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

PUSH - fatal: unable to access ... Why did this start happening?


SourceTree 3.1.2 (even attempting pushing using Git GUI/CMD trying to bypass SourceTree... issue still happens) Was working fine... then this. Seems like server issue.

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks push -v --tags origin <Branch Name>:<Branch Name>
fatal: unable to access 'https://<user><team>/<repo>.git/': OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054
Pushing to https://<user><team>/<repo>.git
Completed with errors, see above.

1 answer

1 accepted

0 votes
Answer accepted
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 03, 2019

Hi James,

Welcome to the Atlassian Community.

At the moment it looks like there are some issues with Bitbucket and SSH, please have a look at You can also subscribe to the products and/or services you want to be notified about if there are any issues in the future.

Hi Mikael,

Thanks for the info and the quick response.

This did seem to be more on the bitbucket side of things, as I mentioned with my testing through git directly and bypassing sourcetree. A few minutes ago, when I was navigating the site. I did end up seeing a similar notification on one of the pages saying there was a known issue.

I'll chalk this up as the answer, as it appears to be a known issue.

Thanks again for your help.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events