Eclipse EGit "cannot open git-upload-pack" error message

Hi all,

I've been using Gitlab without problems for a couple of months now. But, since last week, I can suddenly not "reach" (fetch, push,...) Gitlab from my Eclipse IDE anymore.

I get the following error message:

https://gitlab.com/XXX/XXX.git: cannot open git-upload-pack

Looking at my Eclipse log file, the cause is:
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    at sun.security.ssl.Alerts.getSSLException(Unknown Source)
    at sun.security.ssl.Alerts.getSSLException(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
    at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
    at java.net.HttpURLConnection.getResponseCode(Unknown Source)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)
    at org.eclipse.jgit.transport.http.JDKHttpConnection.getResponseCode(JDKHttpConnection.java:98)
    at org.eclipse.jgit.util.HttpSupport.response(HttpSupport.java:168)
    at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:460)
    ... 10 more

The problem has apparently nothing to do with a bad proxy configuration (no proxy configuration at home...). I tried http.sslVerify=false in my Eclipse/Git configuration but it does not help.

Moreover I found another problem. When I'm logged in my gitlab.com space, if I go to my project page and try to download it as a zip, I got a 16Mb file the first time. But now, when I try again I only get a 1Mb file back, whatever branch I try to download.

So I was wondering if these connection and download problems could result of a configuration change on the gitlab.com web server side ?

Kind regards,

Laurent

I get the same error in NetBeans, I tried generating a new SSH key and using SSH settings but did not work, this occurred only gitlab repositories I could only do push/pull/clone from bash command line

Kind regards, Javier

I first post a topic about this problem on stackoverflow and got the same feedback:

http://stackoverflow.com/questions/26066993/gitlab-cannot-open-git-upload-pack-error

I haven't got any error with Sublime Text with sidebargit plugin, but my collaborator has the same problem with Eclipse since last week.

I'm new to bitlab but i get the same error message when I try to use it with eclipse :(

Same error message in Eclipse! Kepler and Luna

• Double checked my public/private key and added the key to my GitLab profile.
• Double checked that my user.name and user.email are the same as on GitLab.
• Tried http.sslVerify=false which is not solving this problem.

Same error message here also in Eclipse. Using Kepler

same in Android Studio (IntelliJ)

same in Eclipse Luna 4.4.0, Windows 8.1 .. anyone got some luck with that? are they fixing it?

I'm having the same in eclipse 8.0.1. Started on last week of september.

I've encountered a similar error with another Gitlab server. I dug into it and discovered that all of the available ciphers on the server were at least 256 bits. Standard Oracle Java ships with crypto that's restricted to 128 bits for some algorithms. After installing the unlimited strength crypto package from Oracle the issue went away. Note that the unlimited strength package is only legally available in the US. If you're outside of the US then I think that OpenJDK will work instead.

Just tried John's suggestion and it works for WebStorm. Many thanks

John, you're awesome! Just replaced the "local_policy.jar" and "US_export_policy.jar" and it works! and I'm not from US. Many thanks!! wish Gitlab would post a guide about this instead of us getting all crazy..

Many thanks John! It works for NetBeans

Status changed to closed

I guess this is safe to be closed then? If not, ping me and I'll reopen it :)

I tweeted about this https://twitter.com/gitlabhq/status/519471592632750081

This is fixed with this commit and will be released in 7.4.

Status changed to reopened

Sorry to bring this issue back on the scene but, since yesterday, I'm facing the problem again and can not push my work anymore...

I get the following error message in my Eclipse log: Caused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair ... Caused by: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive) ...

Since the weekend we're using HA proxy in front of the app servers and the app servers themselves might have different ssh settings. @jacobvosmaer can you look into this?

@sytses @jacobvosmaer Here is a nice article how GitHub is doing. http://www.anchor.com.au/blog/2009/10/load-balancing-at-github-why-ldirectord/ Maybe this has changed but it describes their rationales.

@llemoux are you using HTTPS or SSH to access your Git repository?

@sytses the SSH settings on the workers are identical to before, and HAproxy does not 'speak' SSH. The HTTPS connection to gitlab.com has changed though, because all clients now talk to HAproxy instead of NGINX, and HAproxy does 'speak' HTTPS. Or more technically: our HAproxy forwards SSH on layer 4, but HTTPS on layer 7.

I noticed this on https://www.ssllabs.com/ssltest/analyze.html?d=gitlab.com&s=54.93.71.23 :

So gitlab.com HTTPS stopped supporting Java 6 this weekend. I will drop the DH parameters to 1024.

@razer6 we considered LVS (which your blog post is about) but decided against it because it depends on your network infrastructure if and how you can deploy it. Not a good fit for AWS nor for our enterprise customers.

@llemoux Java 6 HTTPS access should be working again on gitlab.com.

Thanks for the quick answer. I'm indeed using https and Java 6. And I confirm it's now working again.

Status changed to closed

Mentioned in issue gitlab-com/infrastructure#599

marked this issue as related to omnibus-gitlab#2666 (closed)