I am getting an error when I am pushing a changeset to bitbucket. I have been able to push slightly smaller changesets previously, like around 250MB, without any issues. I am not anywhere near max capacity on the account, got like 9GB left from the premium starter size.
$ git push
Enumerating objects: 1813, done.
Counting objects: 100% (1813/1813), done.
Delta compression using up to 24 threads
Compressing objects: 100% (1698/1698), done.
Writing objects: 100% (1698/1698), 319.07 MiB | 175.38 MiB/s, done.
Total 1698 (delta 989), reused 0 (delta 0), pack-reused 0
error: RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date
I have tried switching to tls 1.2 as I have seen in other posts, however when I run with a trace it still seem to use 1.3
22:46:43.651805 http.c:774 == Info: OpenSSL SSL_read: Connection was reset, errno 10054
22:46:43.651805 http.c:774 == Info: Failed receiving HTTP2 data
22:46:43.651805 http.c:774 == Info: Connection died, retrying a fresh connect(retry count: 1)
22:46:43.651805 http.c:774 == Info: Closing connection 0
22:46:43.652805 http.c:774 == Info: Issue another request to this URL: 'https://saasktp-admin@bitbucket.org/saasktp/mech.git/git-receive-pack'
22:46:43.652805 http.c:774 == Info: NTLM-proxy picked AND auth done set, clear picked!
22:46:43.652805 http.c:774 == Info: Hostname bitbucket.org was found in DNS cache
22:46:43.652805 http.c:774 == Info: Trying 2406:da00:ff00::22c2:513:443...
22:46:43.700816 http.c:774 == Info: Connected to bitbucket.org (2406:da00:ff00::22c2:513) port 443 (#1)
22:46:43.700816 http.c:774 == Info: ALPN, offering h2
22:46:43.700816 http.c:774 == Info: ALPN, offering http/1.1
22:46:43.706817 http.c:774 == Info: successfully set certificate verify locations:
22:46:43.706817 http.c:774 == Info: CAfile: d:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
22:46:43.706817 http.c:774 == Info: CApath: none
22:46:43.706817 http.c:774 == Info: SSL re-using session ID
22:46:43.706817 http.c:774 == Info: TLSv1.3 (OUT), TLS handshake, Client hello (1):
22:46:43.767831 http.c:774 == Info: TLSv1.3 (IN), TLS handshake, Server hello (2):
22:46:43.767831 http.c:774 == Info: TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
22:46:43.767831 http.c:774 == Info: TLSv1.3 (OUT), TLS handshake, Client hello (1):
22:46:43.819842 http.c:774 == Info: TLSv1.3 (IN), TLS handshake, Server hello (2):
22:46:43.820843 http.c:774 == Info: TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
22:46:43.820843 http.c:774 == Info: TLSv1.3 (IN), TLS handshake, Finished (20):
22:46:43.820843 http.c:774 == Info: TLSv1.3 (OUT), TLS handshake, Finished (20):
22:46:43.820843 http.c:774 == Info: SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
22:46:43.820843 http.c:774 == Info: ALPN, server accepted to use h2
22:46:43.820843 http.c:774 == Info: Server certificate:
22:46:43.820843 http.c:774 == Info: subject: businessCategory=Private Organization; jurisdictionC=US; jurisdictionST=Delaware; serialNumber=3928449; C=US; ST=California; L=San Francisco; O=Atlassian, Inc.; OU=Bitbucket; CN=bitbucket.org
22:46:43.820843 http.c:774 == Info: start date: Mar 27 00:00:00 2020 GMT
22:46:43.820843 http.c:774 == Info: expire date: May 23 12:00:00 2022 GMT
22:46:43.820843 http.c:774 == Info: subjectAltName: host "bitbucket.org" matched cert's "bitbucket.org"
22:46:43.820843 http.c:774 == Info: issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 Extended Validation Server CA
22:46:43.820843 http.c:774 == Info: SSL certificate verify ok.
22:46:43.820843 http.c:774 == Info: Using HTTP2, server supports multi-use
22:46:43.820843 http.c:774 == Info: Connection state changed (HTTP/2 confirmed)
22:46:43.820843 http.c:774 == Info: Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
22:46:43.820843 http.c:774 == Info: Server auth using Basic with user 'saasktp-admin'
22:46:43.820843 http.c:774 == Info: Using Stream ID: 1 (easy handle 0x20b10dfa538)
22:46:43.820843 http.c:721 => Send header, 0000000339 bytes (0x00000153)
22:46:43.820843 http.c:733 => Send header: POST /xxx/xxx.git/git-receive-pack HTTP/2
22:46:43.820843 http.c:733 => Send header: Host: bitbucket.org
22:46:43.820843 http.c:733 => Send header: authorization: Basic c2Fhc2t0cC1hZG1pbjpEIW4wU2F1cmhlcnJpbmc=
22:46:43.820843 http.c:733 => Send header: user-agent: git/2.31.1.windows.1
22:46:43.820843 http.c:733 => Send header: accept-encoding: deflate, gzip, br, zstd
22:46:43.820843 http.c:733 => Send header: content-type: application/x-git-receive-pack-request
22:46:43.820843 http.c:733 => Send header: accept: application/x-git-receive-pack-result
22:46:43.820843 http.c:733 => Send header: content-length: 1642374026
22:46:43.820843 http.c:733 => Send header:
22:46:43.861852 http.c:774 == Info: TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
22:46:43.861852 http.c:774 == Info: old SSL session ID is stale, removing
22:46:43.861852 http.c:774 == Info: Connection state changed (MAX_CONCURRENT_STREAMS == 200)!
22:48:57.735605 http.c:774 == Info: OpenSSL SSL_read: Connection was reset, errno 10054
22:48:57.735605 http.c:774 == Info: Failed receiving HTTP2 data
22:48:57.735605 http.c:774 == Info: OpenSSL SSL_write: Connection was reset, errno 10054
22:48:57.735605 http.c:774 == Info: Failed sending HTTP2 data
was reset
22:48:57.735605 http.c:774 == Info: Connection #1 to host bitbucket.org left intact
error: RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date
I was able to push my changes using GitKraken instead. Seems like the Git Bash package for win10-64 is broken.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.