[ISSUE]remote: Could not create socket to ping Stash: Connection refused

Mohanraj August 8, 2017

Not able to Push in to the Bitbucket

 

GD00519242@INBASDPC08424 MINGW64 ~/git/atlassian-project-repo (master)
$ git push
\Counting objects: 39, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (19/19), done.
Writing objects: 100% (39/39), 4.07 KiB | 0 bytes/s, done.
Total 39 (delta 3), reused 0 (delta 0)
remote: Could not create socket to ping Stash: Connection refused
To http://10.20.126.38:7990/scm/ap/atlassian-project-repo.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'http://GD00519242@10.20.126.38:7990/scm/ap/atlassian-project-repo.git'

 

pre-receive hook declined --> We dont have any hooks enabled in bitbucket.

 

Any pointers about this issues.

 

1 comment

Kevin Stark September 5, 2017

I have been having the same issue and opened a ticket for it.  I did not get resolution from the ticket but in my case found at least a temporary solution.  I am running iptables on my server and have rules opening up the ports specified for the services listed.  When I stopped iptables, my pushes ran successfully.  When I ran netstat on the server I discovered it was listening on an additional port.  I added that port, 45453, to my allowed list in iptables and my pushes worked with iptables running.  I have not restarted bitbucket server yet to see if the additional port I added remains the same or if it will change with each restart.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events