[SOLVED] Proxmox git clone issue in all VMs

[mahdikhan]

Hi Guys,

I'm fairly new to Proxmox and love the experience so far. I've come across a single issue, which is the "git clone" command is not working in any VMs. The output hangs for a while and then gives the below error:

Command: git clone https://github.com/xxxx/xxxx.git

Error: fatal: unable to access 'https://github.com/xxxx/xxxx.git/': gnutls_handshake() failed: Error in the pull function.

This is happening for all VMs respectively. What should be the resolution for this?
I'm running Proxmox on the Dell Poweredge T130. Currently have 3 VMs and all are having the same issues.

 

[oguz]

hi,

I've come across a single issue, which is the "git clone" command is not working in any VMs.

are these VMs all the same, or do they use different OS/settings?

if it happens in different OS, then i would look for a network issue. otherwise if they're all clones of each other then maybe there's a wrong setting somewhere?

does the error happen on all https sites? or just with github? can you do a curl https://github.com -v

 

[mahdikhan]

Hi, Thanks for the reply. All three VMs are Ubuntu Server based with one being 20.04.3 and the others being 18.04.

The outcome of the command is:
* Trying 20.205.243.166:443...
* TCP_NODELAY set
* Connected to github.com (20.205.243.166) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
.....It gets stuck after this.


But I can curl google https. Seems like it's only GitHub issue.

 

[oguz]

But I can curl google https. Seems like it's only GitHub issue.

okay, then maybe it's a problem on their end. for what it's worth it works fine here (although it resolves to a different IP address for me).

maybe you can check your DNS resolver, clearing the cache might help, or using a different DNS server.

 

[mahdikhan]

Thanks for the suggestion. I think the same as well. Let's wait for a while and I'll update you on the status as well.

 

[mahdikhan]

okay, then maybe it's a problem on their end. for what it's worth it works fine here (although it resolves to a different IP address for me).

maybe you can check your DNS resolver, clearing the cache might help, or using a different DNS server.

Update: It was my router end's issue. I'm running MikroTik for the routing and DNS caching. After upgrading my MikroTik RouterOS to a stable package, the issue is resolved. Thank you for your quick help and suggestions.

 

[oguz]

Update: It was my router end's issue. I'm running MikroTik for the routing and DNS caching. After upgrading my MikroTik RouterOS to a stable package, the issue is resolved. Thank you for your quick help and suggestions.

great, and thanks for posting the solution!

you can also mark the thread as [SOLVED] so others will know before clicking

 

[mahdikhan]

great, and thanks for posting the solution!

you can also mark the thread as [SOLVED] so others will know before clicking

Thanks! Already updated!