Runner is not activated after registering

I created project on server instance with GitLab ver. 13.2.9-ee.
Also registered specific runner ver. 13.4.1 , running on my build-machine .

File config.toml was generated :

concurrent = 1
check_interval = 0

session_timeout = 1800

name = “ValRunnerBM08”
url = “https://[our GitLab server].org/”
token = “[some token]”
executor = “docker-windows”
host = “tcp://”
tls_verify = false
image = “my/public_repo_in_docker_hub:my_image_win1909”
privileged = false
disable_entrypoint_overwrite = false
oom_kill_disable = false
disable_cache = false
volumes = [“c:\cache”]
shm_size = 0

Runner appeared on GitLab interface ( in my account as owner) in state “Pause”.
Any manipulations with buttons did not help, I cannot activate it.
IP Address is not defined ( .
Command ‘gitlab-runner.exe health-check’ gives ‘FATAL: No HOST or PORT found’
Command ‘gitlab-runner.exe --debug run’ gives
‘listen_address not defined, metrics & debug endpoints disabled builds=0
[session_server].listen_address not defined, session endpoints disabled builds=0’
I would appreciate any help to fix the problem .

1 Like

Exact same problem. Found a fix?
I’ve been trying to provide a host/port in config.toml but not sure I’m doing it right.

Tried different ports. FATAL: No HOST or PORT still shows on health-check, but gitlab was able to run the job.

Yes, GitLab runner is able to run the job even in it’s state ‘Pause’.
Looks like it’s just different behavior of runner after GitLab was updated on our instance.