I cannot connect to git using ssh

[roabhi]

Hello. First post.

Been browsing the forum for a while since I installed Manjaro a few weeks ago trying to get a solution to my problem but wasn´t able to get a clear picture of what is going on with my system so…here I am

Since day one I was having issues connecting to github via ssh. After I few days i assumed it was some kind of error related to my network since I noticed I could ssh into github using a shared connection from my phone. Also I was able to connect through cable directly plugged in into the router.

However that is not the case anymore. The only difference between before (working with my borrowed cell phone connection / cable and now) is that I installed base-devel package. I also installed foundry. Other that that everything is the same…

I noticed a huge update a week ago where a few ssh packages were updated. Not sure if that could be the issue.

tac /var/log/pacman.log | less | grep ssh

[2024-08-20T22:07:07+0200] [ALPM] upgraded libssh (0.10.6-2 -> 0.11.0-2)
[2024-08-09T16:36:01+0200] [ALPM] upgraded qemu-block-ssh (9.0.1-1 -> 9.0.2-1)

If I go

systemctl status ssh-agent.service

then

Unit ssh-agent.service could not be found.

I can enable it as user service with

systemctl --user enable ssh-agent.service

But ssh still does not work

I also noticed I can ssh into other desktop / machines without problem but I cannot ssh back from those machines into Manjaro.

No idea how to work around this. I am a long time Mint user but I do not consider myself a Linux expert whatsoever so please bear with me.

Any help is appreciated

Thanks.

[linux-aarhus]

openssh works just as expected.

I use it often to commit to github.

@roabhi

I also noticed I can ssh into other desktop / machines without problem but I cannot ssh back from those machines into Manjaro.

ssh and sshd is two different aspects of the same service.

The ssh daemon is not default enabled.

To be able ssh into a Manjaro host you need to enable the daemon.

systemctl enable --now sshd

There is no global ssh-agent.service - there is a ssh-agent - it has been asked before how to setup ssh-agent - and if you really need the service it is a user service

systemctl --user status ssh-agent.service

[Search results for 'ssh-agent' - Manjaro Linux Forum]

[site.manjaro.org ssh-agent]

[cscs]

@roabhi

If I go

systemctl status ssh-agent.service

then

Unit ssh-agent.service could not be found.

I can enable it as user service with

systemctl --user enable ssh-agent.service

This is unnecessary.

Just use ssh-agent.

The only need to start the service is to have this automatically run in the background even if you dont start a graphical session.

https://wiki.archlinux.org/title/OpenSSH

https://wiki.archlinux.org/title/SSH_keys#ssh-agent

@linux-aarhus

There is no ssh-agent.service

There is. Its a user service. Though I dont think most users actually need/want it.

$ pacman -Ql openssh | grep service
openssh /usr/lib/systemd/system/sshd.service
openssh /usr/lib/systemd/system/sshdgenkeys.service
openssh /usr/lib/systemd/user/ssh-agent.service

If you would like your ssh agent to run when you are logged in, regardless of whether X is running, a handy ssh-agent.service is included in openssh since the version 9.4p1-3, which can be enabled as a user unit.

[linux-aarhus]

@cscs

There is. Its a user service. Though I dont think most users actually need/want it.

Yes - I know - I realized that it should read no global ssh-agent.service as the agent always is run in user space.

[roabhi]

Wow thanks for the quick reply.

Any idea the reason why I could connect via my shared cell-phone connection before and why that stopped working?

Thanks.

[linux-aarhus]

@roabhi

Any idea the reason why I could connect via my shared cell-phone connection before and why that stopped working

Not really - It has never happened to me (Denmark) - so I am speculating that it could be network related. Perhaps not your local network - but the wider internet - depending on your location …

@roabhi

I could ssh into github using a shared connection from my phone. Also I was able to connect through cable directly plugged in into the router.

So you are able to connect to github using ssh.

@roabhi

is that I installed base-devel package

That does not change your network connection capabilities.

Some help to do basic network troubleshooting can be found in below mini guide - you may want to disable IPv6 as this can sometimes be the joker - I remember several topics where IPv6 played a role

[root tip] [How To] Basic network know-how and troubleshooting

Difficulty: ☆☆☆☆☆ Network connections This is not a guide on troubleshooting hardware and drivers but the network connection itself. The guide is assuming your hardware and driver(s) are in a working state. The guide is intended as a reference for working your self through situations like I can’t connect to the internet I ping an IP but not a domain name How can I find my printer’s IP My browser is slow when browsing Every user will be in a situation when network troubleshooting is nece…

[xabbu]

Can you try to connect to the problematic ssh server with a more verbose output? With it, you can see at which point the ssh connection hangs or get disconnected.

ssh -vvv user@server

[roabhi]

@linux-aarhus

Not really - It has never happened to me (Denmark) - so I am speculating that it could be network related. Perhaps not your local network - but the wider internet - depending on your location …

I do not think that is the issue because I have another machine (exactly the same model - HP 2570p) running Mint 19.3 and I can ssh to anything without problems. Obviously it runs another OS and Kernel but if network is the issue I do not see how that is possible.

@linux-aarhus

So you are able to connect to github using ssh.

I was able to do that through sharing my cell phone connection from my Android device yes. Not anymore.

Will take a look at that tutorial thanks

[roabhi]

@xabbu

Can you try to connect to the problematic ssh server with a more verbose output? With it, you can see at which point the ssh connection hangs or get disconnected.

My logs

ssh -vvv git@github.com

OpenSSH_9.8p1, OpenSSL 3.3.1 4 Jun 2024
debug1: Reading configuration data /home/rob/.ssh/config
debug1: /home/rob/.ssh/config line 1: Applying options for github.com
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf
debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/rob/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/rob/.ssh/known_hosts2'
debug2: resolving "github.com" port 22
debug3: resolve_host: lookup github.com:22
debug3: channel_clear_timeouts: clearing
debug3: ssh_connect_direct: entering
debug1: Connecting to github.com [140.82.121.3] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: connect to address 140.82.121.3 port 22: Connection timed out
ssh: connect to host github.com port 22: Connection timed out

~/.ssh/config

Host github.com
	AddKeysToAgent yes
	IdentityFile ~/.ssh/id_ed25519

Thank you

[xabbu]

It fails very early in the process. So it is not a ssh protocol problem. It looks more like a network problem to me. It doesn’t need to be a cable, router or ISP network problem, the problem can be a bad firewall rule or some other network setting on this specific system. Sometimes settings for container or virtualization software can also be a problem.

If you use the latest live image, can you connect to github via ssh?

[roabhi]

Same thing

    ~  ssh -vvv git@github.com                              INT ✘  25s  
OpenSSH_9.8p1, OpenSSL 3.3.1 4 Jun 2024
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf
debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/manjaro/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/manjaro/.ssh/known_hosts2'
debug2: resolving "github.com" port 22
debug3: resolve_host: lookup github.com:22
debug3: channel_clear_timeouts: clearing
debug3: ssh_connect_direct: entering
debug1: Connecting to github.com [140.82.121.3] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: connect to address 140.82.121.3 port 22: Connection timed out
ssh: connect to host github.com port 22: Connection timed out

Tried over my shared phone connection which used to work and with cable directly. Same thing.

[linux-aarhus]

If you cannot make a live iso connect to github using ssh Hmm - something odd is going on with your network

Just as a PoC that a - mostly default - Manjaro system can connect

 $ ssh -vvv github.com
