I have encountered this problem recently and I have never been able to find a coherent explanation or solution.
When attempting to push a specific branch to github, I am receiving the following error:
client_loop: send disconnect: Connection reset by peer
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
I am able to push other branches fine, so it cannot be a network error.
I vaguely remember in the past getting an error like this when I mistakenly included something like an auth token in the code. However, that is not the case here.
I am also not pushing any particularly large files (except maybe package-lock.json?)
How I can I find out more about what is causing github to reject my push?
Update
After a dozen tries over about 20 minutes the push was finally accepted. I am still curious whether there is an explanation.
I suppose there could be a number of reasons for this to occur, but in my case it was some issue on our VPN. I encountered the issue again today, hopped off the VPN and pushed again, and it immediately worked.
There is simple solution for this. Go to git bash and just follow the steps,
(1) vim .ssh/config
(2) insert- ServerAliveInterval 60
(3) close vim by Esc ---> ZZ
Related
I am running on a Windows 10 machine and want to install the flutter to my PC. Upon following the first step to install it I've been keeping stuck by this error. I thought re doing it would just get it over, but yeah no. it keeps on getting the error again. Could I get someone to solve this ?
remote: Enumerating objects: 289848, done.
error: 5920 bytes of body are still expected0 MiB | 29.00 KiB/s
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: index-pack failed
pls check here this is the msg I've been getting
Have you write rights on that location?
Does it work when you download the zip file from here https://flutter.dev/docs/get-started/install/windows and extract it in that folder? (note: if the context for admin rights pops up, it means you dont have write rights in there and you should activate the powershell with admin rights in the future)
First off, try instead using the Git desktop application. This will make it easier for you, as long as you don't need to do anything too complex on git, besides just cloning, pulling, pushing and merging with a master branch.
https://desktop.github.com/
Second, this is not an issue with flutter, this sounds like it might be a firewall issue. Do you by any chance have any antivirus software running that could be blocking the connection?
If that's the case for example, if you are running with AVG, just turn off the internet security option, then you should be able to clone the repo.
I am having issues pushing my latest commits for an UE4 project. The commit contains a huge number of changed or added files.
Github Error when pushing:
fatal: the remote hung up unexpectedly.
error RPC failed; curl 55 send failure: Connection was aborted.
Everything up-to-date
I would like some advice how I should go forward with this issue. Will it work to upload the entire update as a new repository or branch or could it be solved in a better way? There is weeks of work done since the last commit so it is important that no information gets lost.
Image of the error:
https://i.imgur.com/NZWPlnI.png
Tried to increase post buffer size for uploading, with git config command: http.postBuffer 524288000
the same issue persisted even after this.
I would like the commit to be pushed or uploaded in any way possible. This is my first post on Stack overflow and I would be very grateful for any help or advice I may get regarding this issue.
I'm using Eclipse Kepler and connect to SVN via VPN. Sometimes VPN connection drops and when I try do do commit without connection I have to wait for 10 minutes until timeout.
The SVN console shows:
commit -m "...comment..." -N ...file_list...
org.apache.subversion.javahl.ClientException: Connection timed out
svn: Commit failed (details follow):
svn: Unable to connect to a repository at URL 'http://192.168.9.2:81/svn/...'
svn: Connection timed out
Why it takes 10 minutes to get timeout? How can I change it?
EDIT:
Maybe it is related to network routing problem. With VPN is disconnected ping 192.168.9.2 gets timeout instead of unreachable host.
(If you're connecting to your SVN using http protocol) Try setting the http-timeout property in ([global] or relevant server-group section of the) servers file in your subversion home (at %APPDATA%\Subversion\servers on Windows) to a low enough value (in seconds - say like 30), so that subversion realizes the connection is kaput sooner, and causes an error message pop-up!
(By default, bottom of) The file should looks something like this:
[global]
http-timeout = 30
History:
I also had issues with work VPN every now and then, and google took me to this old question. #lhasadad commented that he posted an answer but I couldn't see one (I don't know if this method did not work for him, or why the post was deleted, but I could confirm that it still works! (that is, it makes the handling of connection issue better)). Unfortunately that forum link is also giving 404 atm. So I dived into wayback machine and found a copy from April 2016! Credits go to "stefan", a moderator of that forum. He also mentions (if you have Tortoise), this servers file can be opened by "Settings\Network[Edit]" in that GUI.
Anyone else recently experiencing problems pushing to GitHub repos? I keep receiving errors when I try:
error: RPC failed; result=35, HTTP code = 0
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
or
fatal: unable to access 'https://github.com/sr-murthy/TPP.git/': Server aborted the SSL handshake
Is this some kind of DDoS attack?
This error may be because of the open ssl site down.
Please do operation Once again? If you still facing issue You can disable the sslVerfication for you Debugging Purpose.so that you may come to some conclusion.
Change it in User Settings like http.sslVerify=false (If you are using eclipse window--?Preferences-->git-->configuration-->User Settings)
Hope someone will be be able to help: I've installed GitLab and for a few days it seems that worked ok (I could push and pull only from a client but not from the machine that runs GitLab itself), however that's no longer the case. I have been working on the server (its my own server that I've setup for development/learning/personal stuff but I don't believe I've changed anything that could affect Gitlab, so I'm don't know what to do.
At the moment I can't push or pull from either my local machine (OS X 10.8.3) not from my server (Ubuntu 12.0.4). I've run the test several times and all is green. When I do git config user.name or git config user.email it comes back with my name and email respectively. I've also searched online but couldn't find anyone in exactly the same situation, however I did try many of the approaches suggested: I've deleted and generated more ssh keys, changed config in /home/git/gitlab/config.yml to reflect my setup (I'm running apache). My GitLab is 5.2 and I've followed the instruction on GitLab's homepage. In order to make it working with apache instead of nginx I've followed the instructions here:. This question seems the closest to describe my problem, however the solution is not clearly described, so I couldn't follow. The web ineterface works fine and I can commit either from my local machine (using sshfs) and my server. I just can't push or pull. The error I get is:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
I'd appreciate any help. I've been struggling with this for days now and I'm on the brink of give GitLab up...
Many thanks
EDIT: On my server I've got three accounts: user1 (main, first user, root), user2 a sudoer that also has admin privileges and git which also is a sudoer. After more investigating, I'm pretty sure this is a problem of me messing up with permission and the ssh key. Can someone point me out: when I generate the ssh key, which user should I be logged in as? In which computer should I generate this key? On my server or my Mac? Also, when I've tried push from my server directly (I was physically logged in the server rather than sshed to server via my Mac) GitLab was asking for git's password. I then generated a key logged as git on the server and added to GitLab through the web interface and the error appeared again (the same as before). Still not fixed.
The problem in my case was that I changed the git credentials on my local machine (when you create a new repo, you set the user name and email Git and git#localhost respectively) that I had changed and didn't realise. That's why every time I was trying to either push or pull I got the error. Once that was changed back to the correct settings, Gitlab started working again. Leaving as it might be helpful to someone.