Git on Windows not working with remote because of "SSL protocol" errors -
tl;dr
git on windows stops connecting github because of mysterious "ssl protocol" errors. halp!
the issue
i'm developing on windows, using private github repo source control. when first boot system, i'm able access remote repo without issue - pull, push, fetch, etc. work fine.
after amount of time(*), stops, , following error:
fatal: unable access 'https://github.com/our-team/private-repo.git/': unknown ssl protocol error in connection github.com:443
(*) amount of time seems variable - i've witnessed little hour or two, whole day. after coming system sleeping, seems issue, don't know if it's caused time delay or system sleeping.
checking via curl, get
λ curl -v "https://github.com/our-team/private-repo.git/" * trying 192.30.252.130... * connected github.com (192.30.252.130) port 443 (#0) * set certificate verify locations: * cafile: c:\program files (x86)\git\bin\curl-ca-bundle.crt capath: none * tlsv1.0, tls handshake, client hello (1): * unknown ssl protocol error in connection github.com:443 * closing connection 0 curl: (35) unknown ssl protocol error in connection github.com:443 using set git_curl_verbose=1 git pull shows similar information. succeeds (see below), of time fails.
further notes
there's little bit of sporadic nature - can requests succeed, once starts exploding, it's broken 9 out of 10 requests or more.
a successful curl request looks like:
λ curl -v "https://github.com/our-team/private-repo.git/" * trying 192.30.252.130... * connected github.com (192.30.252.130) port 443 (#0) * set certificate verify locations: * cafile: c:\program files (x86)\git\bin\curl-ca-bundle.crt capath: none * tlsv1.0, tls handshake, client hello (1): * tlsv1.0, tls handshake, server hello (2): * tlsv1.0, tls handshake, cert (11): * tlsv1.0, tls handshake, server finished (14): * tlsv1.0, tls handshake, client key exchange (16): * tlsv1.0, tls change cipher, client hello (1): * tlsv1.0, tls handshake, finished (20): * tlsv1.0, tls change cipher, client hello (1): * tlsv1.0, tls handshake, finished (20): * ssl connection using tlsv1.0 / aes128-sha * server certificate: * subject: businesscategory=private organization; 1.3.6.1.4.1.311.60.2.1.3=us; 1.3.6.1.4.1.311.60.2.1.2=delaware; serialnumber=5157550; street=548 4th street; postalcode=94107; c=us; st=california; l=san francisco; o=github, inc.; cn=github.com * start date: 2014-04-08 00:00:00 gmt * expire date: 2016-04-12 12:00:00 gmt * subjectaltname: github.com matched * issuer: c=us; o=digicert inc; ou=www.digicert.com; cn=digicert sha2 extended validation server ca * ssl certificate verify ok. > /our-team/private-repo.git/ http/1.1 > user-agent: curl/7.41.0 > host: github.com > accept: */* > < http/1.1 301 moved permanently < server: github.com < date: mon, 11 may 2015 15:19:43 gmt < content-type: text/html < content-length: 178 < location: https://github.com/our-team/private-repo/ < vary: accept-encoding < x-served-by: 76f8aa18dab86a06db6e70a0421dc28c < <html> <head><title>301 moved permanently</title></head> <body bgcolor="white"> <center><h1>301 moved permanently</h1></center> <hr><center>nginx</center> </body> </html> * connection #0 host github.com left intact the question
i've googled bit on trying find (over course of several weeks, don't have links), suggestions seem point @ certificate errors or openssl version mismatches / bugs (which wouldn't sporadic afaik).
what might causing failure, , how can resolve it?
relevant software:
λ git --version git version 1.9.5.msysgit.1 λ curl --version curl 7.41.0 (i386-pc-win32) libcurl/7.41.0 openssl/0.9.8zf zlib/1.2.8 protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp features: asynchdns ipv6 largefile sspi kerberos spnego ntlm ssl libz
oddly, turns out issue laptop throttled because of weak power supply. docking station using plugged low-amp powersupply (3.3 a), which, while compatible laptop, kicked heavily-throttled mode.
apparently, slowed down enough ssl handshake wasn't able complete fast enough.
we finally tracked down after reading dell support forum post (http://en.community.dell.com/support-forums/laptop/f/3518/t/19363340) discussed slowness issues. solution there change power supply.
i had experienced slowness, did not think related. swapped high-amp power supply dock, , fine again, , ssl errors described above went away.
Comments
Post a Comment