ssh_dispatch_run_fatal git error after updating my macbook to MacOs Mojave
up vote
0
down vote
favorite
I recently updated to MacOs Mojave on my Macbook but there have been some issues using git via Terminal. The first error was fixed by installing xCode which was easy afterwards I was able to do everything except commands that include the server such as git push / pull when I run git pull which has always been working I get an error message like this
ssh_dispatch_run_fatal: Connection to [some ip] port 22: incorrect signature
fatal: Could not read from remote repository.
The same happens when trying to git push.
and I cant seem to fix this error any suggestions on how to fix it??
Kind regards Julian
git ssh terminal
asked Nov 10 at 12:37
Julian B.
214
add a comment |
up vote
0
down vote
favorite
I recently updated to MacOs Mojave on my Macbook but there have been some issues using git via Terminal. The first error was fixed by installing xCode which was easy afterwards I was able to do everything except commands that include the server such as git push / pull when I run git pull which has always been working I get an error message like this
ssh_dispatch_run_fatal: Connection to [some ip] port 22: incorrect signature
fatal: Could not read from remote repository.
The same happens when trying to git push.
and I cant seem to fix this error any suggestions on how to fix it??
Kind regards Julian
git ssh terminal
asked Nov 10 at 12:37
Julian B.
214
Somehow following these steps resolved my issue serverfault.com/questions/44222/how-do-i-fix-ssh-on-a-mac
– Julian B.
Nov 10 at 23:29
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I recently updated to MacOs Mojave on my Macbook but there have been some issues using git via Terminal. The first error was fixed by installing xCode which was easy afterwards I was able to do everything except commands that include the server such as git push / pull when I run git pull which has always been working I get an error message like this
ssh_dispatch_run_fatal: Connection to [some ip] port 22: incorrect signature
fatal: Could not read from remote repository.
The same happens when trying to git push.
and I cant seem to fix this error any suggestions on how to fix it??
Kind regards Julian
git ssh terminal
asked Nov 10 at 12:37
Julian B.
214
I recently updated to MacOs Mojave on my Macbook but there have been some issues using git via Terminal. The first error was fixed by installing xCode which was easy afterwards I was able to do everything except commands that include the server such as git push / pull when I run git pull which has always been working I get an error message like this
ssh_dispatch_run_fatal: Connection to [some ip] port 22: incorrect signature
fatal: Could not read from remote repository.
The same happens when trying to git push.
and I cant seem to fix this error any suggestions on how to fix it??
Kind regards Julian
git ssh terminal
git ssh terminal
asked Nov 10 at 12:37
Julian B.
214
asked Nov 10 at 12:37
Julian B.
214
asked Nov 10 at 12:37
Julian B.
214
asked Nov 10 at 12:37
Julian B.
214
asked Nov 10 at 12:37
Julian B.
214
214
Somehow following these steps resolved my issue serverfault.com/questions/44222/how-do-i-fix-ssh-on-a-mac
– Julian B.
Nov 10 at 23:29
add a comment |
Somehow following these steps resolved my issue serverfault.com/questions/44222/how-do-i-fix-ssh-on-a-mac
– Julian B.
Nov 10 at 23:29
Somehow following these steps resolved my issue serverfault.com/questions/44222/how-do-i-fix-ssh-on-a-mac
– Julian B.
Nov 10 at 23:29
Somehow following these steps resolved my issue serverfault.com/questions/44222/how-do-i-fix-ssh-on-a-mac
– Julian B.
Nov 10 at 23:29
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Usually, this message means that the remote server is misconfigured or out of date. Some versions of Gerrit before 2.16 (and possibly other applications using the Apache Mina SSH server) make incorrect signatures when using Ed25519 keys. (It's also possible, but unlikely, that you have a broken network card or proxy in place.)
The best way to fix this is to update the remote server such that it uses a fixed version of the appropriate SSH code. For Gerrit, this means upgrading to 2.15 or newer. Anyone else using an up-to-date OpenSSH will also have this problem and will be unable to access the server.
The alternative is to configure your system not to use Ed25519 for SSH to that system. If the remote system has the hostname example.com, you can add something like the following to your ~/.ssh/config file:
Host example.com
HostKeyAlgorithms ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
answered Nov 10 at 17:49
brian m. carlson
51618
Since I am not working on a Windows PC I don't really know what you are reffering to or what to do
– Julian B.
Nov 10 at 18:12
It means that the server you're trying to push your code to has a bug with how it handles the SSH protocol, which is used for pushing and pulling. You should update it, or modify the configuration file I mentioned, or switch to using HTTPS.
– brian m. carlson
yesterday
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Usually, this message means that the remote server is misconfigured or out of date. Some versions of Gerrit before 2.16 (and possibly other applications using the Apache Mina SSH server) make incorrect signatures when using Ed25519 keys. (It's also possible, but unlikely, that you have a broken network card or proxy in place.)
The best way to fix this is to update the remote server such that it uses a fixed version of the appropriate SSH code. For Gerrit, this means upgrading to 2.15 or newer. Anyone else using an up-to-date OpenSSH will also have this problem and will be unable to access the server.
The alternative is to configure your system not to use Ed25519 for SSH to that system. If the remote system has the hostname example.com, you can add something like the following to your ~/.ssh/config file:
Host example.com
HostKeyAlgorithms ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
answered Nov 10 at 17:49
brian m. carlson
51618
Since I am not working on a Windows PC I don't really know what you are reffering to or what to do
– Julian B.
Nov 10 at 18:12
It means that the server you're trying to push your code to has a bug with how it handles the SSH protocol, which is used for pushing and pulling. You should update it, or modify the configuration file I mentioned, or switch to using HTTPS.
– brian m. carlson
yesterday
add a comment |
up vote
0
down vote
Usually, this message means that the remote server is misconfigured or out of date. Some versions of Gerrit before 2.16 (and possibly other applications using the Apache Mina SSH server) make incorrect signatures when using Ed25519 keys. (It's also possible, but unlikely, that you have a broken network card or proxy in place.)
The best way to fix this is to update the remote server such that it uses a fixed version of the appropriate SSH code. For Gerrit, this means upgrading to 2.15 or newer. Anyone else using an up-to-date OpenSSH will also have this problem and will be unable to access the server.
The alternative is to configure your system not to use Ed25519 for SSH to that system. If the remote system has the hostname example.com, you can add something like the following to your ~/.ssh/config file:
Host example.com
HostKeyAlgorithms ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
answered Nov 10 at 17:49
brian m. carlson
51618
Since I am not working on a Windows PC I don't really know what you are reffering to or what to do
– Julian B.
Nov 10 at 18:12
It means that the server you're trying to push your code to has a bug with how it handles the SSH protocol, which is used for pushing and pulling. You should update it, or modify the configuration file I mentioned, or switch to using HTTPS.
– brian m. carlson
yesterday
add a comment |
up vote
0
down vote
up vote
0
down vote
Usually, this message means that the remote server is misconfigured or out of date. Some versions of Gerrit before 2.16 (and possibly other applications using the Apache Mina SSH server) make incorrect signatures when using Ed25519 keys. (It's also possible, but unlikely, that you have a broken network card or proxy in place.)
The best way to fix this is to update the remote server such that it uses a fixed version of the appropriate SSH code. For Gerrit, this means upgrading to 2.15 or newer. Anyone else using an up-to-date OpenSSH will also have this problem and will be unable to access the server.
The alternative is to configure your system not to use Ed25519 for SSH to that system. If the remote system has the hostname example.com, you can add something like the following to your ~/.ssh/config file:
Host example.com
HostKeyAlgorithms ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
answered Nov 10 at 17:49
brian m. carlson
51618
Usually, this message means that the remote server is misconfigured or out of date. Some versions of Gerrit before 2.16 (and possibly other applications using the Apache Mina SSH server) make incorrect signatures when using Ed25519 keys. (It's also possible, but unlikely, that you have a broken network card or proxy in place.)
The best way to fix this is to update the remote server such that it uses a fixed version of the appropriate SSH code. For Gerrit, this means upgrading to 2.15 or newer. Anyone else using an up-to-date OpenSSH will also have this problem and will be unable to access the server.
The alternative is to configure your system not to use Ed25519 for SSH to that system. If the remote system has the hostname example.com, you can add something like the following to your ~/.ssh/config file:
Host example.com
HostKeyAlgorithms ecdsa-sha2-nistp521,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
answered Nov 10 at 17:49
brian m. carlson
51618
answered Nov 10 at 17:49
brian m. carlson
51618
answered Nov 10 at 17:49
brian m. carlson
51618
answered Nov 10 at 17:49
brian m. carlson
51618
51618
Since I am not working on a Windows PC I don't really know what you are reffering to or what to do
– Julian B.
Nov 10 at 18:12
It means that the server you're trying to push your code to has a bug with how it handles the SSH protocol, which is used for pushing and pulling. You should update it, or modify the configuration file I mentioned, or switch to using HTTPS.
– brian m. carlson
yesterday
add a comment |
Since I am not working on a Windows PC I don't really know what you are reffering to or what to do
– Julian B.
Nov 10 at 18:12
It means that the server you're trying to push your code to has a bug with how it handles the SSH protocol, which is used for pushing and pulling. You should update it, or modify the configuration file I mentioned, or switch to using HTTPS.
– brian m. carlson
yesterday
Since I am not working on a Windows PC I don't really know what you are reffering to or what to do
– Julian B.
Nov 10 at 18:12
Since I am not working on a Windows PC I don't really know what you are reffering to or what to do
– Julian B.
Nov 10 at 18:12
It means that the server you're trying to push your code to has a bug with how it handles the SSH protocol, which is used for pushing and pulling. You should update it, or modify the configuration file I mentioned, or switch to using HTTPS.
– brian m. carlson
yesterday
It means that the server you're trying to push your code to has a bug with how it handles the SSH protocol, which is used for pushing and pulling. You should update it, or modify the configuration file I mentioned, or switch to using HTTPS.
– brian m. carlson
yesterday
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53239028%2fssh-dispatch-run-fatal-git-error-after-updating-my-macbook-to-macos-mojave%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Somehow following these steps resolved my issue serverfault.com/questions/44222/how-do-i-fix-ssh-on-a-mac
– Julian B.
Nov 10 at 23:29