WebFaction
Community site: login faq

I've set up git as an http application as per the instructions at: http://docs.webfaction.com/software/git.html

I've set receivepack to true and postBuffer to 524288000

I can authenticate and pull from the repository over https. But when I push, I get the following error after being asked to authenticate twice. I am able to log into https://git.alk.io and the authentication works, as well as when I do a git pull. The error_git_php.log is giving me a "Password Mismatch" error.

I'm running git 1.8.0.1 on OS X 10.6.8 (snow leopard)

git pull log (completes successfully)

$ git pull --verbose
Password for 'https://polastre@git.alk.io': 
From https://git.alk.io/repos/alkio
 = [up to date]      master     -> origin/master
Already up-to-date.

git push log

git push --verbose
Pushing to https://polastre@git.alk.io/repos/alkio.git
Password for 'https://polastre@git.alk.io': 
Password for 'https://polastre@git.alk.io': 
error: git-http-push died of signal 11
fatal: git-http-push failed

error_git_php.log -- Note the two password prompts above, but only 1 password failure appears in the log file.

[Sun Dec 09 02:07:25 2012] [error] [client <ip hidden>] user polastre: authentication failure for "/repos/alkio.git/info/refs": Password Mismatch

asked 09 Dec '12, 02:37

polastre
312
accept rate: 0%


I believe that the problem may be your git repo URLs are incorrect. It looks like:

  • You're pulling from https://git.alk.io/repos/alkio, but you're pushing to https://polastre@git.alk.io/repos/alkio.git
  • Your URLs include "/repos"

As per our git documentation, you normally would use a URL like this:

git clone https://git.alk.io/alkio.git

then push with "git push origin master" the first time (ensuring that a master branch exists), and "git push" afterward. Note that in your first URL, the ".git" extension was missing.

If you continue to experience trouble, you can open a support ticket and allow us to try cloning your repository and pushing a trivial change to see if we can reproduce the problem for further investigation. Hope that helps!

permanent link

answered 09 Dec '12, 02:48

ryans ♦♦
5.0k93260
accept rate: 43%

@ryans, you're good. The /repos/ was the fix. FWIW, the "URL_path" in the docs is what was causing the confusion. Thanks.

(09 Dec '12, 13:28) polastre
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×225
×111
×44

question asked: 09 Dec '12, 02:37

question was seen: 4,986 times

last updated: 09 Dec '12, 13:28

WEBFACTION
REACH US
SUPPORT
AFFILIATE PROGRAM
LEGAL
© COPYRIGHT 2003-2019 SWARMA LIMITED - WEBFACTION IS A SERVICE OF SWARMA LIMITED
REGISTERED IN ENGLAND AND WALES 5729350 - VAT REGISTRATION NUMBER 877397162
5TH FLOOR, THE OLD VINYL FACTORY, HAYES, UB3 1HA, UNITED KINGDOM