Certificate is valid for m169-571.powervow.com, not gitlab.castris.com

Hi.

On my own installation of GitLab11.7.0-ee (c02f0d4) try install gitlab-runner

After install, try register my first shared runner.

gitlab-runner register
Runtime platform                                    arch=amd64 os=linux pid=1472 revision=8bb608ff version=11.7.0
Running in system-mode.

Please enter the gitlab-ci coordinator URL (e.g. https://gitlab.com/):
https://gitlab.castris.com/
Please enter the gitlab-ci token for this runner:
zBTcN59V-YKsphTF71M9
Please enter the gitlab-ci description for this runner:
[gitlab]: Test runner
Please enter the gitlab-ci tags for this runner (comma separated):
test
ERROR: Registering runner... failed                 runner=zBTcN59V status=couldn't execute POST against https://gitlab.castris.com/api/v4/runners: Post https://gitlab.castris.com/api/v4/runners: x509: certificate is valid for m169-571.powervow.com, not gitlab.castris.com
PANIC: Failed to register this runner. Perhaps you are having network problems

Well,

  1. My server has a valid certificated https://gitlab.castris.com/ && https://gitlab.castris.com/api/v4/runners
  2. Also I tried to search “m169-571.powervow.com” . on any file on server, but I don’t see anything.

After some hours…

No matter how many laps I give, I only see a great lack of information in which nobody makes the procedure clear.

In principle, it seems as simple as installing the package, and registering the first shared runner.

But then one advances in several different sections of the doc, and begins to see that there are many more variables.

Well, I see the gitlab-runner configuration file in .toml format and see its documentation https://docs.gitlab.com/runner/configuration/advanced-configuration.html

Ohh … it seems to indicate that there are many things to do that were not indicated in the “install quickly and use gitlab-runner”

I check and I’m testing …

I tell him to listen to the interface, I indicate the address and port

concurrent = 4
check_interval = 0
log_level = "debug"

[session_server]
  listen_address = "176.31.31.225:8093"
  advertise_address = "gitlab.castris.com:8093"
  session_timeout = 1800

Both listen_address and advertise_address should be provided in the form of host:port, where host may be an IP address (e.g., 127.0.0.1:8093) or a domain (e.g., my-runner.example.com:8093). The Runner will create a TLS certificate automatically to have a secure connection.

Make a systemctl restart gitlab-runner but I done see gitlab-runner create a certicficate an issues continue.

In my life I had felt so utterly useless. Not even in Tomcat’s early years … I still try to compose. I will continue reading and reading …