Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Git on Arch Linux:

git svn init -s https://app.svn.beanstalk.com/repo
Initialized empty Git repository in /path/to/repo/.git/
Authentication realm: <https://app.svn.beanstalk.com/repo:443> SVN    
Password for 'localuser':
Authentication realm: <https://app.svn.beanstalk.com/repo:443> SVN
Username: remoteuser
Password for 'remoteuser':
Authentication realm: <https://app.svn.beanstalk.com/repo:443> SVN

No matter how many times I enter my details, it never accepts them. I have logged in successfully with the same credentials in a web browser. I have also tried this without the -s, and with the --no-minimize-url flags. What's going on?

share|improve this question
Do you know if it's Basic, Digest, NTLM, or Negotiate authnetication? – penguin359 Mar 2 '12 at 22:50
Pretty sure it's Basic. – Hugh Guiney Mar 3 '12 at 3:29
Did you try svn directly? Did you try accessing the server directly per http? This probably isn't related to git or even svn. – JonnyJD Dec 25 '12 at 16:21
I have the same scenario using git-svn on windows in the mingw32 shell with Git On my Windows x64 machine I am running TortoiseSVN 1.7.5 with SVN 1.7.3 and I can connect with SVN-cached credentials through both Tortoise and SVN command line yet when I attempt to clone the same SVN url with git-svn I get the behavior described above. – David Alpert Feb 14 '14 at 22:46
Apparently this problem went away for me after I entered my domain credentials (username, then password) 3 or 4 times in a row. Now my git-svn is working against the local svn repos just fine. – David Alpert Feb 15 '14 at 18:25

@DavidAlpert's advice was correct. I fixed this by simply entering my domain credentials (username, then password) 3 or 4 times in a row.

I don't know why, but it worked for me! I repeated this as an answer here since it is easy to miss in the comments.

share|improve this answer

I've found that it's a bug in the latest version 1.9.0, in the previous one I can successfully authenticate.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.