Skip to content
GitLab Next
Closed
Created by Ghost User@ghost1Contributor

couldn't execute POST ... dial tcp 127.0.1.1:443: getsockopt: connection refused

Summary

Unable to register runner. Either gitlab-ci-multi-runner or gitlab-runner, are failing to connect to CI API.

Steps to reproduce

askhat@HOST:~$ sudo gitlab-runner register
Please enter the gitlab-ci coordinator URL (e.g. https://gitlab.com/):
https://HOST/ci
Please enter the gitlab-ci token for this runner:
***
Please enter the gitlab-ci description for this runner:
[HOST]: ruby-alpine
Please enter the gitlab-ci tags for this runner (comma separated):

ERROR: Registering runner... failed                 runner=*** status=couldn't execute POST against https://HOST/ci/api/v1/runners/register.json: Post https://HOST/ci/api/v1/runners/register.json: dial tcp 127.0.1.1:443: getsockopt: connection refused
PANIC: Failed to register this runner. Perhaps you are having network problems

Environment description

  • Self-hosted 8.15.4-ee instance on Ubuntu 16.04.1 x64 (kernel 4.4.0-59-generic)
  • Initially installed from DigitalOcean's one-click GitLab app
  • Docker 1.12.6 with aufs storage
  • Certs from Let's Encrypt
  • /etc/gitlab-runner/certs — no such directory
  • Hostname is the same as instance's URL (HOST above)

Used GitLab Runner version

askhat@HOST:~$ gitlab-runner --version
Version:      1.9.3
Git revision: c689d51
Git branch:   1-9-stable
GO version:   go1.7.4
Built:        Sat, 14 Jan 2017 07:46:19 +0000
OS/Arch:      linux/amd64