Argo CLI Won't Connect

Issue – CLI Fails to Connect

When using the ArgoCD CLI with the Platform9's ArgoCD-as-a-Service, the CLI may fail to connect and display one of the following error codes.

FATA[0018] rpc error: code = Internal desc = transport: received the unexpected content-type "text/html"

FATA[0002] rpc error: code = Internal desc = transport: received the unexpected content-type "text/html"

FATA[0001] rpc error: code = Unknown desc = unexpected EOF

These issues are likely caused by missing CLI flags.

Solution

To connect the ArgoCLI to Platform9 ArgoCD, the CLI should be configured using two specific flags.

--sso

--grpc-web-root-path

The grpc-web-root-path flag requires the path to the ArgoCD API endpoint. For the Platform9 ArgoCD, that is argocd

argocd login argocd-as-a-service.platform9.io --sso --grpc-web-root-path argocd