Stash push problems

I just started using Stash, I setup a project and a repository and gave myself admin access to the repository.  I'm trying to move code from a newly created repository on my workstation to the stash server.  From my workstation I run the following commands:

git remote add origin http://username@stashurl.mydomain.com:7990/scm/apps/reponame.git
git push -u origin

To which I get: 

fatal: unable to access <url above> : The requested URL returned error: 403.

If I manually copy the repository to the server stash is running on and execute the exact same commands as above I get prompted for my password and it works just fine.

The port (7990) is open on the stash server, I can telnet into it.

Any ideas?

3 answers

1 accepted

I ran wireshark last night and recreated the error.  I discovered the proxy server was rejecting the git traffic based on a list from Blue Coat that had categorized the URL as unwanted.  The URL that Git showed me in the error message was the repo URL ending in .git, but the url it actually sent across the network had /info/refs?service=git-upload-pack on the end.  That's probably what triggered the rejection since the site is on our intranet and the url of the repo works fine in a browser.  I should be able to get around it by implementing SSH since I'm not sure how long it'll take them to change the rules to allow the git traffic over our internal network.

Thanks for the suggestions!

Update:

I was able to get around the problem by using SSH.

Look at this KB that might be able to help you https://confluence.atlassian.com/display/STASHKB/Can't+clone+or+pull+due+to+a+git+outbound+proxy. It hints something about being unable to access the URL so this might be your problem.

No luck, I was hoping that was it because I had to set the proxy in the service startup options so Stash could see the marketplace. I tried setting them in git but that didn't work so I unset them, added the environment variables, restarted the shell and still no luck.

Try setting the stash password as well while making the push

a better way would be to set it in git config at a user level 

Can you type the exact command with the password?

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

658 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot