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

[James Burdick]

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>@bitbucket.org/<team>/<repo>.git/': OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054
Pushing to https://<user>@bitbucket.org/<team>/<repo>.git
Completed with errors, see above.

[Mikael Sandberg · Accepted solution]

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 https://status.atlassian.com/. You can also subscribe to the products and/or services you want to be notified about if there are any issues in the future.

[James Burdick]

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.