argoproj / argo-cd

Declarative Continuous Deployment for Kubernetes
https://argo-cd.readthedocs.io
Apache License 2.0
18.01k stars 5.49k forks source link

"remote error: tls: unrecognized name" when adding git repository #20598

Open tgkul opened 3 weeks ago

tgkul commented 3 weeks ago

Discussed in https://github.com/argoproj/argo-cd/discussions/20597

Originally posted by **tgkul** October 30, 2024 Hi, I recently setup my Kubernetes cluster and deployed Rancher, Cert Manager and then Argo CD. I have a Next JS web app that I want to deploy to my Kubernetes cluster using Argo CD. The problem I am facing is with adding git repository in Argo CD. For both public and private repositories on Github and Gitlab, I get following error - ``` > argocd repo add https://gitlab.com/gitlab-org/gitlab.git --loglevel debug --logformat json {"level":"warning","msg":"Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web.","time":"2024-10-30T18:58:55+05:30"} {"level":"fatal","msg":"rpc error: code = Unknown desc = error testing repository connectivity: Get \"https://gitlab.com/gitlab-org/gitlab.git/info/refs?service=git-upload-pack\": remote error: tls: unrecognized name","time":"2024-10-30T18:58:55+05:30"} ``` I can get rid of grpc call error by using --grpc-web flag. It's the second error I am not able to fix. Here is my setup: image Just out of curiosity I tried running git clone on argocd-server pod but it failed for `gnutls_handshake() failed: The server name sent was not recognized`. I am not even sure if this is supposed to succeed or fail. ``` argocd@argocd-server-78c87b9bb6-4v2fc:~$ git clone https://github.com/argoproj/argo-cd.git Cloning into 'argo-cd'... fatal: unable to access 'https://github.com/argoproj/argo-cd.git/': gnutls_handshake() failed: The server name sent was not recognized ``` Can someone help me figure out what I am doing wrong? Let me know if you need more information. I am running out of options.
andrii-korotkov-verkada commented 2 weeks ago

Looks like some DNS or network permissions issue.