gogs: Error when pushing : "error: RPC failed; HTTP 401 curl 22 The requested URL returned error: 401"

  • Gogs version (or commit ref): 0.11.29.0727
  • Git version: 2.11.0
  • Operating system: Kubuntu 17.04 (client), Raspberry Pi docker image (server)
  • Database:
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gogs.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist (usually found in log/gogs.log): logs.txt

Description

I am running a gogs server on my raspberry pi proxy using the gogs-rpi docker image. An NGINX reverse proxy is set in front of the server. I am able to create a repo and clone it, then I create a file and commit it. When I run git push I get the folloing error: error: RPC failed; HTTP 401 curl 22 The requested URL returned error: 401 fatal: The remote end hung up unexpectedly fatal: The remote end hung up unexpectedly

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 7
  • Comments: 15

Most upvoted comments

wrong pass word … 😊

My system is win10. I had solve my problem. The windows had save my error password. Step 1: control panel Step 2:User Account Step 3:Credential Manager Step 4: modify my password image

Same issue. Password is correct.

Had the same issue, password was 100% correct. The symptoms that I had were - only one of my computers was affected. I could pull and clone without restrictions, but I could only push super small chunks like code only. Big commits that contained graphics or sound files always returned this error. Tried to reinstall Git and Git clients on the affected PC. That did not help. What helped was: git config --global --unset http.postBuffer

I am able to overcome this error on every new repo by setting the origin url to include the username: http://<mygitserver>:<gitserverport>/<RepoName>.git -> http://<myuser>@<mygitserver>:<gitserverport>/<RepoName>.git

I have the same issue with TFS and Git 2.21.0. It seems to be an issue with Git and the size of the the repo / of some change. The password is correct for sure. At least it works with a small test repo so it cannot be the password.

I had the same issue. I used these commands and it worked: git remote remove origin git remote add origin https://github…com/user/repo git push --set-upstream origin master

source : https://stackoverflow.com/questions/15240815/git-fatal-the-remote-end-hung-up-unexpectedly