publish fails with curl error "Send failure: Connection was reset"
See original GitHub issueI am trying to publish a new repository to github. It was previously a repository with a commit and some files, but I ran into this issue during a commit and reset the repo in an attempt to solve the problem.
When I push in github desktop I get:
"error: RPC failed; curl 56 Send failure: Connection was reset
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date"
I have tried resetting the http.postBuffer
to a large value in git bash (although none of the files are especially large) without success. I have created and pushed a new, empty repo since this problem arose and didn’t have any problems.
I found a similar issue, https://github.com/desktop/desktop/issues/6485, and per a suggestion there ran Go to Repository > Open in command prompt in GitHub Desktop and run the following commands:
set GIT_TRACE=1
set GIT_CURL_VERBOSE=1
git push origin <branch>
The results were:
Host: github.com
Authorization: Basic UGVyc29uYWxBY2Nlc3NUb2tlbjozYTE4Yzk1NzI5YTljOTEzODkxYTYyMmViY2UwNDE1MmJlZWIwOTAy
User-Agent: git/2.26.2.windows.1
Accept: */*
Accept-Encoding: deflate, gzip
Pragma: no-cache
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: GitHub Babel 2.0
< Content-Type: application/x-git-receive-pack-advertisement
< Transfer-Encoding: chunked
< Expires: Fri, 01 Jan 1980 00:00:00 GMT
< Pragma: no-cache
< Cache-Control: no-cache, max-age=0, must-revalidate
< Vary: Accept-Encoding
< X-GitHub-Request-Id: C56E:7765:925EC0:DBF9BE:5EA3800E
< X-Frame-Options: DENY
* Connection #0 to host github.com left intact
18:11:00.387719 run-command.c:663 trace: run_command: 'git credential-manager store'
18:11:00.434529 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
18:11:00.434529 git.c:703 trace: exec: git-credential-manager store
18:11:00.434529 run-command.c:663 trace: run_command: git-credential-manager store
18:11:00.606390 run-command.c:663 trace: run_command: git send-pack --stateless-rpc --helper-status --thin --progress https://github.com/shaunstarbuck/Basic-NLP-.git/ --stdin
18:11:00.606390 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
18:11:00.606390 git.c:439 trace: built-in: git send-pack --stateless-rpc --helper-status --thin --progress https://github.com/shaunstarbuck/Basic-NLP-.git/ --stdin
18:11:00.606390 run-command.c:663 trace: run_command: git pack-objects --all-progress-implied --revs --stdout --thin --delta-base-offset --progress
18:11:00.621984 exec-cmd.c:237 trace: resolved executable dir: C:/Program Files/Git/mingw64/libexec/git-core
18:11:00.621984 git.c:439 trace: built-in: git pack-objects --all-progress-implied --revs --stdout --thin --delta-base-offset --progress
Enumerating objects: 12, done.
Counting objects: 100% (12/12), done.
Delta compression using up to 8 threads
Compressing objects: 100% (11/11), done.
Writing objects: 100% (12/12), 69.88 MiB | 344.04 MiB/s, done.
Total 12 (delta 1), reused 12 (delta 1), pack-reused 0
* Found bundle for host github.com: 0x3766eb0 [serially]
* Can not multiplex, even if we wanted to!
* Re-using existing connection! (#0) with host github.com
* Connected to github.com (140.82.113.3) port 443 (#0)
* Server auth using Basic with user 'PersonalAccessToken'
> POST /shaunstarbuck/Basic-NLP-.git/git-receive-pack HTTP/1.1
Host: github.com
Authorization: Basic UGVyc29uYWxBY2Nlc3NUb2tlbjozYTE4Yzk1NzI5YTljOTEzODkxYTYyMmViY2UwNDE1MmJlZWIwOTAy
User-Agent: git/2.26.2.windows.1
Accept-Encoding: deflate, gzip
Content-Type: application/x-git-receive-pack-request
Accept: application/x-git-receive-pack-result
Content-Length: 73277320
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: GitHub Babel 2.0
< Content-Type: application/x-git-receive-pack-result
< Transfer-Encoding: chunked
< Expires: Fri, 01 Jan 1980 00:00:00 GMT
< Pragma: no-cache
< Cache-Control: no-cache, max-age=0, must-revalidate
< Vary: Accept-Encoding
< X-GitHub-Request-Id: C56E:7765:925F38:DBFB9C:5EA38013
< X-Frame-Options: DENY
* OpenSSL SSL_read: Connection was reset, errno 10054
* Closing connection 0
error: RPC failed; curl 56 OpenSSL SSL_read: Connection was reset, errno 10054
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date
Any help would be appreciated.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
How to recover from curl: (56) Send failure: Connection was ...
Using -C - will only resume from where I left once I issue the command again. If the connection breaks, network cable is...
Read more >Windows Curl Returning (35) Send failure - Stack Overflow
Autodesk Fusion360 had this issue aswell. I believe I have tracked the issue down to curl.exe returning error 35. Command: curl https://google.
Read more >How to fix cURL 56 recv failure connection reset by peer in ...
cURL error 56 is a temporary error that happens due to different reasons like, idle server connection, firewall restrictions, whitespace in the ...
Read more >Tips to Debug CURL with a client - (56) Recv failure
If you ask the customer to curl from outside their firewall they should be able to get to you. The error from curl...
Read more >Error: [] cURL error 7: | WordPress.org
The loopback request to your site failed, this means features relying on them are not currently working as expected. Error: [] cURL error...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I was able to upload the project today, once with the antivirus turned off and again on a duplicate test project with the antivirus turned on. I don’t know if it got unstuck by turning it off and on or what.
My computer is connected by ethernet, but the underlying internet is pretty poor (satellite internet). Could my ISP be throttling uploads to cause this error? If the start of a new billing month was today they may have reset the data cap and no longer be throttling uploads. My upload speed hasn’t changed, at about 1.5 Mbps, so I don’t know. It’s just a thought why the second upload worked with antivirus on. I’ll find out in a few weeks if the same problem reoccurs.
Anyways, thanks a lot for the help!
Thanks. 82MB should work fine in general. I wish the
error: RPC failed; curl 56 Send failure: Connection was reset
error was just more specific.Your antivirus software could be modifying the HTTP packets in transit – I would try disabling it and attempt the push again. Another cause could be the wifi dropping the connection. If you have connection to LAN, that might help too.
Let us know the outcome please.