Answers: <p>It was a simple mistake I made when I register <code>gitlab-runner</code>. I just used <code>gitlab-runner register [options]</code></p>
  <p>But when I register it with <code>sudo</code>, it was working properly.</p>
  <p><code>sudo gitlab-runner register [option]</code></p>
  <p>Runner is running in <code>Ubuntu-18.04</code> server.</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-02-09T14:40:55.873Z
Answers: 2021-02-09T14:40:55.873Z
Answers: Sachith Muhandiram
Answers: <p>This is likely because your requests were dropped before they landed on the GitLab host. Check your firewalls and other security rules after assured that the 1234 port is open</p>
  
Answers: CC BY-SA 4.0
Answers: 2021-02-06T15:47:44.860Z
Answers: Port is open and can access to it. Will check and let you know.
Answers: Sachith Muhandiram
Answers: CC BY-SA 4.0
Answers: 2021-02-06T06:55:08.917Z
Answers: 2021-02-06T06:55:08.917Z
Answers: Hakob
Body: <p>I have gitlab runner with, <code>docker</code> as executor and <code>docker:latest</code> as default image.</p>
  <p>Runner is connected to the project and runs pipeline, but it stuck at</p>
  <blockquote>
  <p>Reinitialized existing Git repository in /builds/sachith/omy-project/.git/</p>
  <p>fatal: unable to access 'https://gitlab.myhost.com:1234/sachith/omy-project.git/': Failed to connect to gitlab.myhost.com port 1234: Operation timed out</p>
  </blockquote>
  <p>I logged to gitlab-runner running server and tried cloning project as <code>gitlab-runner</code> user and it worked.</p>
  <p>Why am I getting this error?</p>
  
Tags: <continuous-integration><gitlab><gitlab-ci-runner>
Title: Gitlab runner fails with connection timeout
UserDisplayName: Sachith Muhandiram
ThreadText: # Gitlab runner fails with connection timeout
  
  (Asked by: username_0 on 2021-02-04)
  
  I have gitlab runner with, `docker` as executor and `docker:latest` as default image.
  
  Runner is connected to the project and runs pipeline, but it stuck at
  
  > Reinitialized existing Git repository in /builds/username_0/omy-project/.git/
  >
  > fatal: unable to access 'https://gitlab.myhost.com:1234/username_0/omy-project.git/': Failed to connect to gitlab.myhost.com port 1234: Operation timed out
  
  I logged to gitlab-runner running server and tried cloning project as `gitlab-runner` user and it worked.
  
  Why am I getting this error?
  
  **Tags:** continuous-integration, gitlab, gitlab-ci-runner
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2021-02-09. Score: 0 | Accepted answer
  
  It was a simple mistake I made when I register `gitlab-runner`. I just used `gitlab-runner register [options]`
  
  But when I register it with `sudo`, it was working properly.
  
  `sudo gitlab-runner register [option]`
  
  Runner is running in `Ubuntu-18.04` server.
  
  
  ---
  
  ### Answer by username_1 on 2021-02-06. Score: 3
  
  This is likely because your requests were dropped before they landed on the GitLab host. Check your firewalls and other security rules after assured that the 1234 port is open
  
  > **Comments:**
  > **username_0**: Port is open and can access to it. Will check and let you know.  
  
  ---
  
  