Troubleshooting

To troubleshoot connection issues with Gateway,

• Login to Twingate client and sync the Kubernetes configuration if Auto Sync is not enabled.
• Switch kubectl current context to the context added by Twingate.
  • Run kubectl config view --minify --output yaml to print the configuration of the current context.
• Run kubectl auth whoami to check if the connection is working.
• Check the Gateway log for any errors.
  • If there is no log at all, it means the executed kubectl command never reached the Gateway. See Connector fails to connect to the Gateway.
• Check the Kubernetes resource's network events in Twingate Admin Console.

Connector fails to connect to the Gateway

Symptoms

• When running kubectl auth whoami, you get an error message:

E0728 11:28:58.794311   10416 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: 
Get \"https://my-k8s-cluster.int/api?timeout=32s\": read tcp 100.96.0.2:51459->100.109.236.181:443: read: connection 
reset by peer - error from a previous attempt: read tcp 100.96.0.2:51458->100.109.236.181:443: read: connection reset by peer"

Diagnosis

• In Twingate Admin Console, check the Kubernetes resource for its network event. If the Connector fails to connect to the Gateway, you should see a "DNS lookup failed" event.
• There is no logs in the Gateway pod.

Possible causes

• Some Connectors are deployed outside the Kubernetes cluster but the Gateway is deployed with a ClusterIP service (the default configuration).
  • In the default setup using ClusterIP, the Gateway is only accessible to a Connector deployed inside the cluster. If you have a Connector (in the same Remote Network) deployed outside the Kubernetes cluster, you need to use a LoadBalancer or NodePort service to expose the Gateway to the Connector.
• The resource's Gateway address is entered inaccurately and hence not resolvable by the Connector.

Client configuration

~/.kube directory doesn't exist

If ~/.kube isn't present on the machine, the Twingate Client configuration sync will not work.

To resolve, create the ~/.kube directory. After this, the configuration sync should succeed.