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

Can't pull/push after MacOSX Mojave update 10.14.1

blooper13 November 1, 2018

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 git@bitbucket.org` 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
Atlassian Team members are employees working across the company in a wide variety of roles.
November 2, 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

blooper13 November 4, 2018

Hi Brian, 

Thanks for the reply, I tried everything stated on the wikipage: https://confluence.atlassian.com/bitbucket/troubleshoot-ssh-issues-271943403.html

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 https://bitbucket.org/user/repo URL. 

henscu August 5, 2019

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?

blooper13 August 5, 2019

@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 :-( 

henscu August 5, 2019

@blooper13 yes, I saw a similar suggestion here:

https://superuser.com/questions/1373697/ssh-fails-on-macos-mojave-10-14-1

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
TAGS
AUG Leaders

Atlassian Community Events