You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Traditionally, our company has accessed bitbucket repositories using SSH such as
git ls-remote --heads ssh://stash.ondomain.com:7999/sqa/ratts.git
and this command is successful.
We are now implementing a new workflow that uses HTTP to access the repositories such as
git ls-remote --heads http://stash.ondomain.com:7990/scm/sqa/ratts.git
and this command fails with error
fatal: unable to access 'http://stash.ondomain.com:7990/scm/sqa/ratts.git/': The requested URL returned error: 500
debug mode for the bitbucket log revealed this message
DEBUG [http-scmrequest-handler:thread-10] <user> @919999750x162357408x0 10.148.18.231 "GET /scm/sqa/ratts.git/info/refs HTTP/1.1" c.a.s.i.s.g.p.h.GitSmartExitHandler SQA/ratts[53]: Read request from 10.148.18.231 succeeded, but the following was written to stderr:
error: bogus format in GIT_CONFIG_PARAMETERS
fatal: unable to parse command-line config
I haven’t been successful resolving this error and need help.
The Bitbucket version is 7.21.0 (and yes, we are absolutely on an upgrade path!)
We used an updated git version installed from tarbal at /usr/local
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.