Problem Description:
the following error is reported during git push:
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
Solution steps:
simple solution (restore to HTTP 2 later):
git config --global http.version HTTP/1.1
git push
git config --global http.version HTTP/2Crime scene
When using git to push the local code to the remote warehouse, the push fails (using the HTTP protocol). The error message is as follows:
$ git push
Enumerating objects: 3383, done.
Counting objects: 100% (3383/3383), done.
Delta compression using up to 8 threads
Compressing objects: 100% (1216/1216), done.
Writing objects: 100% (3383/3383), 6.96 MiB | 81.92 MiB/s, done.
Total 3383 (delta 2303), reused 3007 (delta 2034), pack-reused 0
error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date
Solution:
The data size of this push is 17m.
1. To solve the problem from the perspective of GIT, you can add the size of http.postBuffer
git config http.postBuffer 524288000
2. Because my Gitlab service is using Nginx as a domain proxy, it is possible that the client_max_body_size of nginx is limited and can be adjusted as follows.
client_max_body_size 1024m;
Git push origin XXX error proxy connect aborted
Let’s first analyze the problem. The error prompt is obvious. The proxy connection is aborted. What causes it
at the beginning, without saying a word, baidu directly. After various operations, cancel the agent, set the agent, cancel again, and try again?It’s useless. It still reports an error, but the initial timeout error has become proxy connect aborted
it’s hard for me. I’ve been working all day. When it’s time to submit, give me the whole deal?Is this the law that problems must happen before work. Hey, I can’t continue the whole process. I’ve seen various methods on the Internet. The original solution is as follows:
It turns out that there is no separate proxy configured for GIT. Configure proxy for git:
git config — global http.proxy‘ http://127.0.0.1:1087 ’
git config –global https.proxy ‘ socks://127.0.0.1:1080 ’
However, I’m sorry, it’s no use. It’s still wrong. But this operation reminds me that I haven’t checked the GIT configuration of my own project.
Solution:
Next is the moment to witness miracles
1. The questions are as follows:
echigh@huangchenggong:/mnt/e/work/workspace/withdraw_validdata_from_file/withdraw$ git push -u origin main
Username for 'https://github.com': echigh
Password for 'https://[email protected]':
To https://github.com/echigh/withdraw_frontbytes_of_file.git
! [rejected] main -> main (fetch first)
error: failed to push some refs to 'https://github.com/echigh/withdraw_frontbytes_of_file.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.2. The reason is that the remote warehouse has been changed and does not match any local commit version
Reference: [status question] why can’t you push it up sometimes… – learn git for yourself
3. Solution:
1) Merge remote changes with git pull before git push
2) Directly use git push – F to forcibly overwrite the remote warehouse. Anyway, I dare not
4. So I did this:
echigh@huangchenggong:/mnt/e/work/workspace/withdraw_validdata_from_file/withdraw$ git pull
remote: Enumerating objects: 22, done.
remote: Counting objects: 100% (22/22), done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 21 (delta 13), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (21/21), 5.03 KiB | 66.00 KiB/s, done.
From https://github.com/echigh/withdraw_frontbytes_of_file
c6d3d5e..e50b1bc main -> origin/main
Merge made by the 'recursive' strategy.
README.md | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
create mode 100644 README.mdThen push:
echigh@huangchenggong:/mnt/e/work/workspace/withdraw_validdata_from_file/withdraw$ git push
Username for 'https://github.com': echigh
Password for 'https://[email protected]':
Enumerating objects: 44, done.
Counting objects: 100% (42/42), done.
Delta compression using up to 8 threads
Compressing objects: 100% (38/38), done.
Writing objects: 100% (38/38), 3.16 MiB | 994.00 KiB/s, done.
Total 38 (delta 19), reused 0 (delta 0)
remote: Resolving deltas: 100% (19/19), completed with 2 local objects.
To https://github.com/echigh/withdraw_frontbytes_of_file.git
e50b1bc..b7684a5 main -> maingit push Error: unpacker error 000000000000
Problem cause: there is a problem with Chinese characters in the commit content
how to modify:
git commit --amend
Delete the Chinese content of the commit and write it again
report errors:
error: src refspec v3.3.04.1000 matches more than one.
Error reporting reason: the branch name is the same as the tag name.
So delete the remote tag and push the code.
Delete local tag v3.3.04.1000
git tag -d v3.3.04.1000
Delete remote Tag v3.3.04.1000
git push origin :refs/tags/v3.3.04.1000
An error was reported when pushing the code to GitHub today:
the reason is that GitHub does not support the password authentication scheme, so use personal access token instead.
Solution
Generate token on GitHub
Settings -> Developer Settings -> Personal Access Token -> Generate New Token -> Check – > Click generate token – > Copy the generated token
Change the local certificate to personal access token
Control panel – > Credential manager – > Windows credentials – > Locate git: https://github.com , just change the credentials to the previously generated token.
For other platforms, please refer to support for password authentication was removed. Please use a personal access token instead [duplicate]
Reason: the file size is too large and cannot exceed 100m
1. Check which file exceeds 100m
git rev-list --objects --all | grep xxx
2. Remove from cache
git filter-branch --tree-filter 'rm -f xxx' --tag-name-filter cat -- --all
XXX represents the file name returned in the first step
In the morning, I turned on the computer for research and development, and the information came, and the local git push code reported an error. Okay, take a screenshot of the error report
fatal: unable to access”: The requested URL returned error: 500
To be honest, if you look at this content, it is a feedback permission problem, then directly take the account password and log in to the gitlab page to try it. I took the R&D account and password to log in and it didn’t respond. And my own account login is no problem.
solve:
Log in to gitlab as an administrator user, and then reset the password of the R&D user account.
$ git push -u origin master
To [email protected]:xxx/xxx.git
! [rejected] master -> master (fetch first)
error: failed to push some refs to '[email protected]:xxx/xxx.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.Reason:
in GitHub remote warehouse README.md The file is not in the local warehouse.
solutions:
$ git pull --rebase origin master
$ git push -u origin master