shanklq
September 19, 2020, 11:23pm
1
Hi Everyone, i’m not sure if i’m posting it in wrong category please assist me if i’m wrong.
My team is having a trouble for past few days everything was working fine suddenly two days ago all of our team members who were using ssh for their git operations started to have problem with gitlab.
What we’ve went through so far.
We made sure ssh key is fine.
https is working fine.
Checked on multiple OS Windows/Mac/Linux
So far no luck and problem is still there.
Thank you
ammar15
September 21, 2020, 9:06am
3
Yes i am also facing same issue. error is
kex_exchange_identification: read: Connection timed out
fatal: Could not read from remote repository.
i have githib repo also and this is working. i am easily clone, pull and push code from gihub but i am facing issue in project on gitlab.
shanklq
September 21, 2020, 11:17am
4
yes I’m using GitLab as the provider any action clone/pull/push is not responding i.e do a clone with ssh git@gitlab.com : keeps hanging and ends without any progress.
Let me know if I can run any diagnostic commands to find the issue.
shanklq
September 21, 2020, 11:18am
5
in my case I’m not seeing any error as command never finishes
Are you able to clone through HTTPS?
Do you have any new firewall / something that closes port 22?
shanklq
September 22, 2020, 7:19pm
7
Yeah, we’re able to perform all action through https.
No, we’ve no firewall blocking port 22.
shanklq
September 22, 2020, 7:27pm
8
I believe the problem is specific with region as i used on a remote computer and key worked perfectly.
Can you try to do ssh -vvv git@gitlab.com
, so we can see where the connection drops?
shanklq
September 23, 2020, 12:20pm
10
ssh -vvv git@gitlab.com
OpenSSH_7.9p1 Debian-10+deb10u2, OpenSSL 1.1.1d 10 Sep 2019
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "gitlab.com" port 22
debug2: ssh_connect_direct
debug1: Connecting to gitlab.com [172.65.251.78] port 22.
debug1: Connection established.
debug1: identity file /home/lb/.ssh/id_rsa type -1
debug1: identity file /home/lb/.ssh/id_rsa-cert type -1
debug1: identity file /home/lb/.ssh/id_dsa type -1
debug1: identity file /home/lb/.ssh/id_dsa-cert type -1
debug1: identity file /home/lb/.ssh/id_ecdsa type -1
debug1: identity file /home/lb/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/lb/.ssh/id_ed25519 type -1
debug1: identity file /home/lb/.ssh/id_ed25519-cert type -1
debug1: identity file /home/lb/.ssh/id_xmss type -1
debug1: identity file /home/lb/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.9p1 Debian-10+deb10u2
That’s where it stops
Unfortunately, I don’t really know how to help you, it seems that you don’t receive any response about the protocol.
Strange thing is that the connection has been established:
debug1: Connecting to gitlab.com [172.65.251.78] port 22.
debug1: Connection established.
Maybe open a support ticket?
shanklq
September 26, 2020, 2:40am
13
Yeah seems like the only option.
Thanks for helping man
Hi @shanklq
I’m facing the same issue.
Is your issue resolved?
Thank you