kex_exchange_identification: Connection closed by remote host #55269

dongdongbh · 2023-05-12T07:22:59Z

dongdongbh
May 12, 2023

My git(hub) works fine before, but suddenly it not work.
When I type git pull origin master, it shows

kex_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I have configed key, and it works before. My network works fine. ping github.com also works.
Here is the debug message

ssh -vT git@github.com
OpenSSH_8.2p1 Ubuntu-4ubuntu0.5, OpenSSL 1.1.1f  31 Mar 2020
debug1: Reading configuration data /home/dd/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to github.com [20.205.243.166] port 22.
debug1: Connection established.
debug1: identity file /home/dd/.ssh/id_rsa type 0
debug1: identity file /home/dd/.ssh/id_rsa-cert type -1
debug1: identity file /home/dd/.ssh/id_dsa type -1
debug1: identity file /home/dd/.ssh/id_dsa-cert type -1
debug1: identity file /home/dd/.ssh/id_ecdsa type -1
debug1: identity file /home/dd/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/dd/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/dd/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/dd/.ssh/id_ed25519 type -1
debug1: identity file /home/dd/.ssh/id_ed25519-cert type -1
debug1: identity file /home/dd/.ssh/id_ed25519_sk type -1
debug1: identity file /home/dd/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/dd/.ssh/id_xmss type -1
debug1: identity file /home/dd/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.5
kex_exchange_identification: Connection closed by remote host

git remote -v
origin  git@github.com:dongdongbh/dotfiles.git (fetch)
origin  git@github.com:dongdongbh/dotfiles.git (push)

airtower-luna · 2023-05-12T12:31:51Z

airtower-luna
May 12, 2023

The SSH output looks like you don't have any keys available for authentication. Do you have SSH-Agent running, and the right key pair loaded into it?

0 replies

xc2f · 2023-05-12T12:53:43Z

xc2f
May 12, 2023

I encountered the same problem 3 hours ago, unable to push the code to github, it showed no permission, but it was still able to push normally just yesterday. After I generate a new ssh key locally and add it to the github ssh configuration, this problem still exists.
After about five or six minutes, I tried to push again, and the push was successful.

A strange thing happened to me the other day when I was syncing code on another computer. The remote branch is one commit ahead of the local branch, but when I execute git pull or git fetch / rebase locally, it shows Already up to date.. Finally, I deleted the local project and re-pulled the remote code to solve the problem.

1 reply

LeisureLinux May 13, 2023

I still have the same issue here in Shanghai. git pull/push through proxy though.
But apparently, since it is through ssh protocol, then the http.proxy setup should not affect.

dongdongbh · 2023-05-13T01:20:40Z

dongdongbh
May 13, 2023
Author

I have sshd daemon running. I didn't make any change, and now it works, so strange~

6 replies

LeisureLinux May 13, 2023

I guess I found the root cause, and had a work around by adding a line in my /etc/hosts Linux Desktop.
pick an IP address from git section in https://api.github.com/meta

❯ grep github /etc/hosts
20.201.28.152 github.com

my original resolving github.com has address 20.205.243.166, is not working.

Unfortunately, no service outage reported in githubstatus.com page.

LeisureLinux May 13, 2023

Just after a working git pull, and re-run git pull again, found same issue happened on the new IP.
So this workaround won't work, since it is a server side issue.

xuthus5 Jun 6, 2023

I guess I found the root cause, and had a work around by adding a line in my /etc/hosts Linux Desktop. pick an IP address from git section in https://api.github.com/meta

❯ grep github /etc/hosts 20.201.28.152 github.com

my original resolving github.com has address 20.205.243.166, is not working.

Unfortunately, no service outage reported in githubstatus.com page.

thank you, good for me.

1990jtf Jan 23, 2024

wow~ It works! Thanks a lot!

cooljacket Jan 27, 2024

But it cause that when i access github.com in Chrome, the web page cannot display right. Finally i recover the local host dns config, use the following LeisureLinux's solution.

LeisureLinux · 2023-05-13T09:54:26Z

