gitlab connection refused ssh port 22 and 443

Question

For the last couple of days I have been unable to push to the remote (gitlab), it has worked before this. I know this question has 10s of similar SO questions and perhaps an answer is somewhere in those. However I have been trying many of the suggested solutions - in vain.

• When I push I get:

  ssh: connect to host gitlab.com port 22: Connection refused fatal: The remote end hung up unexpectedly

• The local is on a constitutional server and many people here are using port 22 mostly for github with no problems. Is it possible that this is a firewall setting on my side that could be related to gitlab specifically? The administrator ensures that it is not a simple whitelist issue.

• My gitlab url is as:

  origin [email protected]:myname/myproject.git (fetch) origin [email protected]:myname/myproject.git (push)

• I have tried to update the git-url with the alternative ssh format:

  origin ssh://[email protected]/myname/myproject.git (fetch) origin ssh://[email protected]/myname/myproject.git (push)

• I have tried both port 22 and the alternative 443 - this is the ~/.ssh/config file:

  Host gitlab.com RSAAuthentication yes IdentityFile ~/.ssh/id_rsa

• Alternative:

  Host gitlab.com Hostname altssh.gitlab.com User git Port 443 PreferredAuthentications publickey IdentityFile ~/.ssh/id_rsa

• I have tried to use https connection (in vain).

• Made new ssh keys (in vain).

I am lost with things to try and my branch is ahead of origin by a lot of commits. Am I missing something simple here to try out ?.

UPDATE

When removing ~/.ssh/config and issuing ssh -Tv [email protected] it still does not work - I get:

OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to gitlab.com [52.167.219.168] port 22.
debug1: connect to address 52.167.219.168 port 22: Connection refused
ssh: connect to host gitlab.com port 22: Connection refused

UPDATE 2 So it turns out that our institutional server does not whitelist gitlab.com because they - in contrast to, say, github.com, does not provide an official IP address range. My solution was to make a mount point from my workstation computer to the server containing my project, and then push/pull the git directory via the computer.

Nan

Answer 1

Make sure there is no ~/.ssh/config file in your case: the default URL you mention should work without a config file.

And make sure the content of the ~/.ssh/id_rsa.pub is registered to your account.

Test that it is the case with:

ssh -Tv [email protected]

If that does not work, it means either the ssh port is blocked, or ISP does not give access to the remote site.

It turns out the OP mentions the second case:

our institutional server does not whitelist gitlab.com because they - in contrast to, say, github.com, does not provide an official IP address range.
My solution was to make a mount point from my workstation computer to the server containing my project, and then push/pull the git directory via the computer.

Splint

See update. BTW, why no config file in this setting ? – Nan

@Nan no config: it will interfere with the default URL. – Splint

@Nan Does it work with ssh -Tv [email protected]? If not, would about.gitlab.com/2016/02/18/… help? (I mentioned it in https://mcmap.net/q/1281485/-gitlab-ssh-via-public-wifi-port-22-blocked) – Splint

No see my update. Connection still refused, but whether registered to my account i do not know if it tells. – Nan

@Nan it looks like the ssh ports are blocked from your workstation somehow (even though it was working before) Especially if github.com does not work either. – Splint

Answer 2

If you get the error..

ssh: connect to host git.my-host.com port 22: Connection refused
fatal: Could not read from remote repository.

..then you might be able to solve it by deleting the entry for the IP of your GitLab host in

~/.ssh/known_hosts

Cradling

Answer 3

1.) Add the Host known in nano ~/.ssh/config

Host git.company.com
HostName <ip address of git> 
Port 222

2.) Run this command to generate and pair pub and priv key.

ssh-keygen -t ed25519 -C "<comment>"

3.) Copy content of ~/.ssh/id_rsa.pub

4.) Paste it in by generating new SSH keys in your gitlab account, specify title to where you will use it to add identification of the generated SSH Key.

Try to clone a project now on your gitlab repo.

Plascencia

Answer 4

I had this error when I had checked out the origin/<branch_name> branch. After switching to branch <branch_name> and pushing them again, it worked properly.

Dagmar