SSH is Down

SSH for gitlab is down:

~>ssh -T git@github.com
Hi b9chris! You've successfully authenticated, but GitHub does not provide shell access.
~>ssh -T git@gitlab.com
ssh: connect to host gitlab.com port 22: Network is unreachable

Here I’m connecting to github on SSH, just to verify it’s nothing on my end. Works like a charm. In the second 2 lines, I attempt to connect to gitlab, and it takes a while (you can’t see the timing here), then produces the above error.

I use Gitlab daily. I’ve been connecting successfully for years, including yesterday, so this isn’t an issue of poor configuration or a novice - nothing has changed in my config. The issue first arose today, and has been ongoing for several hours.

Here’s another attempt, using TortoiseGit instead, which uses a different SSH client (PLink):

git.exe pull --progress -v --no-rebase “origin”
fatal: Could not read from remote repository.

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

git did not exit cleanly (exit code 1) (23172 ms @ 10/19/2021 5:01:33 PM)

In addition, it appears this page is not checking enough to monitor outages - it reports all systems are up:

https://status.gitlab.com/

That command says “Welcome to GitLab, @hcgrove!” to me, so it would seem that SSH is up again.

Strange. I found it very odd there’s nothing about this on any Gitlab official channel, so, something more complicated is up. But, here I am again, same test just a minute ago, getting into Github just fine, same client same connection same port same everything… and Gitlab is unreachable.

I can’t just keep being unable to work … gonna start moving things over to Github, since I see no attention being paid to this by Gitlab.

~>ssh -T git@gitlab.com
ssh: connect to host gitlab.com port 22: Network is unreachable
~>ssh -T git@github.com
Hi b9chris! You’ve successfully authenticated, but GitHub does not provide shell access.

does suggest the problem is on your end. Just not in something that also affects github.com. Can you see gitlab.com in a browser (make sure it’s not just a cached copy you see)?

I can also connect to GitLab (via SSH) now.

Your ISP can also have problems causing problems like what you see, but the error message is typically different, my ISP at home had an issue last week, causing some sites, github being one of them, to be unavailable for an hour or two).

Why would GitLab pay attention? Nothing objectively verifiable suggests this is due to an error on their part, and this is just a user forum, mostly frequently by other users of GitLab. A couple of employees come by here regularly, but they generally don’t deal with (what looks like) networking issues (on what seems to be your end).

I’ve ruled that out - like I said I can connect on the exact same protocol and port to Github, but, not Gitlab. I really doubt this is an issue on my end. It’s possible the port is blocked by my ISP, but, why now and why just one website?

And that’s just the least-large explanation I can think of - the problem isn’t on my machine given I can access other SSH just fine without changing anything. So… I’d think whatever customers are affected by this, Gitlab would want to fix it.

But I’m moving on.

That only rules out a very limited set of problems. And with an error message that clearly points to your end, your insisting that the problem is not on your end seems rather uninformed.

As I’m just a user: Please do move on.

@b9chris sounds more like the problem is with the IP address range. Cloudflare functionality used by Gitlab will force you to do google captchas on the website if your IP address or ISP IP Range has been used for abuse - so as @grove said, check https://gitlab.com in your browser and see if you have any issues with it or not? If you see the cloudflare checking your whatever screen, then it means that your IP address/range is a problem. You can easily get around this by firing up a free VPN to change your location, eg different town/country or whatever and see if SSH access and Gitlab starts to work. If it does, then this will prove that your internet connection/IP/ISP IP range is the source of the problem.

You can even do other diagnostics like:

telnet gitlab.com 22

and see if you get a response. For example, SSH for gitlab.com is working for me, see below:

ian@elise:~$ ssh -T git@gitlab.com
Welcome to GitLab, @iwalker!

ian@elise:~$ telnet gitlab.com 22
Trying 172.65.251.78...
Connected to gitlab.com.
Escape character is '^]'.
SSH-2.0-OpenSSH_7.9p1 Debian-10+deb10u2
^]
telnet> quit
Connection closed.

as you can see, I used the standard ssh command used for verifying the connection from Gitlabs documentation, and also a telnet command to make sure access to the particular port isn’t blocked. I don’t think your ISP is blocking just to one site, rather your IP address/IP range is compromised because it was used for abuse via spammers or whatever in the past, and is seen by cloudflare as an untrusted source.

Gitlab is not responsible for any abuse on ISP provider networks - therefore if you cannot access Gitlab because of this, then you should be complaining to your ISP and not blaming Gitlab. Gitlab have the right to block nefarious networks from connecting to their servers. Therefore you need to be a bit more reasonable in your accusations before blaming Gitlab as being the problem. You need to diagnose further the issues to find out what is the cause.

1 Like