LeisureLinux
May 13, 2023

I guess GFW make it.
By checking: https://docs.github.com/en/authentication/troubleshooting-ssh/using-ssh-over-the-https-port
which I followed the ~/.ssh/config added the port 443.
and use command like: "proxychains -q git pull", it is working now.

Here is what is working now through https, and through proxy:

❯ proxychains -q ssh -T git@github.com
The authenticity of host '[ssh.github.com]:443 ([20.205.243.160]:443)' can't be established.
ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[ssh.github.com]:443' (ED25519) to the list of known hosts.
Hi LeisureLinux! You've successfully authenticated, but GitHub does not provide shell access.

13 replies

Nu11able Jan 22, 2024

It works! Thank you so much

lxd6701996 Jan 22, 2024

macOS 13.6.3 is ok

ZiyangQian Jan 30, 2024

thanks so much

charlesMYoung Feb 21, 2024

it's working ~~~. nice

stupidchen Mar 13, 2024

Cool! It works for me. Thanks!

dongdongbh · 2023-05-14T22:11:45Z

dongdongbh
May 14, 2023
Author

Because many people in China encounter this problem, seems it's related to network. I reopen this issue. More solution and feedback are welcome.

0 replies

LeslieLeung · 2023-05-15T03:39:22Z

LeslieLeung
May 15, 2023

Try ssh-keyscan github.com >> ~/.ssh/known_hosts. Works for me.

Found on this post

3 replies

airtower-luna May 15, 2023

Never do this, especially not if you know or suspect the government is behind the problem. ⚠️

It means you accept whatever keys the server offers, allowing them to intercept your connection. If there's a problem with the public keys of the server, check if the fingerprint you're seeing is one of the published ones. Same for any other SSH server.

LeslieLeung May 15, 2023

Thanks for the notice. If anyone did the above, just use ssh-keygen -R github.com to undo it.

P.S. I've checked my known_hosts, the fingerprints are identical to the published ones. Maybe whoever's doing this is not clever/malicious enough to do this.

AffordCK Jun 10, 2023

It works for me, thanks!

ChrisVicky · 2023-05-15T04:55:33Z

ChrisVicky
May 15, 2023

Same here in Tianjin, and it's resolved by executing the following command, found here.

ssh -T -p 443 git@ssh.github.com

It seems that something, related to ssh identification or Github ip resolution, has been changed during the execution.

6 replies

neufeng Jun 8, 2023

Very good! Works for me too! I'm in ShangHai! Thanks a lot!

berrytsukiii Jun 30, 2023

thx！

Angeladadd Jul 23, 2023

Thanks! Works for me along with closing VPN.

zhaziqwe Jan 20, 2024

thank you， it really works

swahpy Apr 2, 2024

this works for me. Together with adding IP to /etc/hosts file by checking https://dnschecker.org/#A/ssh.github.com. Thanks a lot!

Seraphli · 2023-05-15T05:50:38Z

Seraphli
May 15, 2023

Adding this to ~/.ssh/config solves my problem

Host github.com
  Hostname 20.200.245.248
  Port 443

I use South Korea IP.
https://dnschecker.org/#A/ssh.github.com

19 replies

ocean2580 Jan 26, 2024

Thanks a lot!!!

fearlesschenc Jan 26, 2024

Save my life!!!

yiwenup Jan 26, 2024

thx!

y0unghe Jan 27, 2024

It worked. Thanks!

kelinkong Jan 31, 2024

Thanks!

leeeezp · 2023-05-15T12:17:08Z

leeeezp
May 15, 2023

I have the same problem. It will be normal when I don't use clash.

0 replies

iDestin · 2023-05-27T05:36:16Z

iDestin
May 27, 2023

I am in Beijing and recently discovered that SSH is not working properly, but I have not found a solution yet

0 replies

spianmo · 2023-06-07T02:00:08Z

spianmo
Jun 7, 2023

Enabling SSH connections over HTTPS can solve this problem
If you are able to SSH into git@ssh.github.com over port 443, you can override your SSH settings to force any connection to GitHub.com to run through that server and port.

