Yahoo! JAPAN

2011/4/6 -When I do a git push mypro1 master, I get the error Cannot access URL http://mywebsite.com/myproject1/, return code 22 fatal: git-http-push failed.

2014/1/31 -One solution is to clone using the ssh url which will be of the form git@github.com:username/repo-name.git

2010/10/16 -Otherwise, failing to set correct permissions will result in "PUT error: curl result=22, HTTP code=403" when performing a "git push". Now simply ...

2016/7/18 -When trying to upload updates via http/https I was getting the above errors. The solution is here: https://gitlab.com/gitlab-org/gitlab-ce/issues/2669#note_ ...

2009/9/23 -This is probably because you are using an HTTP proxy to access the repo and that proxy doesn't support WebDAV HTTP methods (especially PROPFIND) ...

2019/3/9 -Error: Cannot access URL https://bloodygit.tejat.net/BloodyRum/ServerOS.git/, return code 22 fatal: git-http-push failed error: failed to push some refs.

2016/1/21 -Hey people, I currently installed gitlab 8.4.0.pre from source and I'm running it behind a reverse proxy as mydomain.tld/gitlab (sadly, ...

2020/9/21 -Cannot access. error: Cannot access URL http://git.drupal.org/project/PROJECT.git/, return code 22. or. Unable to access. fatal: unable to ...

All HTTP response status codes are separated into five classes or categories. The first digit of the status code defines the class of response.

You are likely seeing this error because there are newer changes that have been pushed into master than you have in your local repository.