Gitlab-runner Interactive Web Terminals not connected

问题

I have installed successfully a gitlab-runner on a VM, and it is used by some of my projects. I would like to use the Interactive Web Terminal to have a chance to debug when some pipeline fails.

I'm trying to configure my config.toml file, following this docu of gitlab but i'm not understanding wich ip addess i should use in the setting listen_address. Should it be the ip of the running machine? The docker container instance? Or what?

Here is my current configuration:

concurrent = 2
check_interval = 0
log_level = "panic"

[session_server]
  listen_address = "0.0.0.0:8093" #  listen on all available interfaces on port 8093
  session_timeout = 1800

[[runners]]
  name = "A test private repo"
  url = "https://gitlab.com/"
  token = "myToken"
  executor = "docker"
  [runners.custom_build_dir]
  [runners.docker]
    tls_verify = false
    image = "alpine:latest"
    privileged = false
    disable_entrypoint_overwrite = false
    oom_kill_disable = false
    disable_cache = false
    volumes = ["/cache"]
    shm_size = 0
  [runners.cache]
    [runners.cache.s3]
    [runners.cache.gcs]
  [runners.custom]
    run_exec = ""

Screen of error i get

I noticed that when i hit the 0.0.0.0:8093 address on the machine where the gitlab-runner is running i get this response:

回答1:

Your configuration should use:

[session_server]
   session_timeout = 1800
   listen_address = "0.0.0.0:8093"
   advertise_address = "<your runner IP/hostname>:8093"

Should it be the ip of the running machine?

Yes

来源：https://stackoverflow.com/questions/57233524/gitlab-runner-interactive-web-terminals-not-connected