To set this in your SSH configuration file, edit the file at ~/.ssh/config, and add this section:

Host github.com
    Hostname ssh.github.com
    Port 443
    User git

You can test that this works by connecting once more to GitHub.com:

$ ssh -T git@github.com

Hi USERNAME! You've successfully authenticated, but GitHub does not
provide shell access.

17 replies

cyssxt Jan 20, 2024

Thanks!it works for me!

Mrhs121 Feb 3, 2024

万分感谢！！！

wangxdmm Feb 23, 2024

You save my life....

xxxxinc Mar 28, 2024

好使的！

wa008 Apr 22, 2024

works for me

zachx121 · 2023-06-14T10:01:41Z

zachx121
Jun 14, 2023

try 'ssh-agent && ssh-add ~/.ssh/id_rsa'

1 reply

ning2510 Aug 13, 2023

This works for me, thx

Falasool · 2023-08-02T08:13:59Z

Falasool
Aug 2, 2023

If you use Proxy client like ClashX, please close the "Enhanced Mode" and try again.

3 replies

Div1to Aug 4, 2023

This works for me, thx

crazy-dadong Sep 21, 2023

This works for me, thx

cheung-chifung Apr 2, 2024

This works for me, thx

Elon-Lee · 2023-08-24T01:54:10Z

Elon-Lee
Aug 24, 2023

Becuase of this problem , check your proxy config . Just like clashx shadowsocks etc ...

0 replies

ccsuper1024 · 2023-10-18T12:39:41Z

ccsuper1024
Oct 18, 2023

sometimes,Maybe ,we should check our .ssh/ , the public key's and private key's file name.it must start with id_rsa. do not start with anyelse word. I modify the filename ,then ,everything go correct

0 replies

mark-wang-beep · 2023-11-01T00:44:29Z

mark-wang-beep
Nov 1, 2023

I just closed my ClashX, and then problem solved

0 replies

changbindu · 2023-11-19T01:55:06Z

changbindu
Nov 19, 2023

Check the solution here.
https://stackoverflow.com/questions/10127818/ssh-exchange-identification-connection-closed-by-remote-host-under-git-bash

1 reply

philipjoep Dec 29, 2023

This is literally the only thing that worked for me. I'm running a Linux VM on Windows. I unplugged my LAN cable, switched to Wifi, and suddenly I was able to connect to github again. Then after switching back to LAN, it all worked.

Now, I did also update my .ssh/config file and cleared out my known_hosts file before these steps, but they didn't have any affect. I did leave the config file the same.

Host github.com
    Hostname ssh.github.com
    Port 443
    User git

treblam · 2023-12-08T00:22:11Z

treblam
Dec 8, 2023

I just closed openclash in my openwrt router, and it works.

2 replies

Marerc Jan 9, 2024

Then how can you access github.com?

treblam Jan 22, 2024

github is not blocked in China, but it’s very slow without using proxy.

arko-svmx · 2024-02-21T07:19:50Z

arko-svmx
Feb 21, 2024

Make sure if you are using any client connector app like Zscaler, turn its internet security off. It solved every problem for me.

0 replies

queenofcorgis · 2024-03-14T15:35:23Z

queenofcorgis
Mar 14, 2024
Maintainer

Given the popularity of this discussion and the quality of information shared, we want to make sure others can easily find it so we’ve reopened this discussion for better discoverability for our members.

0 replies

thesilentpsycho · 2024-03-21T16:57:32Z

thesilentpsycho
Mar 21, 2024

my org vpn was off. please check

0 replies

This comment was marked as off-topic.

Sign in to view

kex_exchange_identification: Connection closed by remote host #55269

Replies: 22 comments · 72 replies

dongdongbh May 13, 2023 Author

dongdongbh May 14, 2023 Author

This comment was marked as off-topic.

queenofcorgis Mar 14, 2024 Maintainer

Replies: 22 comments 72 replies

dongdongbh
May 13, 2023
Author

dongdongbh
May 14, 2023
Author

queenofcorgis
Mar 14, 2024
Maintainer