can't push

[saadlu]

So just trying out stash. Used one machine, everything was fine. But now installed it on a second machine, created a project, repository, cloned the repository on local workspace, made a change, commited and while trying to push the change from local repository to the stash, getting error like

remote: Could not create socket to ping Stash: Connection refused

Full output

$ git push --all

Password for 'http://mmia@localhost:7990':

Counting objects: 3, done.

Writing objects: 100% (3/3), 204 bytes | 0 bytes/s, done.

Total 3 (delta 0), reused 0 (delta 0)

remote: Could not create socket to ping Stash: Connection refused

To http://mmia@localhost:7990/scm/test/test.git  

   ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'http://mmia@localhost:7990/scm/test/test.git '

Any clue?

[Daniel Wester]

Check the repository's hook configuration:

   ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'http://mmia@localhost:7990/scm/test/test.git '

That seems to suggest that you're actually able to connect to stash through git but a pre-receive hook is declining. Do you have any add ons installed that might be interfering?

[saadlu]

Thanks for replying. I haven't added any add ons. This was a vanilla installation. I have tried the installation on a different Windows Installation and doesn't seem to have the problem.

[Adam]

I would suggest you open a support ticket for this at support.atlassian.com. I've not personally seen this before and I suspect wed need to dig in a bit deeper to figure it out. Best of luck!

[saadlu]

The log file

C:\Atlassian\ApplicationData\Stash\log\audit\atlassian-stash-audit.txt 

produces the following everytime push fails

0:0:0:0:0:0:0:1 | AuthenticationFailureEvent | mmia | 1421860866355 | mmia | {"authentication-method":"basic","error":"Invalid username or password."} | @19Y829Tx1041x99x0 | -

mmia is my username and the password is correct.

[Adam]

That's probably irrelevant. As I understand it, Git tries a few different protocols before actually using the right credentials. One of those might be causing this. Disclaimer: Git internals is not my forte and I could be very wrong.