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

Can't pull/push after MacOSX Mojave update 10.14.1

After updating my macbook today (2018-11-01) to Mojave 10.14.1

I suddenly can't push or pull to Bitbucket. 

The test `ssh -T` doesn't give a warning and before the update everyting was fine. 

I tried renewing my SSH key but that doesn't work. The strange part is that I can check the remote because it says that my local is not up to date with remote but I can't push or pull.. 

Help me! 

1 answer

0 votes
bgannin Atlassian Team Nov 02, 2018

Hi Gijs,

Are all your SSH keys loaded into the SSH agent? They frequently get booted unexpectedly in our experience. You can check with the following command:

ssh-add -l

if not then you'll use:

ssh-add ~/.ssh/your-key-name

Brian Ganninger
Senior Mac Developer, Sourcetree

Hi Brian, 

Thanks for the reply, I tried everything stated on the wikipage:

But I didn't see anything wrong. I still think it's because of the update from Apple. 

I just noticed yesterday that I cannot SSH to my VPS-server anymore too so I think there is something wrong within the update. 

For now I can pull/get with the URL. 

I have the same problem with ssh and pull/push. It started when I updated to Mojave 10.14.6 last week (late July 2019)

Did you ever solve it, or are you still using HTTPS?

@henscu I solved the problem by editing the settings of my SSH configuration 

sudo nano /etc/ssh/ssh_config

Than the IPQoS part was needed to fix my problem: 

Host *

        SendEnv LANG LC_*

        ServerAliveInterval 30

        ServerAliveCountMax 5

        IPQoS 0x00  


But I noticed while updating I suddenly get the error that there is a new problem with that the commit is too large too commit, while the internet is saying that you need to enlarge the buffer, this doesn't fix my problem. So my only fix now is still working with HTTPS instead of SSH :-( 

@blooper13 yes, I saw a similar suggestion here:

So I added the following line to my ~/.ssh/config, but it made no difference (I tried your variant as well)...

Host *

IPQoS lowdelay throughput

I'm surprised there isn't more info on this problem as it must be affecting everyone who uses Git/Bitbucket...

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Sourcetree

Bug Fix: Sourcetree for Windows authentication error when updating to app password

Hello Sourcetree users!!! With the recent removal of Bitbucket Cloud account passwords for app passwords (please see our Bitbucket Cloud community post for details on why we made this change for se...

78,814 views 134 29
Read article

Atlassian Community Events