OpenSSH_9.8p1, OpenSSL 3.3.1 4 Jun 2024
debug1: Reading configuration data /home/fh/.ssh/config
debug1: /home/fh/.ssh/config line 2: Applying options for *
debug1: /home/fh/.ssh/config line 25: Applying options for github.com
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf
debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/fh/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/fh/.ssh/known_hosts2'
debug2: resolving "github.com" port 22
debug3: resolve_host: lookup github.com:22
debug3: channel_clear_timeouts: clearing
debug3: ssh_connect_direct: entering
debug1: Connecting to github.com [140.82.121.4] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: Connection established.
debug1: identity file /home/fh/.ssh/fhdk-github-ssh.key type 3
debug1: identity file /home/fh/.ssh/fhdk-github-ssh.key-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.8
debug1: Remote protocol version 2.0, remote software version babeld-18e0b4214
debug1: compat_banner: no match: babeld-18e0b4214
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to github.com:22 as 'git'
debug3: record_hostkey: found key type ED25519 in file /home/fh/.ssh/known_hosts:5
debug3: record_hostkey: found key type ECDSA in file /home/fh/.ssh/known_hosts:6
debug3: record_hostkey: found key type RSA in file /home/fh/.ssh/known_hosts:15
debug3: load_hostkeys_file: loaded 3 keys from github.com
debug1: load_hostkeys: fopen /home/fh/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: have matching best-preference key type ssh-ed25519-cert-v01@openssh.com, using HostkeyAlgorithms verbatim
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-v00@openssh.com
debug2: host key algorithms: ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,kex-strict-s-v00@openssh.com
debug2: host key algorithms: ssh-ed25519,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
debug2: MACs ctos: hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256
debug2: MACs stoc: hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512,hmac-sha2-256
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug3: kex_choose_conf: will use strict KEX ordering
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU
debug3: record_hostkey: found key type ED25519 in file /home/fh/.ssh/known_hosts:5
debug3: record_hostkey: found key type ECDSA in file /home/fh/.ssh/known_hosts:6
debug3: record_hostkey: found key type RSA in file /home/fh/.ssh/known_hosts:15
debug3: load_hostkeys_file: loaded 3 keys from github.com
debug1: load_hostkeys: fopen /home/fh/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host 'github.com' is known and matches the ED25519 host key.
debug1: Found key in /home/fh/.ssh/known_hosts:5
debug3: send packet: type 21
debug1: ssh_packet_send2_wrapped: resetting send seqnr 3
debug2: ssh_set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: ssh_packet_read_poll2: resetting read seqnr 3
debug1: SSH2_MSG_NEWKEYS received
debug2: ssh_set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug2: KEX algorithms: sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-v00@openssh.com
debug2: host key algorithms: ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug3: kex_input_ext_info: extension server-sig-algs
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Will attempt key: /home/fh/.ssh/fhdk-github-ssh.key ED25519 SHA256:OBcYNZWbYRtEY3ixt9L6HelSRjp6Y3IDqzKbP5VUpeo explicit
debug2: pubkey_prepare: done
debug1: Offering public key: /home/fh/.ssh/fhdk-github-ssh.key ED25519 SHA256:OBcYNZWbYRtEY3ixt9L6HelSRjp6Y3IDqzKbP5VUpeo explicit
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: /home/fh/.ssh/fhdk-github-ssh.key ED25519 SHA256:OBcYNZWbYRtEY3ixt9L6HelSRjp6Y3IDqzKbP5VUpeo explicit
debug3: sign_and_send_pubkey: using publickey with ED25519 SHA256:OBcYNZWbYRtEY3ixt9L6HelSRjp6Y3IDqzKbP5VUpeo
debug3: sign_and_send_pubkey: signing using ssh-ed25519 SHA256:OBcYNZWbYRtEY3ixt9L6HelSRjp6Y3IDqzKbP5VUpeo
debug3: no authentication agent, not adding key
debug3: send packet: type 50
debug3: receive packet: type 52
Authenticated to github.com ([140.82.121.4]:22) using "publickey".
debug1: channel 0: new session [client-session] (inactive timeout: 0)
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Entering interactive session.
debug1: pledge: filesystem
debug3: client_repledge: enter
debug3: receive packet: type 80
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug3: client_input_hostkeys: received RSA key SHA256:uNiVztksCsDhcc0u9e8BujQXVUpKZIDTMczCvj3tD2s
debug3: client_input_hostkeys: received ECDSA key SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM
debug3: client_input_hostkeys: received ED25519 key SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU
debug1: client_input_hostkeys: searching /home/fh/.ssh/known_hosts for github.com / (none)
debug3: hostkeys_foreach: reading file "/home/fh/.ssh/known_hosts"
debug3: hostkeys_find: found ssh-ed25519 key at /home/fh/.ssh/known_hosts:5
debug3: hostkeys_find: found ecdsa-sha2-nistp256 key at /home/fh/.ssh/known_hosts:6
debug3: hostkeys_find: found ssh-rsa key at /home/fh/.ssh/known_hosts:15
debug1: client_input_hostkeys: searching /home/fh/.ssh/known_hosts2 for github.com / (none)
debug1: client_input_hostkeys: hostkeys file /home/fh/.ssh/known_hosts2 does not exist
debug3: client_input_hostkeys: 3 server keys: 0 new, 3 retained, 0 incomplete match. 0 to remove
debug1: client_input_hostkeys: no new or deprecated keys from server
debug3: client_repledge: enter
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 3 setting TCP_NODELAY
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug3: send packet: type 98
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug3: client_repledge: enter
debug1: pledge: fork
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 32000 rmax 35000
debug3: receive packet: type 100
debug2: channel_input_status_confirm: type 100 id 0
PTY allocation request failed on channel 0
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
debug2: channel 0: rcvd ext data 3
debug2: channel 0: rcvd ext data 4
debug2: channel 0: rcvd ext data 2
Hi fhdk! debug2: channel 0: written 9 to efd 6
debug2: channel 0: rcvd ext data 76
debug2: channel 0: rcvd ext data 1
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug3: receive packet: type 96
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug3: receive packet: type 97
debug2: channel 0: rcvd close
debug2: chan_shutdown_read: channel 0: (i0 o1 sock -1 wfd 4 efd 6 [write])
debug2: channel 0: input open -> closed
debug3: channel 0: will not send data after close
debug2: channel 0: obuf_empty delayed efd 6/(77)
You've successfully authenticated, but GitHub does not provide shell access.
debug2: channel 0: written 77 to efd 6
debug3: channel 0: will not send data after close
debug2: channel 0: obuf empty
debug2: chan_shutdown_write: channel 0: (i3 o1 sock -1 wfd 5 efd 6 [write])
debug2: channel 0: output drain -> closed
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug3: send packet: type 97
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
  #0 client-session (t4 [session] r43 i3/0 o3/0 e[write]/0 fd -1/-1/6 sock -1 cc -1 io 0x00/0x00)

