Gitlab KAS connection issue

Gitlab kubernetes agent is not establishing connection with local gitlab. When I checked the logs only log I see is

kubectl logs -f gitlab-agent-547b7984cd-r4q5q -n gitlab-kubernetes-agent
{“level”:“info”,“time”:“2022-01-21T13:47:32.279Z”,“msg”:“Feature status change”,“feature_name”:“tunnel”,“feature_status”:true}
{“level”:“info”,“time”:“2022-01-21T13:47:32.279Z”,“msg”:“Observability endpoint is up”,“mod_name”:“observability”,“net_network”:“tcp”,“net_address”:"[::]:8080"}

thats it. no other logs are getting emitted

this is agent deployment arg

  • args:
    - --token-file=/config/token
    - --kas-address
    - wss://

gitlab config for kas:
Enable GitLab KAS
gitlab_kas[‘enable’] = true

##! Listen configuration for GitLab KAS
gitlab_kas[‘listen_address’] = ‘’

1 Like

Did you ever fix this? I found this to be frustratingly impossible to debug.

I had this issue as well.

In my case I was running GitLab Omnibus on my own server, using docker and running behind a Traefik reverse proxy.

According to the troubleshooting information here:

Right at the bottom it speaks of checking the gitlab-kas logs (<GITLAB_ROOT>/logs/gitlab-kas/current) and about this message showing up:

{"level":"error","time":"2021-08-16T14:56:47.289Z","msg":"GetAgentInfo()","correlation_id":"01FD7QE35RXXXX8R47WZFBAXTN","grpc_service":"gitlab.agent.reverse_tunnel.rpc.ReverseTunnel","grpc_method":"Connect","error":"Get \"\": dial tcp connect: connection refused"}

Which I had, and seems to be because of the reverse proxy terminating the SSL certificate.

The resolution was to add this option to the /etc/gitlab/gitlab.rb file with your domain:

gitlab_kas['gitlab_address'] = ''

Note that there is no S in http, this is what fixed it for me