Can't work with remote repo by ssh. Please make sure you have the correct access rights and the repository exists

General
1

I turned off my laptop, the next day I tried to pull new master but suddenly I received this message

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

OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f 31 Mar 2020
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolving “gitlab.example.net” port 22
ssh: Could not resolve hostname gitlab.example.net: Temporary failure in name resolution

2

Looks like a DNS resolution problem to me, check the network configuration for your laptop, and make sure you can visit websites, as well as resolve the name for your Gitlab server.

3

Appreciate your answer, I am able to visit websites, would you mind to tell me how can I “resolve the name for your Gitlab server” ?

4

Well, in your text above, you have gitlab.example.net. So whatever that host was, if you are using the DNS name for it, it needs to resolve to an IP. So this needs to be resolved from wherever your domain is registered - be it a domain that is purchased, or some internal one, for example, gitlab.local.

I don’t know your environment so I cannot tell you anymore than that, but obviously, if you are trying to connect to gitlab.example.net, that domain must exist. Otherwise, you would have to use the IP address of your server instead.

1 Like
5

@actimel33

The domain GitLab is served under should match the value for external_url in /etc/gitlab/gitlab.rb. You can find it with:

egrep "^external_url" /etc/gitlab/gitlab.rb

For this to work, a DNS record must be set up to point to your GitLab server’s IP address.

If you don’t have a DNS record set up, or if external_url is literally set to gitlab.example.com, you can use the IP address to connect to the server by setting external_url to http://<your_server_ip> and then running gitlab-ctl reconfigure

If your GitLab server has a working external_url and domain name other than gitlab.example.com, you’ll want to change the remote origin in your .gitconfig so it doesn’t point to gitlab.example.com (a non-working domain)

1 Like
6

I don’t have /etc/gitlab/gitlab.rb folder at all on my linux machine, I checked .git/config url = git@gitlab.example.ne…
It points to the right place

7

@actimel33 If you pull up gitlab.example.net in your web browser, does it load your GitLab instances’ login page?