Can different git accounts transfer files to the same github account through ssh key?

Question

I have set up the ssh key on github:

But when cloning the library on github through ssh, an error message appears:

Am I missing any configuration?

Supplement:

ssh -vvv -T git@github.com

Supplement:

The file is generated

習慣沉默 · Answer

Do you lack the configuration for scientific Internet access? ssh -vvv -T git@github.com take a look.

Git has no concept of account.

You have different ssh keys and the same GitHub account.

All GitHub users share an ssh account named git.

Based on the ssh debugging information, consider firewall (or similar network restrictions) issues. Check the Windows Firewall settings, network settings (does your network not allow access to port 22 or something? Is there a transparent proxy?), and finally check the Chinese characteristics part.

PHP中文网 · Answer

First picture

➜ .ssh ssh -vvv -T git@github.com

OpenSSH_7.3p1, OpenSSL 1.0.2j  26 Sep 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: resolving "github.com" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to github.com [192.30.253.112] port 22.
debug1: Connection established.
debug1: identity file /home/mugbya/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mugbya/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mugbya/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mugbya/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mugbya/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mugbya/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mugbya/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mugbya/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.3
debug1: Remote protocol version 2.0, remote software version libssh-0.7.0
debug1: no match: libssh-0.7.0
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to github.com:22 as 'git'

After trying it, it seems that it is not a problem with the ssh certificate. You can continue to investigate