The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

geting 400 error when trying to clone a repository from stash

Ronnie Otts
October 7, 2012

error: The requested URL returned error: 400 while accessing https://user@stashserver.mydomain/scm/PR/app1.git/info/refs

I have stash(port7990) running behind apache.(port 80)
Apache is behind a hardware loadbalancer, SSL terminates at the hardware loadbalancer(ssl accelerator)

I can loginto the stash ui just find, all actions through the UI are working, just can check in, out, clone, push etc.

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

2 votes
Answer accepted
Michael Heemskerk
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 8, 2012

Hi Ronnie,

The 400 code (Bad Request) usually means that your git client version is trying to use the git 'dumb' HTTP protocol, which is not supported by Stash. Stash only supports the 'smart' HTTP protocol, which was introduced in git 1.6.6. Check the Stash logs; it should contain messages along the lines 'Stash received an invalid git request from host ....'.

If you're using a git client that is older than 1.6.6, please upgrade your client.

0 votes
Ronnie Otts
October 8, 2012

I finally found the logs for stash and noticed "git http-backend not a command"

I realized that I had compiled and installed git incorrectly. FML!

CentOS 6 comes with 1.6.6 so I chose to compile from source, didn't configure the build properly the first time.
All is well now.

TAGS
AUG Leaders

Atlassian Community Events