Connection to github.com closed.
debug3: send packet: type 1
Transferred: sent 2468, received 2620 bytes, in 0.2 seconds
Bytes per second: sent 10567.7, received 11218.6
debug1: Exit status 1

When a connection times out in the way your does - it is a telltale sign that something is preventing the service response from reaching your system - where that lies - one can only guess.

Depending on whether your phone connects using the mobile network or your local wifi AP you may be able to verify if it is a local to your network issue.

[roabhi]

I can confirm I can connect without issues from another network

OpenSSH_9.8p1, OpenSSL 3.3.1 4 Jun 2024
debug1: Reading configuration data /home/rob/.ssh/config
debug1: /home/rob/.ssh/config line 1: Applying options for github.com
debug1: Reading configuration data /etc/ssh/ssh_config
debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf
debug3: /etc/ssh/ssh_config line 2: Including file /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf depth 0
debug1: Reading configuration data /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/home/rob/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/home/rob/.ssh/known_hosts2'
debug2: resolving "github.com" port 22
debug3: resolve_host: lookup github.com:22
debug3: channel_clear_timeouts: clearing
debug3: ssh_connect_direct: entering
debug1: Connecting to github.com [140.82.121.3] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x48
debug1: Connection established.
debug1: identity file /home/rob/.ssh/id_ed25519 type 3
debug1: identity file /home/rob/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.8
debug1: Remote protocol version 2.0, remote software version babeld-18e0b4214
debug1: compat_banner: no match: babeld-18e0b4214
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to github.com:22 as 'git'
debug3: record_hostkey: found key type ED25519 in file /home/rob/.ssh/known_hosts:1
debug3: record_hostkey: found key type RSA in file /home/rob/.ssh/known_hosts:2
debug3: record_hostkey: found key type ECDSA in file /home/rob/.ssh/known_hosts:3
debug3: load_hostkeys_file: loaded 3 keys from github.com
debug1: load_hostkeys: fopen /home/rob/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: have matching best-preference key type ssh-ed25519-cert-v01@openssh.com, using HostkeyAlgorithms verbatim
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal

.....

ssh -T git@github.com  
Hi roabhi! You've successfully authenticated, but GitHub does not provide shell access.

So it is the network…any idea how to debug that?. Where to start? .

Also it is not clear to me why I can connect with Mint 19.3 and not with Manjaro. If someone could share some light on it I would appreciate it.

Thanks a lot.