Databases
StackOverflow2013
Postsdbo
POGit push failing due to company proxy certificate being changed
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGit push failing due to company proxy certificate being changed
    primarykey
    data
    text
    <p>Recently, the certificates for the company proxy was changed. Ever since, I have been facing problems using git. When I try to do a <code>git push</code> , I get the following error:</p> <pre><code>error: gnutls_handshake() failed: The Diffie-Hellman prime sent by the server is not acceptable (not long enough). while accessing https://github.com/me/myproj.git/info/refs fatal: HTTP request failed </code></pre> <p>I could just switch to pushing using HTTP or switching off sslVerify by doing <code>git config --global http.sslVerify false</code> but they insist I use <strong><em>only</em></strong> HTTPS.</p> <p>I have a <em>.cer</em> certificate file which I've been asked to install system wide in my Ubuntu desktop (Ubuntu 12.04) but I have not been able to find a way to do it. Please help !</p> <p>Here is the <em>curl</em> logs I obtained after performing <code>export GIT_CURL_VERBOSE=1</code>:</p> <pre><code>* Couldn't find host github.com in the .netrc file; using defaults * About to connect() to proxy proxy.mycompany.com port 5150 (#0) * Trying 10.226.xx.yyy... * Connected to proxy.mycompany.com (10.226.xx.yyy) port 5150 (#0) * Establish HTTP proxy tunnel to github.com:443 * Proxy auth using Basic with user 'me' &gt; CONNECT github.com:443 HTTP/1.1 Host: github.com:443 Proxy-Authorization: Basic MjQABCD3Og== User-Agent: git/1.7.9.5 Proxy-Connection: Keep-Alive Pragma: no-cache &lt; HTTP/1.1 200 Connection established &lt; Date: Tue, 23 Oct 2012 11:45:37 GMT &lt; Age: 0 &lt; Proxy-Connection: Keep-Alive &lt; Via: 1.0 MYCOMPANYSERVER.MYCOMPANY.COM &lt; * Proxy replied OK to CONNECT request * found 1 certificates in /etc/ssl/certs/cert.crt * gnutls_handshake() failed: The Diffie-Hellman prime sent by the server is not acceptable (not long enough). * Closing connection #0 * Couldn't find host github.com in the .netrc file; using defaults * About to connect() to proxy proxy.mycompany.com port 5150 (#0) * Trying 10.226.xx.yyy... * Connected to proxy.mycompany.com (10.226.xx.yyy) port 5150 (#0) * Establish HTTP proxy tunnel to github.com:443 * Proxy auth using Basic with user 'me' &gt; CONNECT github.com:443 HTTP/1.1 Host: github.com:443 Proxy-Authorization: Basic MjQABCD3Og== User-Agent: git/1.7.9.5 Proxy-Connection: Keep-Alive Pragma: no-cache &lt; HTTP/1.1 200 Connection established &lt; Date: Tue, 23 Oct 2012 11:45:37 GMT &lt; Age: 0 &lt; Proxy-Connection: Keep-Alive &lt; Via: 1.0 MYCOMPANYSERVER.MYCOMPANY.COM &lt; * Proxy replied OK to CONNECT request * found 1 certificates in /etc/ssl/certs/cert.crt * gnutls_handshake() failed: The Diffie-Hellman prime sent by the server is not acceptable (not long enough). * Closing connection #0 error: gnutls_handshake() failed: The Diffie-Hellman prime sent by the server is not acceptable (not long enough). while accessing https://github.com/me/myproject.git/info/refs fatal: HTTP request failed </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. UScodemaniac
    1. UScodemaniac
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGit push failing due to company proxy certificate being changed
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGit push failing due to company proxy certificate being changed
      1. USVonC
      1. VTFavorite
    3. VO
      singulars
      1. POGit push failing due to company proxy certificate being changed
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload