While trying to log in to the ArgoCD server from a command-line interface (CLI), the connection attempt may hang for some time and then fail with the error as follows: “FATA[0060] context deadline exceeded“.
This error usually occurs when the ArgoCD instance is setup behind a load balancer or reverse proxy which doesn’t support HTTP2.
Besides of this, the argocd login command may hang for no apparent reason while testing whether the server is configured with TLS.
This short note shows how to resolve these issues.
ArgoCD: FATA[0060] context deadline exceeded
While executing the argocd login command you may receive the error as follows:
$ argocd login <SERVER> - sample output - FATA[0060] context deadline exceeded
To log in to the ArgoCD server, try to add the --skip-test-tls and --grpc-web options:
$ argocd login <SERVER> --skip-test-tls --grpc-web
- sample output -
Username: admin
Password:
'admin:login' logged is successfully
Context <SERVER> updated
If you want to pass credentials on the command-line, this can be done as follows:
$ argocd login <SERVER> --skip-test-tls --grpc-web \
--username <USER> \
--password <PASSWORD>
To log in to the ArgoCD server, try to add the --skip-test-tls and --grpc-web options:
| Option | Description |
|---|---|
--skip-test-tls |
Skip testing whether the server is configured with TLS (this can help when the command hangs for no apparent reason). |
--grpc-web |
Enables gRPC-web protocol. Useful if Argo CD server is behind proxy which does not support HTTP2. |
--username |
The username of an account to authenticate. |
--password |
The password of an account to authenticate. |